Hi,
We would like some more information.
A. Are all your non-Yoast plugins and themes also updated?
B. If you go to SEO-General-Settings and scroll down to the Beta section. If you disable it does the issue resolve?
C. Are you using the new Gutenberg Editor or the Classic Editor?
D. If you check for JavaScript errors do any appear on that page in the backend? Can you describe them or take a screenshot? If you are not sure how to look for JavaScript errors please use this guide: http://kb.yoast.com/article/321-how-to-find-javascript-errors-with-your-browsers-console.
Thread Starter
tohop
(@tohop)
Hi,
thank you for your answer!
I think first I have to correct my error description: When I open a blog and press Save the blog will be saved since I get a “Post updated” message from Word Press. But the “save cloud” will not stop to blink and the save button is disabled. So I have to exit the page and open it again. Hope that clearifys it a bit!
Here is the information you asked for:
A. Are all your non-Yoast plugins and themes also updated?
Yes
B. If you go to SEO-General-Settings and scroll down to the Beta section. If you disable it does the issue resolve?
No
C. Are you using the new Gutenberg Editor or the Classic Editor?
Gutenberg
D. If you check for JavaScript errors do any appear on that page in the backend?
Proxy { <target>: {…}, <handler>: {…} }
post-thumbnail.min.js:23:12
Laden fehlgeschlagen für das <script> mit der Quelle “https://stats.wp.com/w.js?57”. notifications:19:1
Proxy { <target>: {…}, <handler>: {…} }
post-thumbnail.min.js:23:12
Proxy { <target>: {…}, <handler>: {…} }
post-thumbnail.min.js:23:12
Unhandled promise rejection
Response { type: “basic”, url: “https://dasbestezumschluss.com/wp-admin/post.php?post=1797&action=edit&meta-box-loader=1&_wpnonce=cf5ef00c42&_locale=user”, redirected: false, status: 403, ok: false, statusText: “Forbidden”, headers: Headers, bodyUsed: false }
wp-polyfill.min.js:2:29718
T/</n<
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:2:29718
[89]</n.exports
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:1:25719
T/<
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:2:29595
[51]</n.exports
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:1:16271
<anonym>
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:1:30590
m
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:1:30435
x
https://dasbestezumschluss.com/wp-includes/js/dist/vendor/wp-polyfill.min.js:1:30455
This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.
If you can install plugins, install “Health Check”: https://ww.wp.xz.cn/plugins/health-check/ On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.
Thread Starter
tohop
(@tohop)
Hi,
I have as proposed installed the health check plugin. I have disabled all plugins except the yoast plugin: Same result. As soon as I press “save” the cloud starts blinking, the save button gets disabled. And still the “Save post” message appears.
Any further ideas?
Rgeards,
Oliver
Thread Starter
tohop
(@tohop)
I did further tests and now I get this behaviour:
With all plugins / theme active except yoast and jetpack: No problem
Activate then either yoast or jetpack: The “trouble mode” starts.
I now discovered a sign which shows me that there is a problem: When I open a page or a block, the “update” button normally is disabled. It switches its mode as soon as I do a modification.
But when I am in “trouble mode” the button is enabled as soon as I open the blog/page. So maybe WP thinks in this case that there is a permanant change to the object and loops therefore endlessly?
Oliver
Hi Oliver,
We are not sure. It is odd that the issue happens with either Yoast or JetPack active. This suggests something else on your site (maybe WordPress itself?) is causing the error rather than just Yoast. If Yoast was causing the issue, it would only appear when Yoast is active and would not also manifest under another plugin.
We think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.
This thread has been marked as resolved due to lack of activity.
You’re always welcome to re-open this topic. Please read this post before opening a new request.
Thanks for understanding!
