cappu Hello, On Joomla 3 and Joomla 4 I do get Error 500 on upgrading from v8.3.0 to 8.4.0. Reloading the backend pages works and AcyMailing 8.4.0 PRO seems to be installed. I haven't investigated any side effect, yet. Any ideas? Kind regards, Bernhard [Edit] Reinstalling v8.4.0 seems to work
Dax mollcons Hello, could you copy-paste the error message please? I can't read it in your screenshot. This is the message at the top of the screenshot mentioning a file and a line number Or if anyone can share the error message, for those that don't have the Joomla debug mode enabled you should be able to find the real error message in the server logs. Thank you!
mihha Hi, thank you for reporting the issue. Our developers have already been alerted about this issue and are working on a solution. You can work around this problem by manually uploading the latest installation package using Joomla Installation manager. I just tried it on the test site and by doing that, I was able to upgrade without an error during the upgrade. Thank you for your understanding!
smash91 Bonjour Meme problème sur 2 site des test en chargeant la package d'installation par Joomla Manager Joomla 4.2.9 Acymailing entreprise 8.4.0 PHP 8.1.9 Cordialement
Dax We released a v8.4.1 that should fix this error message during the update, thank you for reporting this 👍🏼
cappu Thanks for the fix. On some installations it works, on other I do get this error on a blank screen, now: {"message":"NOT_FOUND","data":[],"error":true} The URL is: /index.php?option=com_installer&view=install [Edit] The displayed version is v8.4.1, anyways
mollcons This error has now occurred on two sites I am updating this morning. When looking back at the updated AcyMailing modules, the main module does now display as 9.7.0, but other plugins are showing very old versions. Is that OK?
jvstratum mollcons The other plugins will be updated as soon as you visit the Acymailing dashboard. You can safely ignore the 500 error, Acymailing will function normally. We are working on a solution to prevent this from happening again. Nex time, please be so kind to start your own thread. You replied to a very old thread with a different cause of the 500 error. Your issue it's not related in any way to the topic of this thread. Thank you for understanding.