What's weird about this error is it's only affecting a single node on a fairly large site:
When I disable the editor, the source code is there in the textarea but the text editor (TinyMCE) doesn't seem to like it (in Firefox at least, Chrome works fine). Enabling the rich text editor causes the error to repeat:
Error: regular expression too complex
Source File: http://nnwo.org/misc/jquery.js?i
Line: 12
Has anyone else ever seen this before? I can't for the life of me figure out what's causing it and why only for just that one node.
Comments
Comment #1
sunCan you post the source HTML text that's contained in the textarea?
Comment #2
seanrIt was just this:
Comment #3
mygumbo commentedThis is happening with our site too.
-- it's only a small subset of the nodes (2 found so far)
-- nothing displays in the body textarea (except the background color), but disable rich text and the source is there
-- mac firefox and mac safari show this behavior, but pc chrome and even pc ie8 display ok
Comment #4
hctomI also get this errors now... and after som research:
This seems to be a bug in Firefox 4/5
https://support.mozilla.com/en-US/questions/797123
Comment #5
twodI was able to reproduce this, especially with invalid XHTML markup (#2 has a missing / in a br tag, #3 has uppercase tags and other symptoms of being previously mangled by IE), but like hctom said, this appears to be a browser issue and I can't find a reliable workaround for it.
Comment #6
mygumbo commentedSafari shows this behavior too.
Comment #7
jeffschulerI was experiencing this too. Couldn't save the node and couldn't disable rich text [seeing regex error] without switching to Filtered HTML Input Format first.
I found that there are characters in the markup that look like spaces that aren't really spaces, but are rather the character with ASCII code 8232.
If you look through the markup posted in comments #2 and #3 here, you'll find the same character, though it just looks like a space.
I stripped those out and was able to save the node.
Comment #8
twodLooks like this is a browser problem triggered by invalid markup or perhaps encoding issues. I don't think we can work around this in Wysiwyg itself so I'll close the issue.
If anyone is able to find out more and perhaps even find a workaround, please reopen the issue. We'd be really grateful!