New forum text editor - When to migrate?
JuliusBorisov
Member, Administrator, Moderator, Developer Posts: 22,758
Vanilla’s Advanced Editor for text formatting is soon to be a legacy product, and is being replaced with a new Rich Editor. We understand text formatting is very important for our forum users and would love to hear your feedback.
At this time, the new editor won’t allow users to edit the source of their posts and advanced users (who like to add their html via copy/paste, or like doing code stuff) may find frustrations as the new editor does everything for you, and you may not be able to copy/paste html code as easily.
Read about the new text editor here and here.
This change will happen, the question is when. We want your feedback on that. This poll will stay active for 2 weeks, and then we’ll make a decision based on poll results and community feedback.
At this time, the new editor won’t allow users to edit the source of their posts and advanced users (who like to add their html via copy/paste, or like doing code stuff) may find frustrations as the new editor does everything for you, and you may not be able to copy/paste html code as easily.
Read about the new text editor here and here.
This change will happen, the question is when. We want your feedback on that. This poll will stay active for 2 weeks, and then we’ll make a decision based on poll results and community feedback.
- New forum text editor - When to migrate?28 votes
- We should migrate once the Rich Editor is out of beta.67.86%
- We should migrate when the problems caused by the legacy editor become overwhelming.32.14%
2
This discussion has been closed.
Comments
In the document via the first link in the original post, it shows:
Rich Editor can function side by side with Advanced Editor. Leave Advanced Editor enabled in addition to Rich Editor, and older posts will still be editable using Advanced Editor.
Does this mean we can have both, or does it mean something else? I'd like to have both, as I think most people would also like to have. I like the idea of more emojis, but not being able to use HTML is a severe atrocity. That's why both options should be provided, and it would be better if Vanilla provides cross-compatibility between the two text-editors, or at least add HTML support for the new Rich Editor.
That being said, if a change is inevitable, it's best to have it soon.
What about the Activity page comments? Now that we'll be having an improved text editor, does the Activity page get a revamp? Since HTML never worked there, does it mean this new editor can assist us in formatting and adding emojis, links and images in the Activity page comments?
I'm here for the words mostly, everything else is just frills. Nice frills at times, I admit, but at the end of the day it doesn't matter at all to me. Maybe this is closest to option 1 though?
The new editor supports both BBCode and Markdown (Yes!), so everyone, even HTML hardcore fans, should be happy.
If it's possible I would propose to add a toggle that allows you to choose between Rich Edit or one of the available source format modes mentioned in the linked document (Markdown, BBCode or HTML).
But if the tool is going to be changed anyway I suggest the bandaid methodology. Just get it over with.
TR
<i class="Italic">Example</i>
and have it show up as Example. It will still show as<i class="Italic">Example</i>
.I don't think any forum text editor would be so improperly made as not to allow anybody to edit their posts at all. So don't worry, you will still be able to edit your posts.
See https://forum.bubble.is/t/vanilla-rich-text-editor-beta-5-update-themes/19099/2 for example (mind that those are old images).
from https://forum.bubble.is/t/vanilla-rich-text-editor-beta-5-update-themes/19099/28