Hi Calin,
I deactivated all plugins except for TD Composer and the ads are still not accessible.
There are no special codes in the Google or custom code areas, however many of the ads (which I can not access right now) have Ezoic ad wrappers around them. The Ezoic ad wrappers have the structure shown below. I used the Ezoic ad wrappers with my old host and Newspaper with no issues.
<!– Ezoic – ArticleSidebar – sidebar_1 –>
<div id=”ezoic-pub-ad-placeholder-102″>
(ad code goes here)
</div>
<!– End Ezoic – ArticleSidebar – sidebar_1 –>
Appreciate any other thoughts!
Hi Bogdan,
Just closing this out on my question about the sidebar. After I removed the Chris Custom Mods, the smart sidebar started working as intended in Chrome again. I didn’t go through the Chris Custom Mods line by line to figure out what part of it was causing the issue, but I might do that later since I liked having some of the Chris Custom Mods to make the site run faster.
Hi Alin / Chris,
I just noticed that after the update to 6.6, the 404s for http://website.com/wp-content/plugins/js_composer/assets/css/vc_lte_ie9.min.css are back in a big way. My 404 log is full of 404s for this ie9 css file since the 6.6 update. Any recommendation on how to eliminate this?
Thanks
It appears I have a similar issue related to the smart sidebar with Chrome. With the smart sidebar option turned on in the theme panel, in the Microsoft Explorer and Firefox browsers, the sidebar scrolls to the bottom of it’s contents and stops while the main article window continues scrolling to the bottom of it’s content. However since the 6.6 newspaper upgrade, in the Chrome browser, the sidebar scrolls to the bottom of it’s contents and then keeps scrolling past the end with whitespace as the main article window scrolls to the bottom of it’s content. Obviously I would prefer for the smart sidebar in Chrome to behave the way it does in explorer and firefox and not scroll past the end of the sidebar with whitespace.
Is this related to the same sidebar chrome bug that is discussed here?
Is the latest version of the theme bundled visual composer 4.7.1.1 from the October 6th email? The change log for 4.7.1.1 doesn’t seem to mention addressing security vulnerabilities.
Yes Andrei, system status shows that speed booster is active. I doublechecked the file id, cleared all the caches, and still have the same result with the jquery-migrate.min javascript render blocking. Any other ideas.
Thanks,
Looks like I had an old sitemap in place that was blocking my Yoast SEO sitemaps, so I took care of that. Thanks for the guidance.
Thanks Chris,
It must be from when I accidentally imported demo content early on since I haven’t deleted any real content. I will check the sitemaps as well.
Ok, I think I’m back in business now. The version of Composer that was included in my download was 4.6.2. I just upgraded to 4.7.1.1 and now it seems to be playing nicely with Facebook again. I just purchased and downloaded the bundled them on 9/21, so it’s hard to believe that one of the critical bundled plugins was that far behind on the version. Thanks for your help.
Just a quick update – I checked with the Visual Composer team and they indicated that when VC is bundled with the theme, the support comes from the theme for VC issues, so I’m back to the Newspaper theme for support on this matter. Thanks,
Ok, did the one by one deactivation of every plugin I have and isolated the issue to Visual Composer. When I deactivate Visual Composer, Facebook reads my Yoast SEO open graph tags perfectly. When Visual Composer is activated, Facebook totally ignores the Yoast SEO open graph tags and does not pick up post titles or post images which is really unacceptable. This would also explain why I only starting seeing this issue on Facebook after installing the Newspaper theme. Is Visual Composer conflicting with the Yoast SEO open graph tags, and if so, is there a way to remove the conflict?
Not sure how integrated visual composer is with the Newspaper them, so I will also see if there is a separate support page for Visual Composer.
