Grandfathered account. I pay for custom domain. Suddenly can’t save posts.
-
Get this error “Updating failed. Could not update the meta value of jetpack_seo_noindex in database.” Support suggested
“You do not currently have a paid plan, but you are grandfathered into the old system that allows you to run a custom domain on a free site. Your domain, which you are paying for, is separate from your hosting plan. Please open a thread on our forums to have this issue investigated further.”
However I do pay $13 a year for custom domaoin.
The blog I need help with is: (visible only to logged in users)
-
I upgraded the account and still get the error to the pro plan “Updating failed. Could not update the meta value of jetpack_seo_noindex in database.”
-
Appears to be specific to the post https://wordpress.com/post/whatisprogress.com/868 but other draft posts can be edited saved and
-
-
I’ve copied content to a new post and this seems to resolve the issue. The original post does not show in my list of posts at all any more. luckily I kept the tab open
-
Hi there!
I’m sorry to hear about the issue you faced. We were unable to replicate the issue on our end, and as you mentioned, it doesn’t seem to occur on new posts. So, I’m not really sure what caused it, but please let us know if this happens again.
Thanks!
-
I just started a migration from Substack to WP and am getting this when I try to add a paywall to imported posts.
-
I also have this issue but am not on a paid account (and haven’t been for over a year) – only one post is subscribers-only, I cannot update it due to the error “Updating failed. Could not update the meta value of jetpack_seo_noindex in database.”
-
Hello, I am having the same issue. Whenever I try to update a blog post published before the domain change, I get this notification: “Updating failed. Could not update the meta value of jetpack_seo_noindex in database.” Please advice on how to resolve this issue.
Best,
Kemi -
Hi there,
This is a known bug that we are looking into currently. I have reported this thread to our developers and once the issue is resolved, we will let you know.
Several people are saying that as a workaround, copying the post content using the code view, and pasting it into a new post entirely allowed the content to save/publish as intended. I’d recommend trying that for now to see if it works.
Thank you and sorry for the inconvenience. -
I’m getting the same issue, an error in red that reads ‘Updating failed. Could not update the meta value of jetpack_seo_noindex in database.’
It seems to be happy to save updates in the main body of a post but is affecting any footnotes – updates to footnotes are not always retained, sometimes there are more footnotes showing in the draft than in the preview and some are blank. Has been like this for several weeks now.
-
-
I am getting the same issue. My issue seems to be related to footnotes. Was fine until I added them. Was about to copy the whole thing and create a new post so glad that is the suggested workaround.
-
Hello, suddenly having the same issue with updating a blog post that initially published successfully.
-
-
Can confirm as original issue poster seemed related to footnotes.
Wonder if anyone is going to fix this? -
I also am having this problem when trying to insert new citations into an older post. Is there any timetable on the fix for this?
-
@staff-doublebassd if this issue is not resolved are we entitled to a refund on the rest of our publishing package. I add new citations to my work as new studies come out all the time and the workaround is not sustainable.
-
- The topic ‘Grandfathered account. I pay for custom domain. Suddenly can’t save posts.’ is closed to new replies.
