WYSIWYG Editor Disapeared
 

Hello,

I have just upgraded from 4.1.5 to 4.1.6 and now my WYSIWYG editor is not displaying....

Any ideas on what may cause this, my members are already moaning :-(

Thanks for your help

Danny

Try disabling your modifications/plugins and see if you still have this problem.
Note: To temporarily disable the plugin system, edit includes/config.php and add this line right under <?php

If so, create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse the site using that totally default vbulletin style and with your modifications disabled - do you still have the same problem?

Also, did you check to see if it was, you know, turned off? :)

OK default style works fine.....

Not sure why that is though as the custom style has only had colour changes

Obviously it has more than that. Go to the style > Edit templates > and see if any templates show up in red.

Hi, I'm having a similar issue with my "custom skin" as well. And it seemed to have happened right after the 4.1.5 to 4.1.6 upgrade...

Posted at the forum where I got the skin from:
I even disabled all plugins and add-ons when trying the above measures. There were no style/skin file edits either. I tried finding some solutions and etc, but with no luck, have found a "fix". I'm at a loss...

QUICK UPDATE: Turning OFF the option to let users pick their own skin/theme seems to work. Also, AdminCP -> Styles & Templates -> Style Manager -> MYSKIN -> StyleVars -> ImagePaths -> imgdir_editor
Make sure the value is: images/editor
instead of: images/styles/MYSKIN/editor

Seems to help a little bit. But it's still weird that it would only work in the opposite chosen skin...

Thanks for the writeup, but the above doesn't work for me.

--------------- Added [DATE]1316169134[/DATE] at [TIME]1316169134[/TIME] ---------------

Found a fix:

Re-upload includes\functions_editor.php. from the 4.1.5 version.

You're welcome... :) If it's core code that's doing this, we best report it to vBulletin.com as bug then. I just figured I'd add to this thread here, thinking or hoping maybe someone had quick solutions... lol. But will give it a shot though! :)

--------------- Added [DATE]1316198648[/DATE] at [TIME]1316198648[/TIME] ---------------

I just tried this, it does in fact work! Yes!! :D :D Thank you! We best submit this bug to vBulletin.com lol

Already in there, but read the bug report and see that it may be working as designed since this is specific to certain configurations some users have set that may be incorrectly set. http://tracker.vbulletin.com/browse/VBIV-13156

Thank you Lynne... :) I've read it, and reuploaded the 4.1.6 includes/functions_editor.php file and tried some things with it.

Attempt 1:
I set the custom skin "CinemaFluid" as forum default skin for the board, set vBulletin's default skin for the two mobile settings. Enabled skin chooser/changer option for users. The editor is there for the "CinemaFluid" and "CinemaFixed" of custom skin. But it's not there for the vBulletin default skin.

Attempt 2:
I set the custom skin "CinemaFluid" as forum default skin for the board, set NONE for the two mobile settings. Enabled skin chooser/changer option for users. The editor is there for the "CinemaFluid", "CinemaFixed" of custom skin. And it's there for the vBulletin default skin.

According to what's said in the bug report comments, even if the two mobile settings are set at "None"... it would resort back to default skin anyway right? However, in this case, having the default vBulletin skin chosen for both mobile settings... The advanced editor is gone, but not in the custom skins when chosen in the forum... So the only way it works properly in all three skins, is to have NONE set for the mobile settings... Not sure if this is really correct or proper though either, because it should work with the vBulletin's default skin for the two mobile settings...?

I've replied to the ticket as well:
http://tracker.vbulletin.com/browse/...#action_123818