Delete Notice: Check out the Autoptimize Extra settings to activate this option.

Okay…Just now I opened up my dashboard to discover something conflicting with my Google Analytics Dashboard. I deactivated Autoptomize; GAD worked; I re-activated–and got an error message:

[16-Oct-2018 01:22:30 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/[redacted]wp-content/plugins/autoptimize/classes/autoptimizeMain.php:1) in /home/[redacted]/wp-includes/rest-api/class-wp-rest-server.php on line 1248

So I changed the code back to what it was before, which made GAD work again. Rolled back to 2.4.0, updated to 2.4.1, then added the new snippet. So far, so good.

closing as we now at least have a working workaround. we might switch to storing dismissal in a setting instead of a transient, see https://github.com/collizo4sky/persist-admin-notices-dismissal/issues/17.

frank

Where do we place the code-snippet shown on Page 4? Can you provide step-by-step instructions?

Thanks!

you could add it to your (child) theme’s functions.php or use the code snippets plugin jetxpert (snippets -> add new snippet (-> choose a title) -> paste the code -> save changes and activate).

hope this helps,
frank

Hi @optimizingmatters,

Thanks for your help. It worked. However, we see this as a temporary fix.

Any plans to take care of this issue at a plugin-level? Why have the message displayed in the first place? The issue does not occur with version 2.4.0 and below.

PS: The “solution” we identified earlier only worked on a temporary basis (cache build-up or refresh brought back the issue), so please ignore it.

Again, thank you!

Any plans to take care of this issue at a plugin-level?

this is being looked into at a framework library level (which AO incorporates)

Why have the message displayed in the first place?

because I consider it a requirement to promote the image optimization ??

The issue does not occur with version 2.4.0 and below.

that’s because the notice was introduced in 2.4.1

if you want there’s a potential fix for the notice’s non-dismissable state you found, would be great if you could download the github version and check if the “try shortpixel” notice can be dismissed (technical details; the PAnD framework library now doens’t use transients any more to store notice status, but an option).

looking forward to your feedback! ??
frank

Hi Frank,

Thanks for the suggestion and possible fix. We have spent too much time on this, so we decided to purchase and use WP Rocket. WP Rocket works like a charm. Best wishes.

Cheers!

no problem @jetxpert, wp rocket’s a good choice ??

I’ll have a look as soon as I can grab 10min of time ??

To continue this dialog, as this is a problem for us as well (on several AWS self-hosted production sites), I suggest you review @afragen’s comment from last month, which is right on point. (You may have already incorporated a fix.) But to reiterate, what you’re doing here is not a proper use of a transient, per the WP codex. The transient framework is not meant t reliably store data for any length of time. You should probably move your storage of the preference to a blog-level option.

Just as a matter of record, the Persist Admin notices Dismissal library, which brought this issue to light, has been updated to store it’s data in the options table and not as transients.

Autooptimize has incorporated this update on GitHub but needs to release to the Plugin Directory.

thanks Andy ??

I can confirm AO 2.4.2 will include the updated PAnD library which stores dismissal state as an option. One can download that new version here to test it, feedback always welcome (there’s a collection of other small changes in there, see commit log)

hi, updated to the new version, but the warning has reappeared again and there is no way to remove it.

I had to do this as for the previous version.

easy solution; edit wp-content/autoptimize/classes/autoptimizeMain.php and on line 550 change

$_ao_imgopt_active = false;

into

$_ao_imgopt_active = true;

frank

Weird you’re still having issues @nick8182, the fix (in the updated PAnD component) was tested successfully by multiple others that had problem .. :-/

Is there anything relevant in the PHP errorlog which might shed a light on what is going wrong?