Mick Levin

Thank you team, the option B worked.

FYI: got this message upon activation:

The Repair Action Scheduler process is complete. The following actions have been performed:

Created table: actionscheduler_actions
Created table: actionscheduler_claims
Created table: actionscheduler_groups
Created table: actionscheduler_logs

The Repair Action Scheduler plugin has been automatically deactivated.

Thank you for the option B. Will try it.

And the option A won’t work, since Analytics mode did not exist in previous version, while new version enables it automatically. Dead loop.

Maybe your emergency plugin also could do some update_option to make Analytics mode “already” disabled, ahead of 1.0.49 update?

Sincerely,
Mick

Hi team,

I understand that the problem exists in the 3rd party code from Automatic and that you should not tamper with that code, but rather escalate it to them.

But since you including that code into version 1.0.49 (vendor/woocommerce was not included into previous version) does negatively impact some of your users, then maybe you could do something about it now?

E.g. check if the table $wpdb->actionscheduler_actions exists, before executing (including or requiring) that whole vendor code? Or do more smart checks, like

IF table ‘$wpdb->actionscheduler_actions’ DOES NOT EXIST
AND option ‘schema-ActionScheduler_StoreSchema’ DOES EXIST
THEN
DELETE option ‘schema-ActionScheduler_StoreSchema’
END

You did identify that these are 2 conditions are causing the fatal crash (right?). So maybe do that.

Or at least release that as a quick fix-plugin, if you do not want to bloat your own code.

Thank you.

Thank you but that was not really an acceptable solution. Please add that code into next version of your plugin and push it.

I can not do that manual procedure on so many of clients’ websites I support.

Looking forward for your plugin to work around this all by itself.

Thanks a lot!

Will definitely check it out!

Sincerely,
Mick Levin

Thank you, the updated CSS worked in my test case.

Hoping to see updated fixed version soon!

Sincerely,
Mick Levin

Thanks Anton.

Wait a sec… are you one of them? ??

Thanks Anton,

The Smush plugin *is* the 3rd party code to WordPress ??

I am not going to cut it open, if there is alive support team behind it.

And I hope they are reading this support forum, otherwise why it does even exist ??

Take care.

Thanks Anton, but that was not the best advice to tamper 3rd party code though.

Besides removing a call to “__” function XXX times is defeating the purpose. If we speak of a hack-around, then it has to be in a code section which loads up the [im]proper translation.

Cheers.

Thank you support.

It’s commercial from Elegant Themes, which I have a subscription with. Not as feature-rich, but does the work.

Nope,..

Since it looks like there is no support for this plugin anymore, I just switched to another one.

Good luck!

Thanks Scott,

I’ve figured as much…

I am trying to find a way to still put jQuery into a footer – that’s one of my “must have” things, and I am working with each plugin author which has a dependency on jQuery, to make sure that it still works when all scripts are in the footer.

Sorry, but I just can’t let it be in a header. I am not on WPengine, thus every bit of optimization I can do, I will. So… for now I am keeping it in the header. But I am going to dig around to find a way to fix that, one way or other.

Cheers.
Mick.

Thanks Greg,

Just emailed you the PO file!

Sincerely,
Mick