@ruediger it sounds like you have a different problem, can you please create a new thread or open a chat where someone will be able to look into the specifics of your issue.
To the other new commenters asking about a fix, please see me first reply to this thread:
@nigela One problem here is that (at least these) WPML updates didn't show up on site management software such as MainWP etc. because they were not handled by the normal WP update process (why?), but instead require a manual check for updates. This is a major downside to your current update implementation and causes a fair bit of manual labour for someone managing many sites.
I, for example, scanned the sites for updates several times, even just a moment ago, in MainWP after your earlier email, but the sites showed no updates available so I thought you hadn't released the update yet. I had no idea that a manual check was required as this was not mentioned in your email, just that you'd be releasing an update.
@danielv-48@markusa-25@davidev-2 please see the first reply in this thread which details how to update WPML plugins if you experience this same problem:
@nigel thanks for the reference, however I thought my situation was different because wp-admin was still functional, while only the frontend lead to the fatal error.
I'm updating the main plugin to v4.5.12 but the activation first failed due to server error, and the second time is taking more thank 20 minutes and still loading. I wonder if anyone else is having this issue and can we do something about that or just wait, or cancel and try again?
Thanks
The topic ‘[Closed] Fatal error: Uncaught Error: Call to undefined method WP_Textdomain_Registry’ is closed to new replies.