Chris Jean

With the second option being the issue, I can think of two possibilities:

1) The plugin version number was not updated properly when the zip file was created. In other words, the plugin is updating just fine, but the plugin in the zip file still has the old version number.

2) There is some type of new compatibility issue with your site and the Easy Theme and Plugin Upgrades plugin. I say new issue since you indicate that it was working before.

I’ve seen #1 many times before. It’s a simple thing to accidentally forget to update the version number before shipping out a plugin update.

The least-technical way to test for #1 is to manually update the plugin (use FTP to remove the old plugin directory and install the plugin zip file as normal). If the version stays the same after updating, the plugin zip file is the issue and you need to contact the plugin developer to ask for a new zip file that has the proper version number.

Try manually updating and let me know the results.

Best of luck Paul. Sometimes it can be difficult to get to the root of the issue since there are so many potential sources of the issue. If possible, could you provide the following:

Can you confirm that you are getting a 404 Not Found error rather than something similar such as a 403 error?

Can you provide a list of active plugins?

I was hoping that would not be your answer. That’s the URL that should be seen when installing or updating a theme, so there isn’t an issue of something sending off the request somewhere strange.

What remains is that something blocking the request. There are many things that this could be:

1) Your host’s network or server firewall (they sometimes see things like the word “upload”, get scared, and block the request).
2) A plugin, such as a security or caching plugin.
3) Web server or PHP configuration that blocks file uploads above a certain size.
4) Something else that I can’t think of.

The really odd thing is that most security blocks result in a 403 Forbidden error and that blocking requests that are too large should result in a 413 Payload Too Large error. Can you confirm that it was a 404 error and not some other kind of error?

It’s also possible that whatever is blocking access to that page intentionally is sending the wrong error code.

I know that this information isn’t very helpful, but unfortunately, I don’t have much to work with. Have you tried contacting your host about this issue? They might know the cause and have a solution. I recommend giving them the URL at issue and any other relevant details.

• This reply was modified 9 years, 3 months ago by Chris Jean.

No problem. Have a good day.

Hi Pippin. I think this report is meant for this plugin.

Hi André. This support area is for the Easy Theme and Plugin Upgrades plugin and not the Easy Updates Manager plugin. Support for that plugin can be found here.

I’m sorry for the confusion. The primary reason for the big change was that for many users, the plugin simply did not work. After working with some of the users, I found that the plugin had to alter many of the ways it worked in order to allow for these users to be able to use the plugin.

I found a couple of sites where the compatibility issue was triggered by modifying the pages where the theme or plugin file is selected (the pages that originally had details about upgrading and selecting “Yes” from the drop down). Since WordPress doesn’t have any hooks that specifically allow modification of the content on that page, my way of doing so was basically a hack that worked for most people. However, I confirmed from those users’ sites that it creates problems for others.

So, the only way to allow more people to successfully use the plugin was to make drastic changes to how the plugin functioned, including the removal of any modification to the pages used to select the theme or plugin to upload. I could have added a message and then removed it at a later date, but that would mean that those users would have to wait until that later date before they could use the plugin.

I wish that there was a way to fix the old problems without creating confusion, but in this case, that simply wasn’t possible.

The new 2.0.0 version no longer modifies the installer page. It now automatically handles identifying if the plugin or theme needs to be upgraded.

Please try upgrading a plugin or theme to confirm that things are working properly. You should see messages indicating that a backup was created and that the plugin/theme was upgraded successfully.