Is there any way to force the use of the Enhanced Editor when in QE even if you have the Standard Editor selected as your default? That would solve my issue I mentioned 3 posts ago.

1. Admin CP >> Maintenance >> Execute SQL Query

2. Then from the drop down list, select Show Enhanced (WYSIWYG) Editor Toolbar

Also set this as the default for new registrations:

3. Admin CP >> Settings >> Options >> User Registration Options

4. Scroll down to >> Default Registration Options

5. Set Message Editor Interface to Show Enhanced (WYSIWYG) Editor Toolbar

Thanks djbaxter, although that will make everyone use the Enhanced as their default it will not prevent the standard editor from being used in QE if they select the standard editor after I ran the query. I need them to be able to use the standard editor if they choose but force the Enhanced while in QE no matter what they have as their default.


Hence my interest in this mod, I was thinking to force the Enhanced editor even if they choose the standard for QE.

Don't force users and don't make any changes in the modification, Just wait to the next version, All of theses things has already done in the next version, It's just I don't have much time to QA'ed it and release it.

Will do!! That's a whole lot easier. Thank you Marco! :)

Excelent, thanks !

Thanks, great mod, although I won't be using it because of the copyright text. I just modified templates manually and I have the same FULL EDITOR in my quick reply :)

Translation: You stole the code and edited it manually to avoid displaying the copyright, correct?

I don't mind the copyright, myself... but I did alter it to say "Advanced Quick Reply/Edit Developed By" rather than "Forum Modifications Developed By." Hope you don't mind too much--it's just that not all of my forum modifications were developed by you. XD

Marco1 i have set "Table Features" to yes and all the buttons are visible but greyed out in the quick reply, quick editor and the advanced mode.

Am i missing a setting somewhere maybe ?

*edit* never mind, it was my own fault.
I had "Message Posting Interface Options" set to "Standard Controls".

Sorry :)