check error log ?
disable plugins ?

Look for custom field bottom of a post, the name of custom field is there… not in code of public page, but in post editor

• This reply was modified 8 years by simchris.

the view count field should be a custom field as part of all your posts, look at the custom fields at bottom of the posts to see what the hit counter field actually is, like ‘views’ or “Views” or “hits” or “Count” or whatever.

you might try ‘webnus_views‘ and see if the count then shows on your posts.

Be sure to make back up of your dbase FIRST, which you should already have done before changing themes!

So
did you fix your robots.txt file>

did you resubmit your sitemap after the fix?

You might check the Yoast support topics since not related to theme in any way.

I don’t work here but you might use the inspector in Chrome to see the styles and add custom css for

<div class="comment-content">
<p>These are impressive, Tre! You are a person of incredible talent and vision. I especially like the portrait of Joe Biden and the one just above the Statue of Liberty. That face is so expressive — compels the viewer to pause and consider what the young man might say in a face-to-face conversation. Congrats on your show at the Glen Allen Cultural Center!</p>
</div>

The theme uses a different custom field for the counter; so you need to edit the /includes/wp-booster/td_page_views.php
file or similar.

a) figure out what the name of the custom field was for your old hit counter (e.g., on my sites it was ‘views’)

b) then edit this line at top of the page views file to match your custom field; e.g.,
static $post_view_counter_key = 'views';

What security issue are you referring to with the current bundled version?

Unless you’re using the 2015 version, you should be fine.

The current bundled version is found in the ‘all files’ folder from the theme download.

You can purchase a RevSlider license on your own, obviously, but the bundled version is generally the latest one included with the theme license.

Can you specify which security issue concerns you?

Theme has nothing to do with your content on instagram — perhaps optimize the images you upload to instagram before you upload them?

Theme can’t change images on other sites; if it’s loading from the cdn, that’s where the images are. See the instagram website for developers, to learn more. 🙂

There might be some ‘preview’ plugin you can use which loads preview images locally of your instagram feed, and saves those images locally .. which might be faster, although would load up your local storage, and might actually be slower … but don’t have recommendation on that.

(I don’t work here; just veteran/dinosaur in this industry)

Basically make your robots.txt file blank and retry. If Google saying they can’t read your site due to your robots.txt file — you answered your question already.

try this instead:

# This space intentionally left blank
# If you want to learn about why our robots.txt looks like this, read this post: https://yoa.st/robots-txt
User-Agent: *
Disallow: /suggest/?*

I think you have to re-activate if you upgrade from 3x to 4x; as new theme; or if you uninstall a demo and go back to the default setup.

Well, only you can educate yourself on what structured data is. Sorry .. wont try to help you again. Good luck!

Hopefully tagdiv can point you at a better article in your language.

https://support.google.com/webmasters/topic/4599161?hl=en&ref_topic=4589289

Version included with theme is latest compatible ‘bundled’ version; see the theme docs for more info 🙂

Might want to check the Yoast SEO plugin forum on WordPress.org for basic solutions to the most common issues; Yoast is not part of the theme.

Use an rss widget to load an rss feed from one site onto another.

you need to install the version included with the theme in the /allfiles zip > plugins

Sorry. Did not know that. I apologize for butting in.

First time I’ve heard of that issue and I’ve been here 4 years now.

You may wish to email them directly for clarification. Clearly if they “warned” you not to do something, but then did, that might be the reason.

Apologies for my input.

TagDiv can’t ‘take down your site …’ — TD theme is only a theme, it’s not your site manager, hosting company, or admin. Your site can break for various reasons:
a) using hacked theme found online, not legal copy
b) site hacked
c) automatic plugin update breaks site due to bug (Yoast, etc.)
d) hosting company updates system, breaks permissions for php or other such as removing content for legal infringement — nothing to do with theme
e) caching or CDN issue, which must be addressed from those platforms
f) third party element such as ad system or similar breaks, causing pages not to load — nothing to do with theme

Good first step;
a) check your error logs
b) check with your hosting company
c) check for console errors, or similar issues
d) scan site with Securi and other tools for possible hacking, etc.

Only you can manage and update, and keep your site online.

A theme cannot manage your website for you.

( I don’t work here; just some feedback. )

Usually when going to full dot upgrades, it’s an entirely new theme, and so you also need to update the child theme as well. Meaning you need an 8x child theme with 8x parent.

Hi, changelog to what exactly? (sorry)

https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/

Hi
I know I’m technically ‘not updating this thread’ anymore to concentrate on my adventures with php7 + https + http/2 …

but I only today discovered this awesome ‘ultimate boilerplate’ for setting up a custom wp-config.php file with all the pieces to customize however you need all in place, and then you just remove what you’re not needing. Very very nice.

This came recommended by the official WordPress.org codex/docs, btw:
https://github.com/pixeline/wp-config-supercharged/

Wrong. Above the fold CSS loads in the head so that on mobile one doesn’t have to wait for all files to load.

But up to you! Have fun 🙂

• This reply was modified 8 years by simchris.

Actually loads faster in the head, which is why it’s there. 😉

But I don’t work here; just feedback.

‘www’ vs ‘no www’ is managed from your hosting settings, and in the WP admin panel for site URL — theme does not manage http vs https or www vs non www.