- This topic has 2 replies, 2 voices, and was last updated 10 years, 5 months ago by
.
-
Posts
-
In case anyone else has this problem…
I automatically hit update to version 4 on the main plugin and not the addons (as they didn’t have update facility) – this then broke our staging site with a 500 error. I should mention that I didn’t notice the helpful message at the top of the plugins page you guys had added warning about incompatibilities!
So I initially didn’t know what had caused this as was updating other things and had thought a failed update to Yoast had caused it. So this paired with a turd of a server and up and down net connection caused me about 45 mins of agro.
I had to download both addons and upload to the server – can this not be done automatically like the main plugin does, is there a better way of controlling the dependencies a bit better? – or is it not technically possible?
This is not a rant and I apologise if this is ‘old knowledge’ but I thought it might assist anyone else who encounters similar problems but also just make you guys aware of the 500 error, I’m sorry I can’t give more detail about the error as the server doesn’t currently output logs anywhere that I can find yet.
Cheers for a great plugin, keep up the good work!
Hey Laura and thanks for reaching out!
Geez, I’m so sorry about that. The auto-update should indeed work and, in fact, just did when I tested it. I think the difference was having the existing add-ons deactivated when I did. That ensures any incompatibilities between 3.x and 4.0 are moot and provides the server with more capacity to perform the update.
I should mention that I didn’t notice the helpful message at the top of the plugins page you guys had added warning about incompatibilities!
That’s a solid point. We’ve done a lot to communicate the warnings here on the site as well as in our newsletter and social media, but I can see how having an additional warning (like the way WooCommerce does it) would be helpful. I’ve ticketed this in our system for us to look into for a future release to avoid this from happening again.
Again, sorry for the trouble during update and thanks for your feedback–this really does help a lot and I appreciate you sharing this with us here.
Did you have any other questions? Please let me know and I’d be happy to help as we best I can.
Cheers,
Geoff
- The topic ‘Update to 4 gives 500 server error’ is closed to new replies.