Autoptimize conflict

No idea I’m afraid; normally AO & W3TC work together (on condition all minify options in W3TC are disabled). Still it’s possible this is due to a combination of factors (AO + W3TC + XYZ).

what you (mrsupernatural) could do is;
* re-enable W3TC (you want a page cache plugin, unless if you hoster has page caching)
* if the problem re-appears, selectively disable (and re-enable) other plugins while clearing W3TC cache to see if you can identify what XYZ is

once we know which plugin is causing this, we can look into this (preferably with the help of the developer(s) of that software)

frank

@mrsupernatural: Our plugin inserts valid JavaScript. So it not our plugin that breaks your pages, but it is one or a combination of other plugins that take this JavaScript and somehow break the pages.

In other words. Our plugin simply inserts a piece of code which is exactly how Google has specified it. Those other plugins take that code, do some fancy stuff with it and then output problematic code.

So there is nothing I can possibly change in our plugin to get this fixed.

Also the – noptimize – exclusion only works with Autoptimize since it is function that @futta built in. W3 Total Cache doesn’t have such a function which prevent me to build in an exclusion.

I agree with Frank that you need to find a setting that will get everything working together. Turning on/off those plugins, maybe switching them out will help.

I would spend some time to try to find out which plugin really is doing the damage on your site, but since you won’t give me access to you install there is really nothing left for me that I can do.

And maybe our FAQ is not entirely right. Maybe the issue never was with Autoptimize, but always with W3 Total Cache (or a combination, or something else). But since this is a very rare case I was not able yet to pinpoint the exact reason.

• This reply was modified 8 years, 2 months ago by alekv.

Hi @mrsupernatural

Have you found a way around it?

Is there anything else I can help you with?

If not I will close this thread in two days.

Regards
Aleks

Hi,

Sorry for my lack of reply I hadn’t a chance to look at this. Going to start testing and disabling bits to see if I can fix it. Probably start with w3 since that is the plugin that breaks it directly.

@mrsupernatural: Also try to turn off different settings in W3. Maybe it is just one function that is problematic.

Ok I think I have fixed it. It’s the w3 object cache. I was testing these two pages if you can confirm it’s working on your end too:

https://luxzura.com/stage/shop/sheepskin-rugs/new-zealand-sheepskin-rug-single-pelt/
https://luxzura.com/stage/shop/lamb-sheepskin-cushions/new-zealand-short-wool-sheepskin-cushions/

I had a quick look and this guide says that this option can cause problems with shared hosting, which I am on: https://theme-fusion.com/advanced-w3-total-cache/

well, had a quick look at the HTML source and can confirm that:
* the noptimized adwords-block is present
* there is not autoptimize warning about </body> not being found any more

so yep, it seems like W3TC object caching is to blame. good find!

happy holidays!
frank

Excellent :). Hopefully it wasn’t that important anyway.

Thank you both of you for your invaluable help. Really appreciated.

I also confirm that all works properly now.

Thanks so much to both of you guys to have gone through all the hoops to pinpoint the issue !!

I am particularly delighted because it has not been the first time that our plugin has been blamed to be the source of those rendering issues. At least now I know much better how instruct new users to fix it.

Thanks!

Aleks

Just to update, I found that it’s not as simple as I stated above. On my main site it has broken my theme but on my new stage site it works: https://luxzura.com/afold/shop/sheepskin-rugs/new-zealand-sheepskin-rug-single-pelt/

I can’t see why to be honest I even disabled all the plugins that differ between the main site and the stage one but it didn’t change anything. Very confusing. I had all the settings the same on w3 and AO for both too. The only thing that fixed the theme is disabling the adwords plugin. Thought you might want to know anyway for future. I am going to pursue other ways to get remarketing added as this plugin continues to break my theme and is seemingly impossible to see why at the moment.

@mrsupernatural

As stated in the FAQ of our plugin there are incpompatibilies usually provoked by minification plugins, W3 Total Cache, Rocket Cache, etc.

The problem is not in our code. We are inserting the remarketing code exactly as specified by Google. It is the optimization methods of the minification plugins that turn the remarketing code into a problematic peace of code that in some cases affects the themes.

Autoptimize is the only minification plugin which is compatible because the developer has built in a functionality that lets us exclude our code from minification.

In general you should be able to fix those theme issues by disabling minification.

Also it is my personal opinion that remarketing is more valuable than minification. So if it comes to deciding turning off one in favor of the other I always would keep the remarketing code.

Regards
Aleks