• When signing into a client’s website to update another plugin this evening, I noticed a prompt across the top of the Installed Plugins page. The prompt states the following:

    The plugin wp-file-upload/wordpress_file_upload.php has been deactivated due to an error: The plugin does not have a valid header.

    Yes, this website has a cache plugin installed that was purged once your plugin was updated to v4.9.1. Reason I am stating this is that another user of your plugin suffering from an unknown error was asked this when they asked for help.

    Will appreciate any help you can offer me in resolving this.

    Thank you in advance.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author nickboss

    (@nickboss)

    Hi, what happens if you try to activathe the plugin again? do you receive the same error?

    Nickolas

    I am getting this error too. I have re-activated the plugin and it seems to work again. Will report back if this re-occurs.

    Thanks for a great plugin.

    Geoff
    https://digitalprintshop.co.uk/

    Thread Starter Trish

    (@trible)

    @nickboss Sorry for my delay in responding.

    In re-activating the plugin as you suggested, I did not receive any error. Emptied the cache and even the prompt disappeared… pheeew. So, what was that all about, were you able to determine why this happened?

    Thank you!

    Plugin Author nickboss

    (@nickboss)

    Hi, I have changed the process of how the plugin loads to make it more flexible. Maybe this caused the problem, in combination with caching.

    It didn’t happen to my environment during testing of 4.9.1 version.

    Please let me know if it happens again.

    Nickolas

    Thread Starter Trish

    (@trible)

    Updated your plugin to v4.10.0 and the very same deactivation and error occurred as before. Reactivated the plugin and all appears to be okay. Thought you would want to know.

    Plugin Author nickboss

    (@nickboss)

    Hi, yes this is an expected error in this update because I changed the header file of the plugin. This happened with the previous version as well, however it will not be repeated in future updates.

    Regards

    Nickolas

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘plugin got deactivated due to an invalid header’ is closed to new replies.