response back from the MyBB community. If i can get them to realize this error i hope to have it fixed in MyBB 2.0. A lot of customization is default for MyBB 2.0 including a lot of pugins.
So far one suggests to try a different editor via a plugin. This could have some other side effects that i wouldnt really know until after installed....such as the return of WYSIWYG editor and maybe no option to turn it off, our custom python/error/output/spoiler and other buttons that are already existing in this editor might have to be redone completely in the next editor or possibly conflict at all with both plugins (not sure), And not sure if upon re-implementing the current editor if the other one sucks or does not work as expected, would return to exactly as it is now (AKA no conflict with custom BBCodes, etc.) And the whole editor idea might not be the issue at all.
My opinion is the possibility of mucking up the editor worse than it is now is high in changing the editor. And that it is not a high enough priority to be worth hassling about it.
But ill leave it up to you guys. Ill attempt an install of various other editors to try get rid of this issue if everyone wants it.
I got into the habit of using real time posting as my previews. And then i edit the post to fix it up or add a couple sentences like i did with this post. So i dont ever get this problem like other do.
EDIT:
For the record at this current time there is no longer WYSIWYG editor. There is an option in your UserCP but it is overridden hard coded to disable it for everyone. If you copied code over that had formatting you would see the formatting now via BBCode such as [ b ] tags instead of it actually being bold in the editor. But you would still need to paste as text to get rid of the formatting depending on where you copy it from. This should also get rid of the HTML code in the codebox and now you would just see [ b ] tags instead.
EDIT2:
Screw it. Added a plugin for a new editor to try to fix this problem. You can post bogus stuff testing it out or real issues here
So far one suggests to try a different editor via a plugin. This could have some other side effects that i wouldnt really know until after installed....such as the return of WYSIWYG editor and maybe no option to turn it off, our custom python/error/output/spoiler and other buttons that are already existing in this editor might have to be redone completely in the next editor or possibly conflict at all with both plugins (not sure), And not sure if upon re-implementing the current editor if the other one sucks or does not work as expected, would return to exactly as it is now (AKA no conflict with custom BBCodes, etc.) And the whole editor idea might not be the issue at all.
My opinion is the possibility of mucking up the editor worse than it is now is high in changing the editor. And that it is not a high enough priority to be worth hassling about it.
But ill leave it up to you guys. Ill attempt an install of various other editors to try get rid of this issue if everyone wants it.
I got into the habit of using real time posting as my previews. And then i edit the post to fix it up or add a couple sentences like i did with this post. So i dont ever get this problem like other do.
EDIT:
For the record at this current time there is no longer WYSIWYG editor. There is an option in your UserCP but it is overridden hard coded to disable it for everyone. If you copied code over that had formatting you would see the formatting now via BBCode such as [ b ] tags instead of it actually being bold in the editor. But you would still need to paste as text to get rid of the formatting depending on where you copy it from. This should also get rid of the HTML code in the codebox and now you would just see [ b ] tags instead.
EDIT2:
Screw it. Added a plugin for a new editor to try to fix this problem. You can post bogus stuff testing it out or real issues here
Recommended Tutorials: