Closed (won't fix)
Project:
TinyMCE
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 May 2007 at 21:42 UTC
Updated:
3 Feb 2013 at 19:53 UTC
I get the following errors when I reply to comments with tinymce enabled in IE
Line:1
Char:81
Code:0
Error:'tagName' is null or not an object
URL:http://vpc-srv5/comment/reply/1
and in firefox I get
tinyMCE.baseURL has no properties
http://vpc-srv5/sites/all/modules/tinymce/tinymce/jscripts/tiny_mce/tiny...
Line 1
and
fE has no properties
http://vpc-srv5/sites/all/modules/imce/imce_set_tinymce.js
Line 10
If I disable lightbox I do not get any errors.
Comments
Comment #1
stella commentedWhere did you get the scriptaculous and prototype js files from?
Comment #2
stella commentedI can't reproduce this with the normal (non-compressed) tinymce files and no plugins enabled.
Comment #3
H3rnand3z commentedAfter some more testing I realized that the conflict is with IMCE 5.x-1.x-dev and Lightbox2 5.x-1.1 If I disable either IMCE or lightbox the error goes away. I will do some more testing with a clean install
Comment #4
H3rnand3z commentedAfter some more testing I realized that the conflict is with IMCE 5.x-1.x-dev and Lightbox2 5.x-1.1 If I disable either IMCE or lightbox the error goes away. I will do some more testing with a clean install
Comment #5
stella commentedI've only been able to reproduce the 3rd error you've listed. I think these errors occur due to a conflict between the 3rd party prototype.js file, that you have to download to run with the lightbox2 module, and the tinymce 3rd party code. I think it might be a conflict between two "extend" functions. I don't know where or why but data from the prototype.js module end up in the tinyMCE.instances array.
This appears to only cause a problem when the imce_set_tinymce.js file, which comes with the IMCE module ,tries to access the instances array. I think the addition of a simple check to line 10 of this file to see if fE is defined would solve the 3rd error. Well it'd be a workaround. The real fix is to figure out where the extra data is getting into the tinyMCE.instances array.
I'm not sure which project this issue should be reported against. It's probably one for all 3 project groups to solve. I'm going to keep investigating the issue but am going to move it to the IMCE queue so they're aware of the problem and can hopefully help us find a solution.
Stella
Comment #6
ufku commentedthe line starting with settimeout... was added to fix a bug in tinymce before version 2.1. if you use the version 2.1 or above you dont need that line. feel free to delete it.
Comment #7
H3rnand3z commentedIE works ok after I removed setTimeout line from \sites\all\modules\imce\imce_set_tinymce.js but in firefox I still get
the tinymce toolbar does not display, The only time the error goes away is if I disable Lightbox.
Comment #8
ufku commentedthen it is a problem between tinymce and lightbox.
Comment #9
stella commentedI'm not sure where this error occurs. I can't reproduce it and am also finding it hard to follow the tiny_mce.js code since it's all on one line. Can anyone else help?
Stella
Comment #10
H3rnand3z commentedI will try and duplicate this on a clean install.
Comment #11
gemini commentedThese are the errors Firebug reports in Firefox for me:
Comment #12
stella commentedgemini: see comments #5 and #6 for a solution to the fE error.
You could disable the Lightbox2 Plus option on the lightbox2 settings page. This will enable Lightbox2 Lite and you shouldn't have any conflicts with tinyMCE.
Stella
Comment #13
gemini commentedThanks Stella. But then grouping is not working anymore and (i have a lot of photos in groups) and nice resizing effect with the option to see in original size doesn't work either.
Comment #14
stella commentedYeah I'm afraid they're all lightbox2 plus features. I'll have a look and see if I can implement them for lightbox2 lite.
Comment #15
gemini commentedStella,
what if you made a workaround in Lightbox that would check if TinyMCE is on, than it would turn off the Lightbox, or just not load the JS (that could be as an option in administrative menu - on/off kinda thing). Mostly TinyMCE is needed when users edit or add content, and Lightbox is not needed at that time. Do you think it's a dumb idea?
Comment #16
gemini commented..actually would be much easier not to load lightbox js on "add" and "edit" pages without checking for tinyMCE (I guess)
Comment #17
stella commentedsimilar issue in #152860
Comment #18
stella commentedTry the patch from #166461 (comment #2) which will allow you to specify individual pages on which the lightbox javascript should not be loaded.
Cheers,
Stella
Comment #19
stella commentedlightbox2 5.x-2.x released which now uses jQuery instead of prototype and scriptaculous libraries. This should fix any conflicts between these two modules.
Cheers,
Stella
Comment #20
(not verified) commentedComment #21
rohangupta commentedI am getting the following error when i am trying to put tinymce on the text area:
Line:1
Char:81
Code:0
Error:'tagName' is null or not an object
As seen in the posts above commenting the line setTimeout in imce_set_tinymce.js does not help because then i start getting the error of "Invalid source HTML for this operation".
Please help.
Comment #22
pomliane commentedThis version of TinyMCE is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.