The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Editor box not visible in Firefox 33
I just noticed that from last few days there is drop in activity and found that I new Mozilla firefox is the culprit as text editor is not visible in it, neither in full post nor in quick reply. Its working in opera, chrome etc.
I have to disabled enhanced editor and WYSIWYG editor from AdminCP to fix this problem temporary. Any idea what could be causing this problem suddenly.. its VB 4.2.2 PL2 |
#2
|
|||
|
|||
My Firefox just updated to 34, maybe you should update and see if that fixes it.
ETA: Otherwise, try Ctrl+Shift+J to look at the console and see if here are any javascript errors. |
#3
|
|||
|
|||
Just got my FF also upgraded to 34.5 on restart , I guess this update is being rolled out and now box is visible but only basic text editor, no matter what I set "basic" , advance" or wysiwyg editor.
I tried using sql and also from admin CP --------------- Added [DATE]1418588284[/DATE] at [TIME]1418588284[/TIME] --------------- I guess it was too soon to say anything.. Now on Opera it is showing WYSIWG editor but on firefox and chrome, showing basic text editor and console is giving error: Code:
SyntaxError: syntax error ...){var k=null,l=i[j]?if(!l.name&&!l.id)continue;if(t}peof arguments[0]=='string' ckedito...T&v=422 (line 8, col 1154) ReferenceError: CKEDITOR is not defined ...this.unescape_text(this.textarea.value);this.isSafari=CKEDITOR.env.webkit&&navig... vbullet...s?v=422 (line 11, col 777) 1:46:12.662 CSI/tbsd_/ |
#4
|
||||
|
||||
I think Kevin is probably right. You most likely have a JavaScript error on your web site. Have you tried disabling all the hacks that you have installed and re-enable the editor to see if its one of the hacks causing a conflict? There are some hacks that deal with the editor that DO cause problems for it to not show up or act strangely. Try a global disable.
In your includes/config.php find: Code:
<? Code:
define('DISABLE_HOOKS', true); Then enable your editor(s) again and see if that clears the problem up. If so then you will need to to disable each hack one by one until you find the culprit. To do that just open your includes/config.php file again and replace: Code:
define('DISABLE_HOOKS', true); Code:
//define('DISABLE_HOOKS', true); |
#5
|
||||
|
||||
If that don't work, try on a unmodified default style, it could very well be some code you entered into a template.
|
#6
|
||||
|
||||
This is true forgot about that.
|
#7
|
|||
|
|||
Thanks for input, I will test with above suggested methods and will update here .
|
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|