If you have too many ad units from other networks, Google will consider the content to ad ratio to be bad, and consider your site “spammy.” Disable most of your other ad units, then retry.
The theme does not put ads on your website, you do 😉
useful to see:
https://support.google.com/adsense/answer/1348688?hl=en
https://support.google.com/adsense/answer/48182?hl=en
-
This reply was modified 9 years by
simchris.
YOu don’t need to update VC; you don’t need license code.
YOu will get updated version when the theme is updated.
I’d probably do this, except NOT use the pokey Envato updater:
https://forum.tagdiv.com/how-to-update-the-theme-2/
I’d probably make backups, and update WP asap as latest update has notable security fixes for stuff in the wild.
THEN worry about theme upgrade.
Remember you need to FULLY clear caching in Chrome, etc., to SEE any changes to CSS/JS.
So, did you clear your caching plugin, reset CDN, clear your browser history?
I don’t work here. But then, my site is working.
One presumes you’re using latest version of theme, updated your plugins, etc.
WP update does *not* break dbase settings for theme panel or stuff like widgets or similar. You may have some other issue.
A theme or WP update does *not* delete pages. so, your web host might have had an issue; you got hacked, or some plugin or setting you have unique to your setup broke. No way to know.
Ideally if you have missing pages — which is bad — you should roll back to your most recent backup, if any.
If you have no backups, now would be good time to plan for that!
I think you can do that by editing each module in your layout in visual composer on your home ‘page’
If you’re using caching, then you need to clear cache in both site/plugin as applicable AND in your web browser. Chrome in particular holds onto CSS until you clear history or do force reload.
e.g.,
Chrome:
Quick hard refresh can be done by using the following short cut keys
Windows/Linux:
Hold down Ctrl and click the Reload button.
Or, Hold down Ctrl and press F5.
just open the Chrome Dev Tools by pressing F12. Once the chrome dev tools are open, just right click on the refresh button and a menu will drop down. This menu gives you the option of doing a hard refresh, or even clearing the cache and do a hard refresh automatically.
With any new major update to WordPress, you should have backup to roll back to, if needed; you also must clear your browser cache, and any/all caches used in wordpress, CDN, etc.
You can also
a) resave permalinks
b) optimize db to clear transients with wp-optimize
c) simply resave menus from menu panel if none of the above helps
Also good to turn off auto-updates for WP, so you can be prepared with backups prior to doing an update to new version of WP; then roll back if something breaks.
Theme is working for me, but you can try the cache clearning, resave permalinks, resave menu; this is all necessary with many things that changed in WP with new versions of 4.6x.
See the sticky post top of forum index and the theme docs;
you don’t need to update. The bundled version is updated with theme updates 🙂
Might help to explain WHERE you are actually putting the CSS ?
often bottom of your style.css file is best place; although if you’re using the custom CSS box in theme panel, for some things you may need to add the common !important tag to your over-ride to force the CSS to over-ride the default.
Depends on where you’re trying to do that.
In a post you just use normal HTML. Headlines/titles are already H1.
In sidebars and indexes for stories, headlines are usually h2 and h3, as there should only be one H1 per page.
For home page, for a site description, just make a text box and wrap a site description in h1 tags; for custom CSS apply a style class like
<h1 class="homeh1">My Neato Description</h1>
(( I don’t work here. ))
If you see the docs, you get a “bundled version” with the theme (it’s licensed/legal); you don’t get a free license with the WPBakery folk for support and updates (although you could buy one, supposedly).
So, you get the latest “tested” version of VC when the theme itself is next updated. See the sticky topic top of the forum index on “updating visual composer …”
🙂
Whatever. I dont work here. But learning to do this stuff will help you no matter what theme you use. If you cant even look at the example provided, then likely going to have a lot of trouble in future. Cheers.
Had this happen on a site using ACF, different theme; as ACF has option to “hide” some of the post page settings, and broke the custom stuff, until I unchecked some stuff on the ACF “who can see custom fields” settings.
Not sure if your issue, but possible.
Maybe not. Just a thought 🙂
There was new version of WordPress released today; if you have automatic updates turned on, then something might have broken. Often you can resave permalinks, clear caches on site and in web browser, to clear things up.
Usually best to disable automatic updates, and also make sure you keep backups prior to updates!
There was new version of WordPress released today; if you have automatic updates turned on, then something might have broken. Often you can resave permalinks, clear caches on site and in web browser, to clear things up.
Usually best to disable automatic updates, and also make sure you keep backups prior to updates!
Best bet is to learn to use FTP (e.g., Feedzilla, CuteFTP, etc.) … you can then login to your site, go to your plugins folder, or theme folder, and *see* what is actually there. Delete old folder, upload new folder, etc.
This is best way to ensure nothing is broken by your WP installer, etc.
You don’t need to “activate” it as it’s a bundled version. You simply activate the plugin on the wordpress plugins panel. You don’t need to activate it anywhere else. You do, of course, need to install it first. See the install docs for more info.
Simplest way is to add a mailchimp shortcode in the template file(s) you’re using for your post templates used.
An advanced user would hook in a function/filter in functions.php to put the Mailchimp code at bottom of your posts automatically.
You might check to see if Mailchimp has plugin to do this?
TagDiv likely has better answer 🙂
This is an issue with all themes; where you need to tweak some stuff with custom CSS depending on how you happen to use the theme.
Also note there is difference between
A) mobile friendly
B) high pagespeed score for mobile devices
so, your site can have a medium score for pagespeed insights and still be “mobile ready” for Google.
Two totally different things.
For example testing one of your posts
https://www.cubacontacto.com/2016/08/25/los-problemas-economicos-de-venezuela-causan-escalofrios-en-cuba.html
says your site is “mobile friendly” according to the test:
https://www.google.com/webmasters/tools/mobile-friendly/
however, when you see the test render it looks like you have some funky broken registration panel dominating the page which is not normal.
So, it looks like something is not setup properly in your registration system you happen to be using.
You can try disabling the lazy load image function from the theme panel.
Also, best to use Google’s recommended tool to manually compress the main js files, as the caching plugin more likely to break the page load for some users.
You can get latest one from the theme download on your Themeforest account 🙂
It’s in the “all files” in the plugins folder.
Where are you “clicking on the visual composer icon” ? Usually that is done on the page edit screen, and should not take you off your admin panel.
(( or, the code is being broken by the ad unit/block being used/served on the home page, either via theme or ad plugin … ))
suggest you look at actual ad spot doing ‘view source’ on your home page to see what is there, and also check the text in the theme panel for any gremlins like curly quotes, etc.
You might have to email the ad code you’re using to TagDiv to check to see if it’s being re-written by the ad system incorrectly.
Dunno.
Yep. That means they don’t allow that content to be loaded on another website, like yours.
So, you should contact that ad provider and either have them add your site as allowed, or check you have the code setup right.
Javascript, image time-outs, all sorts of things. Some browsers don’t work right (ahem, Firefox) with certain things. Sometimes you have to go by the lowest (bad) web browser to reach everybody the same way. Not counting dead stuff like Safari on Windows, or FF 3, IE6, etc. 🙂