hmwind

I have the same problem with the Magazine 3 theme.

Within that theme it is possible to switch the Magazine 3 SEO part off and rely e.g. on Yoast WordPress SEO which I did.

The header.php of the theme contains meta name description tags. However, those are not active in practice and will not be included if Magazine 3 SEO is switched off.

Nevertheless Youst WordPress SEO continues to give the meta name description error.

Richard, In the meantime I modified my theme and the new plugin version now runs (and updates) without further manual modifications from my side.

Update done without problems. Thanks!

That is the solution indeed, Richard!

Thanks a lot for the very quick fix.

I adapted the code and it validates perfectly in W3C now!

By the way, the document write trick is mentioned here:
https://jamesingham.me/blog/google-plusone-w3c-valid

In the meantime I have added the plug-in to https://www.3dtvnieuws.nl and added a THANK YOU statement with link to the plugin on the cookies and privacy page

Hi Richard,

I got the plugin working properly after adapting my own theme. The main changes were adding the jquery lines as mentioned above and in addition I had to change some layout settings.

Is there another way to load your script functions (e.g. in the header.php)

I am unclear what kind of other functionality cookielawinfo_enqueue_frontend_scripts() offers. Is the Audit function part of that?

Hi Richard,

Thanks a lot!

After adding:

<?php wp_enqueue_script(“jquery”); ?>
<?php wp_head(); ?>

to the header.php of my theme ist seems to work now.

Now I have to make sure that other banners are not overlapping the banner of your plugin.

Hans

Hi Richard,

Thanks a lot for your very quick response. That is highly appreciated.

There is no carriage return in the text and I tried header and footer as well as disabling colour pickers.

As your plug-in works flawlessly in the standard theme I will have to check my own (adapted) theme for jQuery modifications. Maybe hard to find as I am in no way a PHP expert.

I’ll post my findings.

Hans

From what I Read in this forum I understand that this problem has not yet been corrected in a newer version of W3TC. Is that correct?

Is there any new release planned with a fix for this?

Unfortunately I have exactly the same problem.

All access to the w3tc/pgcache directory is denied by the server. Had to un-install the Plugin again because spiders got a 403 Error.

It looks like that did the trick Frederick. Thanks a lot!

I have similar problems.

Initially I decided to use preload cache but that did not work out well for me so I dedided to disable preload again. However, the “list all cached files” option did not come back despite the fact that the total number of cached files is below 300.

Any fix will be appreciated.