This plugin is a next generation block styled editor. Its workspace consists of separate Blocks: paragraphs, headings, images, lists, quotes, etc.
Classic WYSIWYG-editors produce raw HTML-markup with both content data and content appearance. On the contrary, the plugin outputs JSON object with data of each Block.
Levon, just bought this, very cool. Can you explain how to save content to the database? I am not able to save anything, not through action or auto-save. Thanks!
René
@levon I had a look through the documentation again although can’t seem to find any instructions of how to actually store the data. I did see in tour demo you load through search which works for me as well when copying in the json from your demo.
Thanks for helping out. This will be very useful for a new version of Teeming.
Hello @rene, I hope you are doing well so for saving data to the database you have to enable autosave checkbox in Editor properties than you have to set up your event for saving, it may be button click for example. So I create two buttons to demonstrate to you how to save data from EditorJs with the creation of new items and updating the old one. Firstly - the creation action workflow you can find here, the second action workflow you can find here.
@levon, I’m running into an issue when refreshing the editor to set new content. In my application, there are templates users can select, and then when they select the template it adds the body of the template to the modular text & docs editor.
You need to have your database data (templates that users can select) formatted as a JSON code. The Modular Text & Docs Editor plugin works only with the JSON. So, if you want to use the data from your database or input field (like on your second screenshot), you need to have it formatted differently.
The example of this you can see on our demo page (editor):
to display the data from the database, within the plugin element, you refer to the database table - Screenshot by Lightshot
The Initial Content field is working, but you need to set it rightly - the data, you are corresponding to within the Initial Content field, should be in a JSON format also (just like it is shown on our demo page/editor). https://www.loom.com/share/204f2e6af119433c8a82476db59491a6
To make your plugin work correctly within your app, you need to change the content format of your database table to JSON. Would you kindly check out our plugin editor/demo page and make sure it is working properly under the correct setup?
Also, I can suggest you take a look at our ZQ Rich Text Editor 2.0 plugin. For this plugin, the data does not need to be in JSON format - it can work with plain text too, and it has pretty much the same functionalities:
Please check out its demo page/editor and documentation first, to make sure it can be useful for you.
Please let me know if I can help you somehow more
Regards, Kate
Hello @sewar37895,
Please accept our apologies for the late reply.
I’m afraid, we’ve not discussed this. But, I have passed it to the developer team for consideration. Once any news will become available, I will let you know.
We’ve updated the plugin and adapted it to the new responsive engine. Kindly ask you to upgrade your plugin to the latest version (1.11.0.) and give it a try.
Indeed, the plugin element does have a limit of 650px. Even if we try to set it to 100% width, the content inside will still be displayed as 650px. I’ve passed this to our developers, as soon as I have any news I’ll get back to you.
