Hi Sixes,
Can you try 1.4.1? Thanks!
I just discovered the same problem with my Dashboard after updating to 1.4 earlier today. Replacing it with 1.4.1 solved the issue. Thanks!
So is it working for you? Can this topic is marked as solved?
1.4.1 is not working for me, it crashes both the backend as well as the site itself, resulting in blank pages.
@alpha_de did you update from 1.3, or from 1.4.0?
I had already trouble after updating to 1.4 (empty page on config page of bwp sitemap and errors when accessing the sitemap), now
Class ‘BWP_Sitemaps_Handler_Ajax_NewsTermsHandler’ not found
is in the log.
And in the instance where I can access the dashboard, the news remain empty.
These were the 1.4.0 errors
sitemapindex can not be served because of a missing module file: sitemapindex.php.
post_bwg_album can not be served because of a missing module file: post.php.
@alpha_de were you Andreas who also contacted me via email? It seems that your update to 1.4.1 is incomplete. Can you check if news-terms.php can be found in <root>/wp-content/plugins/bwp-google-xml-sitemaps/src/handler/ajax ?
I suggest that you download the plugin in zip file here: https://downloads.wordpress.org/plugin/bwp-google-xml-sitemaps.1.4.1.zip and then upload it manually using FTP to make sure no file is missing.
I am… news-terms.php is present in that instance.
OK let’s not hijack this thread, we will continue our discussion via email.
Thread Starter
Sixes
(@sixes)
So is it working for you? Can this topic is marked as solved?
No, I meant I was already on 1.4.1 when the problem occurred. IN any case, a plugin that crashes 1.4.0 is hardly “solved”.
No, I meant I was already on 1.4.1 when the problem occurred. IN any case, a plugin that crashes 1.4.0 is hardly “solved”.
Hmm when you started this topic I had not released 1.4.1 yet.
The same issue mentioned in this topic is mentioned in other topics too, and people seem to have success with 1.4.1, for example: https://wordpress.org/support/topic/140-ms-admin-lockout?replies=8 . Perhaps you should try removing the plugin entirely and install a fresh 1.4.1.
Thread Starter
Sixes
(@sixes)
Hmm when you started this topic I had not released 1.4.1 yet.
OK, we’re at cross purposes and I apologise. I was referring to the WordPress version, yes I know that’s 4.4.1, not 1.4.1 but I’m easily confused.
I have now tried version 1.4.1 of the plugin (with version 4.4.1 of WordPress) and I’m pleased to say it works fine. Thank for your prompt fix and for producing the plugin. Apologies again for causing confusion.
