-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random <p> and </p> tags in post editor pages #5
Labels
legacy issue
Legacy issue imported from original repo
Comments
Comment by johnclause I see that some extra unmatched |
Comment by johnclause trunk now has a version 2.9.7b available for testing |
Comment by johnclause 2.9.8.0 has a fix. |
Closed
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue by johnclause
Wednesday Jan 14, 2015 at 02:16 GMT
Originally opened as qTranslate-Team/qtranslate-x#5
Theme: any, "Twenty Fifteen" would do.
Plugins: can be qTranslate-X only, I do not think it is a compatibility problem with other plugins.
At least two languages, for example, en and de, to be specific.
Steps to reproduce the problem:
<!--:en-->EN<!--:--><!--:de-->DE<!--:-->
, which is normal.<!--:en--><p>EN</p><!--:--><!--:de-->DE<!--:-->
, where EN was the active language at time of pressing "Update". This part is kind of explainable, TinyMCE embraced active text with<p></p>
, although it does not do so, when plugin is deactivated.But then something really strange happens:
<!--:en--><p>EN</p><p> </p><!--:--><!--:de-->DE<!--:-->
<p><!--:en--><p>EN</p><p> </p><p><!--:--><!--:de-->DE<!--:--></p>
Pay attention that
<p>
and</p>
do not match anymore.Further clicking “Update” does not modify this text anymore.
I have been printing various variables on java console, but those
<p>
did not show up anywhere I looked so far. I have no idea how they get into the database.If people consistently keep editor at "Visual" mode, they apparently do not notice a problem. Nobody complained about this yet, but we'd better to clear it out before somebody does.
P. S. I first discovered this in the original qTranslate, and I thought that after cleaning the code, it will go away on its own, but it did not so far.
The text was updated successfully, but these errors were encountered: