Thank you for your attention. In the last post I fixed, I was getting this error.
Interesting. Does the .json for that particular post have both a mobiledoc and a lexical entry? Or does it look ok in the json but clearly isn’t after importing? I’m wondering if this is problem with the import code or the export code.
I have the json saved. If you want to download it to study I can make it available.
Ahha. I just managed to reproduce it. Will strip it down to the simplest possible repro and then file a bug.
How nice that you were able to reproduce it
Well, it’d be nicer if there was no bug, but it’s a whole lot easier to get a reproducible bug fixed.
Update: I don’t think it matters which editor you have active when you try to import. Does that match your experience? It’s that lexical posts don’t import correctly (and are bugged in a way that they cannot be edited), but editor setting at the time of import doesn’t appear to matter.
I’m quite enticed to give it a try, but I think I’ll wait about a year before starting to use this editor. The current editor is already a decade ahead of WordPress, so I don’t see a compelling reason to experiment with something in beta that carries the risk of causing issues or disruptions.
Thanks, @Cathy_Sarisky, for raising this bug. I wanted to just chime in that I unfortunately encountered this problem tonight as well.
And yes, to your question: it didn’t matter which editor I had toggled at the time of import. If the post was initially written in
lexical, then it simply won’t import correctly. If it was initially written in
mobiledoc, then everything works fine.
My specific workflow is I actually create posts on my localmachine, make sure they look like I expect (especially because I’ll sometimes tweak the theme too) and then when I’m happy I’ll export from my local machine and import that
.json onto my Ghost(Pro) instance (and a new corresponding theme, if necessary). (Also, on my Ghost(Pro) instance, I always do delete everything before importing the new
The workaround right now is to just make sure all of one’s posts and pages are written in
mobiledoc, I guess? Like you said in your GitHub issue, the actual
json I’m importing is correctly formatted and
mobiledoc is indeed set to null:
The problem is something in the
I’d already written about half of my posts and pages in
lexical but I’ll go back now and manually convert them all into
mobiledoc. Am hoping this bug will get fixed soon though! As it’s definitely a dealbreaker that makes
lexical not possible in my current workflow.
I’m adding the actual error message in text so SEO can actually find this post:
Validation error, cannot edit post. Posts can have either a mobiledoc or a lexical property, never both. Both the mobiledoc and lexical properties are set, one must be null
How can I activate the stickers feature? I just purchased the license, the integration was activated, but the stickers option is not available in the editing tools.
In the photo editor, the sticker option is on the left (1). Once selected, upload your sticker image (2).
I have the self-hosted version of Ghost, and I uploaded the files listed on the integrations page. Still no sticker option appears, or is there an extra step required?
Ghost version: 5.53.4
Node version: 16.13.0
SO: Ubuntu 20.04
@RyanF Do I have to edit any part of the pintura-umd.js or pintura.css file and upload it again?
May I ask how you convert
mobiledoc? I have the same issue right now.
@Jun_Mao With a lot of elbow grease! I’d literally gone through manually post by post, selected all text, copied, and pasted into a new post (after I’d disabled the
lexical editor in the
According to @Cathy_Sarisky though, the bug appears to be fixed now! So I think it’s no longer necessary to jump through all of the hoops I had. (I’d just been on a deadline at the time and needed to get all of the posts exported from my localhost and imported into my Ghost(Pro) PROD instance, which is why I’d brute-forced it.)
In any case, thanks for the update, Cathy!
Cathy can you give me any docs on doing this? Would this require theme edit?
Since I said above that I wasn’t sure what you meant when you said you wanted popups (in the Ghost editor?), I don’t know what exactly you’re asking for docs on…
Sorry, learning how to build pop ups in Ghost. Is this a 3rd party solution ?
I thought I’d spend a few moments on Google and found the following two options
Code Snippet:- Simple tips for creating ghost notification popups
Third party option which is free to 5,000 page views/month, then $390 annual for 100,000 views/month and there are more higher tiers. It works using an embed code (you design the pop up at the provider’s url and the code you copy from there and inject in your site calls the info from the provider url):-- Ghost CMS Popup Builder Tool for Free | Popupsmart
These two were so easy to find, there’s likely lots of options out there. I spotted, but did not review, several YT vid tutorials on the topic.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.