[ilianandreev]

Hello,

Sorry for the rant earlier, I got frustrated from negative experiences with other plugins before and your suggestion to try and identify the issue myself. For the time being I’ve switched off “Aggregate Inline CSS” setting from Autoptimize. But please in future releases try and export your css in external file instead so that it is compatible with not only Autoptimize but other extensions (I found one other CSS issue with another plugin but fixed it).

Regards,

Ilian Andreev

[ilianandreev]

Please delete my login credentials from my last comment. I’m unable to edit it. I’m afraid if we’re unable to resolve this I will ask for refund or chargeback of my purchase.

Regards,

Ilian

[ilianandreev]

Hello,

I’d like to criticize you for the support received so far. Being a software developer myself, this is NOT how you should support your customers, asking them to compare HTMLs and blaming them for not using “supported” extensions. You need to ask for login permissions and investigate the issue yourself. Since this didn’t happen I had to debug it myself.

There is an option in Autoptimize plugin “Aggregate Inline CSS”:

prnt.sc/n9z48p

This was turned on so far and working fine and I’m using around 20 plugins. However when your Affiliate plugin is on and this setting is on, it breaks the CSS of my page and the layout respectively. This leads me to believe that your plugin is simply poorly written with CSS scatterred around code instead of injecting it in external file for easier compatibility with caching plugins and other extensions.

Please try to investigate this issue on your side and tell me if you can come up with a fix so I can turn on Aggregate Inline CSS setting as well.

I hope you understand my constructive criticisim.

Regards,

Ilian Andreev

[ilianandreev]

Hello guys,

The javascript errors were coming from a Facebook chat widget plugin (Beeketing). I deactivated it, but it is irrelevant to the issue. The staging copy is exact same as my production website.

The company is Laborator, theme is Aurum.

Here are screenshots of the messed up layout:

Production:

prnt.sc/n9npck

Staging:

prnt.sc/n9npv9

As you can see on staging, the CSS is all over the place.

After some testing I found the issue, your extension is conflicting with a caching plugin I use called Autoptimize. Can you please help me resolve it?

I can exclude certain CSS and JS scripts in the settings of Autoptimize plugin, if you can just point out which I will add them to the exception list.

Best Regards,

Ilian Andreev

[Author]

Posts