Hello,
I’m sorry to hear that you’re facing issues with saving metas in the Classic Editor. If the metadata is saving correctly in Gutenberg but not in the Classic Editor, it could be due to plugin conflicts or JavaScript-related errors.
To troubleshoot this issue, you can follow these steps:
-
Plugin Conflicts: There might be conflicts with other plugins causing the issue. You can check for plugin conflicts by following our guide on checking plugin conflicts.
-
JavaScript-Related Errors: JavaScript errors can also prevent metadata from saving. You can diagnose JavaScript errors by opening the Developer Tools Console Panel in your browser. Here are the steps to open the console panel in Chrome:
- Navigate to More Tools → Developer Tools from the Chrome menu.
- Click on the Console tab to identify any errors.
If you still face issues after checking these steps, please provide more details or open a support ticket with the error details so that our support team can assist you further.
Thank you for reaching out, and we’ll do our best to help you resolve this issue.
Sources:
Why Your SEO Title, Description & Focus Keyword Aren’t Being Saved » Rank Math
What Is a Slug in WordPress? » Rank Math
Hi there
I checked plugin conflicts. I only have RankMath activated and meta title/ meta description are not saving if I modify them. Not with Gutenberg editor, not with Classic editor. It is not a plugin conflict.
In Console errors on Chrome I find these errors:
/wp-json/rankmath/v1/updateMeta/?_locale=user 404 (Not found) api-fetch.min.js?ver…85334c5ec149cc:2
Uncaught (in promise) {code: ‘rest_no_route’, message: “Nessun percorso fornisce una corrispondenza tra l’URL e il metodo richiesto.”, data{…}}
Also I see:
{“code”:”rest_no_route”,”message”:”No se ha encontrado ninguna ruta que coincida con la URL y el método de la solicitud.”,”data”:{“status”:404}}
Hello,
Thank you for contacting us and sorry for any inconvenience that might have been caused due to that.
It seems like you have a redirection on this website that adds a trailing slash to all URLs and that is being triggered in the API routes as well.
That should not be applied to REST API routes but only to the pages and posts of the website. Otherwise, the functionality of the plugin might not work as intended.
To fix this, adding the condition line RewriteCond %{REQUEST_URI} !^/wp-json (exclude wp-json URLs) to your trailing slash redirect rule should work, The edited redirect will look similar to the one below:
#Add Trailing slash for end of the URL
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !^/wp-json
RewriteRule ^(.*[^/])$ /$1/ [L,R]
If you’re not sure, then you can get in touch with your hosting provider to do that for you.
Let us know how it goes. Looking forward to helping you.
Thank you.
Hi there,
Thanks for the answer. However, it did not solve the problem. Still not saving metas. I made changes, cleaned cache, but still not working. I managed to get more details of errors in the console:
Failed to load resource: the server responded with a status of 404 ()
wp-api.min.js?ver=6.5.3:2
n
apiRoot
:
“https://WEBSITENAME.EU/wp-json/”
attributes
:
{_links: {…}, namespace: null, routes: {…}}
changed
:
{}
cid
:
“c4”
requireForceForDelete
:
true
versionString
:
“wp/v2/”
_changing
:
false
_events
:
change
:
[{…}]
[[Prototype]]
:
Object
_pending
:
false
_previousAttributes
:
{_links: {…}, namespace: null, routes: {…}}
[[Prototype]]
:
n
valueOf
:
ƒ valueOf()
__defineGetter__
:
ƒ __defineGetter__()
__defineSetter__
:
ƒ __defineSetter__()
__lookupGetter__
:
ƒ __lookupGetter__()
__lookupSetter__
:
ƒ __lookupSetter__()
__proto__
:
(…)
get __proto__
:
ƒ __proto__()
set __proto__
:
ƒ __proto__()
changed
:
[[Prototype]]
:
Object
cid
:
“c4”
requireForceForDelete
:
true
versionString
:
“wp/v2/”
_changing
:
false
_events
:
change
:
[{…}]
[[Prototype]]
:
Object
_pending
:
false
_previousAttributes
:
{_links: {…}, namespace: null, routes: {…}}
[[Prototype]]
:
n
Hello,
In this case, we might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.
It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
We really look forward to helping you.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello,
We have excluded the wp-json route from the rewrite rule to add a trailing slash to the URLs, and now the metadata is saving without any issues.
Please check and let us know if you need our assistance with anything else.
Hello,
We are super happy that this resolved your issue. If you have any other questions in the future, know that we are here to help you.
If you don’t mind me asking, could you please leave us a review (if you haven’t already) on https://wordpress.org/support/plugin/seo-by-rank-math/reviews/#new-post about your overall experience with Rank Math? We appreciate your time and patience.
If you do have another question in the future, please feel free to create a new forum topic, and it will be our pleasure to assist you again.
Thank you.
