eugene212

Tested the latest version 2.0.7 – the sub-directory issue is still there, so reverting back to 1.7.3…

Are there any plans to address this issue ?

I am glad that the solution helps to overcome this weird issue !

Hopefully WP-Optimize developers also will pay attention to this since the previous version apparently did not have this issue.

I was observing the same issue on one of my websites (but not the others) – since the conversation ended without a resolution I had a closer look at my case and found that adding the ‘/’ at the end of the login link fixed the issue, i.e. after changing ‘…/wp-login.php’ to ‘…/wp-login.php/’ in my browser bookmark the cookie is loaded (can be observed using F12 in Firefox) and there is no more error message.

The issue is gone now – probably it was something to do with the hosting…

Unfortunately the issue of never ending loading spinner for WP sites placed in sub-directory is not fixed in the latest 2.0.6 version…

So far the solution is to revert to 1.7.3 for such sites, but it would be nice if there is no need for such approach !

Hi @aryadhiratara,

Your suggested simple workaround works for me, thank you !

The latest 2.0.0 version does not resolve the issue…

Note: the issue is not there if visiting the page while logged in as an admin.

This excellent plugin did not have any issues before version 2.0.0, but now I experience the same problem (version 2.0.3) on the site where WP is placed in a sub-directory (other sites seem to be fine), i.e. never ending loading spinner when clicking on ‘rollback’ for any plugin.

Firefox console shows the following error:

Error fetching data: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data admin.js:1:1489
i https://mysite/wp/wp-content/plugins/wp-rollback/build/admin.js?ver=9ec969e696dc68bb2222:1
(Async: promise callback)

• This reply was modified 1 year, 2 months ago by eugene212.

Hi @wpmudevsupport16,

Thanks for the additional confirmation – since it seems to be not specific to Forminator forms I am raising the issue at Optimize More plugin support.

Regards

Hi again,

I have found that the conflict is between Forminator Textarea field and Optimize More plugin:

If either Remove CSS or Remove JS are just enabled in Optimize More (no any further settings):

Then Forminator’s Textarea loses new lines, but ordinary text keeps its new lines:

So it seems to be some issue between Forminator and Optimize More plugin, please advise !

• This reply was modified 1 year, 4 months ago by eugene212.

Hi @wpmudevsupport11,

The field in question is Textarea that actually has default placeholder text highlighting the option of having new lines:

I have tried a fresh minimal WP installation + Fominator + Colibri theme and the issue is not there, but it’s visible on the production site, so it could be some conflict with other plugins (or theme) – I will run more tests (disabling other plugins, etc.) to get a clearer picture when the issue crops up and let you know.

Thanks for the clarifications !

Hi @bojankatusic,

I will follow your advice, thanks for the clarification !

As for the initial concern, is it GDPR compliant, i.e. would not requests for some data via 3rd parties violate GDPR compliance (similar to requesting Google fonts) ?

Apart from acquiring screenshots, is there any other cases where the plugin might engage 3rd parties ?

@raulandash,

Regarding Persistent Object Cache I think I saw a question before and the reply was that WP-Optimize has it under consideration at this point of time.

If it helps, I was also looking for Persistent Object Cache solution (as opposed to running Redis or Memcached services) and found that SQLite Object Cache plugin works nicely in my case.

The daily cache clearance because of the WP-Optimize created cron job (wpo_reset_webp_conversion_test_result) was reported in many posts.

Possible temporary work around until it’s fixed could be by using WP Crontrol (or similar) plugin to pause this cron job or maybe by reverting to the previous WP-Optimize version.