datschge

Sorry for the delay. Covering all possible processes we use took some time clarifying. This is what can happen:

• Publishing/de-publishing on the usual edit post page: fully covered by Simple History
• Schedule publishing in the future on the usual edit post page: scheduled status seems to be covered by Simple History, but when the publishing actually happens isn’t
• Change status through Quick Edit on the listing page: Simple History appears to cover everything but the status change
• Change status through Bulk actions > Edit on the listing page: Simple History appears to cover everything but the status change

Hope this helps finding some potential existing issues. Thanks!

I’m repeatedly seeing this error as well. Seems like post in the line AND p.post_type = post needs to be in quotes.

Excellent! Thank you for the quick reply, fix and update!

Thanks!

I just replayed the workflow that led to the fatal error before now using version 1.5.8. I can confirm that there is no longer any error log of any kind. Switching back to my own account within the popup now leads to the admin dashboard to be loaded within the login popup as well instead closing the popup which looks funky but is no real problem whatsoever. Thanks again.

Looking good, thanks! Looking forward to version 1.0.9.

Works great, thank you!

Excellent, looking forward to that version, thank you!

Thanks for the pointer.

Thank you, looking forward to the new version then!

Excellent, thank you!

Thanks for the quick response. The ON statement needs to be adapted as well though.

I managed to reproduce the issue on my non-productive server. Used WP Rollback to rollback Simple History to some older version, then used WP-CLI to execute wp plugin update –all.

When done on the site the banner “Das Plugin simple-history/index.php wurde aufgrund eines Fehlers deaktiviert: Diese Plugindatei existiert nicht.” shows again (essentially “Due to an error the plugin simple-history/index.php was deactivated: This plugin file doesn’t exist.”). During the execution of WP-CLI the error “Warning: fopen(/var/www/html/wp-content/plugins/simple-history/index.php): failed to open stream: No such file or directory in /var/www/html/wp-includes/functions.php on line 6111” was thrown. I have a hunch this may be due to wrong file/directory ownership. I’ll try again after a thorough chown.

Fake edit: Alright, that was it. GitHub Updater apparently tried to unpack the files in some place it didn’t have the permission for, so the files indeed didn’t exist. A chown across the web data resolved this. Sorry for the false alarm. ??

Looking through the PHP error log as well as the logs WooCommerce is creating I couldn’t find any unfortunately. I’ll try to reproduce the issue on a non-productive server. Do you happen to know if there is there some debug logging capability for GitHub Updater or in Simple History that may be more informative?