• Resolved datschge

    (@datschge)


    Hello, firstly thanks for a great useful plugin!

    Another plugin only available from GitHub forces us to use the GitHub Updater plugin to keep it up to date. GitHub Updater appears to see Simple History as a plugin also supporting GitHub as installation source thanks to the * GitHub Plugin URI: https://github.com/bonny/WordPress-Simple-History line in index.php. Unfortunately subsequent automatic update fails due to a missing index.php, after which the plugin gets deactivated, all its data removed, and can’t be activated again before manual installation.

    To avoid that from happening again I disabled automatic updates just for Simple History. Ideally I hope Simple History can either actually support GitHub Updater or remove that above mentioned line announcing the use of GitHub.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author P?r Thernstr?m

    (@eskapism)

    Thanks for the bug report. Not sure what’s causing the error however, because the plugin does have an index.php-file, so why does it say it does not? Do you have more information, perhaps an error log from the github plugin or something?

    Thread Starter datschge

    (@datschge)

    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?

    Thread Starter datschge

    (@datschge)

    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. ??

    Plugin Author P?r Thernstr?m

    (@eskapism)

    Good to hear that you solved in and thanks for all the updates! ??

    I’m late to this but sorry you seemed to be having an issue with GitHub Updater, now Git Updater.

    Git Updater uses core methods for updating so any update issues will be general WP core issues, or more likely, permissions issues with some folder in the update pathway.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Broken GitHub Updater support deactivates Simple History on automatic update’ is closed to new replies.