Hi @cgscomputers,
which version of the plugin do you have installed after updating? Please make sure it is 4.2.1. And if you have Pro, it should be 1.0.7. And please make sure to clear you caches after having updated.
Do you have access to the error log for your server? Could you please send a copy of it to our support email address?
Please let us know so we can assist you further.
Hi, I’m using 4.2.1 and pro 1.0.7. I don’t think the Pro version matters as the issue seems independent of that – even when the pro version is deactivated and just the free version is running I have the issue. Caches of course emptied and completely disabled during troubleshooting to no avail.
The only server error message I can see (it’s reseller hosting so I have a very limited view) is an error that a custom 503 error page is not available. Nothing indicating the source of the 503 error.
In Troubleshooting Mode:
Used TwentyTwenty Theme with ALL plugins disabled except Molongui Free – posts pages load, main archive page is blank (this could be Troubleshooting mode’s response to a 503 error) but other archives appear to work, which is odd because both use the same template. If I just use TwentyTwenty with no plugins enabled at all – the main archive page loads just fine – as soon as I enable Molongui, it won’t load. In this state, other issues are impossible to check because the site is built with Elementor/Elementor Pro and with those disabled, many elements are not visible to check them – but as soon as these are enabled I can see other issues.
Rolling Molongui Authorship Free version back to 4.1.2 resolves all the issues.
Hi @cgscomputers,
what do you mean by “main archive page”? Is it the posts/blog page? Could you please provide the link to it?
Yes, the posts/blog page. I’ll send the link in a private channel through support – it’s not exhibiting the issue now though because I already rolled back to the previous version.
Hi @cgscomputers,
sure. We will post here the solution to the issue one it is resolved.
Just to let everyone reading this know, the issue reported on this ticket has been fixed in version 4.2.3.
Thanks so much for reporting @cgscomputers!