I'm really trying to get som attention to this issue, as it seems that many have the same problem.
If I publish an article, and uses the "break" button in FCKEDIT, the article aperars ok. If I ever try to edit this article it's destroyed. All text is replaced by one more ingress/teaser. The ingress/teaser shows both over and under the red "break"-line. If I save, and edit once more, the teaser aperaes TWO times under the red ingress/teaser line. It does not go further then this. It will continue having three teasers nomatter how many times I edit it.
In the beginning this only happened to my users, and it worked for admins. I found out that the "Administer nodes" rights was the key. If I grant my users this permission FCKEDIT works.
The downside is that "Administer nodes" rights give my users the ability to publish and edit any type of content, so I can't keep it like this. Hope the info helps in finding a solution.
I am now running a high risk site because my users can edit, delete, and mess up every article they want, because of my temporary solution.
I REALLY need a solution here...
Thanks!:-)
Comments
Comment #1
wwalc commentedDoes it happen in a garland theme? Does it happen if you edit page content or is it some custom content type?
Hmm this problem sounds a bit strange.
Comment #2
JeschMB commentedhi,
i've the same problem. it seems that this depends on the os or browser version. i can't reproduce the error with a linux system and firefox but a windows user does.
after saving and reedit the article the teaser appears twice in the FCK text field with the teaser break each.
Comment #3
wwalc commentedConfirmed (unfortunately).
Comment #4
Mac Clemmens commentedconfirmed this is the case in both FF3, IE6, and IE7 for PC.
For me, it seems to happen regardless of permissions. It has something to do with the way the two boxes (one for teaser, one for body) get automatically combined. My guess is that it's caused by code related to the "Show summary in full view" functionality, forcing it to merge that content into the body region. Note that regardless of whether or not that box is checked, the teaser content gets prepended to the body each time.
Hope this helps!
Comment #5
wwalc commentedI think I have found this bug. Please download the dev release tomorrow (dev release from 2008-Dec-05) and reopen this issue if you're still experiencing this bug.
Please test it tomorrow and confirm whether this bug has been really fixed. Remember about: http://drupal.fckeditor.net/troubleshooting#6
(alternatively you can download the FCKeditor module from CVS (6--1 branch))
//Edit: 6.x-1.x is in 6--1 branch
Comment #6
qbnflaco commentedI found this same bug with the 6.x-2.x version. Is this dev version also fixed or should I downgrade to 1.x?
PS. Firefox 3 and Safari 3 on mac have the same issue.
Comment #7
wwalc commented@qbnflaco - are you sure you have upgraded to 6.x-2.x? What does Drupal say when you visit admin/build/modules section? Is it really 6.x-2.x-dev?
I'm asking because the part of code that was invalid in 6.x-1.x does not exist in 6.x-2.x and I can't reproduce it...
Did you remember abut possible problems after upgrading: http://drupal.fckeditor.net/troubleshooting#6 (clear cache etc.)?
Comment #8
qbnflaco commented6.x-2.0-alpha3 is the version I am currently running. updating to the latest dev should fix it?
PS. This was a clean install. I haven't updated yet.
Comment #9
wwalc commented@qbnflaco - definitely please try the latest dev release, a couple of nasty bugs have been fixed recently.
Comment #10
JeschMB commentedit still happens in the latest dev : doubled teaser when edit
Comment #11
wwalc commented@dynamiser: did you use the 6.x-1.x-dev? Are you sure you have cleared the browser's cache?
I had a plan to release rc6 in a couple of hours but after sawing your message I've decided to postpone it until your problem is solved. Please let me know whether clearing browser's cache solved this problem.
Comment #12
JeschMB commentedis used 6.x-2.x-dev (2008-Dez-12).
i tried 6.x-1.x-dev (2008-Dez-12), and the last fckeditor(2.6.3) with success everthing works fine now, sry for confusion
Comment #13
wwalc commentedActually even 6.x-2.x-dev should be working fine, however it's good to hear that 6.x-1.x-dev is performing well. Thanks for rechecking it.
Comment #14
wwalc commented