# The new Ghost editor (beta) - Ghost Changelog

**URL:** <https://forum.ghost.org/t/the-new-ghost-editor-beta-ghost-changelog/38984>\
**Category:** News\
**Created:** [June 6, 2023, 3:45pm UTC](https://forum.ghost.org/t/the-new-ghost-editor-beta-ghost-changelog/38984 "2023-06-06T15:45:00Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![r002](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/r002/32/24964_2.png) [@r002](https://forum.ghost.org/u/r002)\
**Post date:** [July 4, 2023, 2:58am UTC](https://forum.ghost.org/t/the-new-ghost-editor-beta-ghost-changelog/38984/39 "2023-07-04T02:58:07Z")

</div>

Thanks, @Cathy_Sarisky, for raising this bug. I wanted to just chime in that I unfortunately encountered this problem tonight as well. 🙁

 ![image](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/f/4/f4b9e08ce9cc1379c045b201577cb6484a08adba.png)

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 `.json`.)

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:

![image](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/d/f/dfd92d845b01e8df416d8368e81aa8fb2b26d174.png)

The problem is something in the `importer` itself.

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.

* * *

_Edit:_  
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_

---

_[View the full topic](https://forum.ghost.org/t/the-new-ghost-editor-beta-ghost-changelog/38984)._