fckeditor + drupal teaser break = problem

Before going any further, could you confirm that this bug still exists in 6.x-1.x-dev?
(remember to clear your browsers cache after upgrading FCKeditor module.)

Ups i missed that one important part:

I just noticed that if the option "Show disable/enable rich text editor toggle" is true (so the initial document opens in the split field, and the user switches to the editor by clicking on the link below), the problem cannot be reproduced.

I confirm that this is a bug.

http://drupal.org/node/240608

Not so fixed... The jquery looks for a value which isn't there for comments and so returns a browser error...

Removing the fix here; http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/fckeditor/f... and the problem goes away...

Pobster

Check the latest relese: 6.x-1.2-1 (hopefully it works this time).

Awesome, yep thanks works just fine.

Pobster

There is another problem that remains...

I installed the latest FCKEditor (Version 2.5) and Drupal-6.1 fckeditor.module (drupal-6-x-1-2.1). If you start editing a node with a teaser or create a new one with <!--break-->, then click to "Switch to plain text editor" and then back "Switch to rich text editor", the teaser disappears. Clicking "Switch to plain text editor" or submitting the node loses its teaser part for good. I guess another bugfix may be required.

--Ilya

Hmm I can't reproduce #9.
When I click "Switch to plain text editor" I get two textareas, when I click on "Switch to rich text editor" those textareas are translated into <!--break--> again.

Can't reproduce #9 either. This is on Drupal 6.2 with a freshly installed fckeditor module 6.x-1.2-1 and FCKeditor 2.6.

I still have the following problem with Drupal 6.2, FCKModule 6.x-1.2-1, FCKEditor 2.6: -

Worse yet, when the page is saved, the teaser part is simply discarded and lost with only the body part being saved, which essentially makes the use of fckeditor totally impracticable.

If you need any more info, please let me know and I will happily post it...

I have two separate sites running FCKeditor and on one I have the same issue as #13, but on the other no problem at all.

I'm wondering if its a conflict with other modules, or general drupal settings rather than something inside FCKeditor. I'm going to set up a test site locally and see if I can have any luck figuring this out.

edit:After some preliminary testing it seems to be a problem when using a custom content type. When I use the standard "story" node it doesn't lose the teaser. I'll see if I can track it down even further.

edit 2:Okay, so I was able to track it down to a 2nd FCKeditor field in my content type. I had a custom text field that was also using the FCKeditor, but once I disabled FCKeditor from that custom text field the teaser worked fine. Obviously this isn't a solution to the problem, but for me its livable.

I need a detailed list of steps to reproduce this or at least link to a site where I can look at this, tried custom content types with a couple of text fileds mixed with other types and couldn't observe similar issue.

I have exactly the same problem as described in #13 (teaser is discarded). The problem exists since I installed FCKeditor and is independent of the installed version (currently 6.x-1.3-beta). When I configure FCKeditor with 'Editor appearance' "disabled" and 'Show disable/enable rich text editor toggle' "true" and I edit a document with rich text editor switched on everything works fine and the teaser doesn't disappear. But as soon as 'Editor appearance' is "enabled" and I save the document or switch from rich text editor to html text editor the teaser is discarded again.
Additionally the bug depends on the content type. If it's a custom type, it doesn't happen.
If you want to login to my site to reproduce the bug, please let me know and I give you a user name / password.

Under IE I got different problem:
1) FCK profile:
Default state - Enabled
Show disable/enable rich text editor toggle - Disabled
2) Put 2 or more paragraphs of text
3) Insert teaser-break after first paragraph
4) Show summary in full view - checked
5) Push Preview

Preview of full version holds dubbed teaser and editor holds two teasers.
Suppose this all caused/depends by hiding toggle settings

Targeting to 6.2: #277657: TODO list for 6.x-2.x and 5.x-3.x.

The loading code has been rewritten completely and the teaser case has specifically been tested and works now.

Ok, so here's a trick - if I have FCKEditor turned on, I don't get the "Split summary at cursor" button, although I do see the "Show summary in full view" check-box. When I switch to the rich text editor, the button appears; switch back, it disappears. Is this a bug?? I shouldn't expect my users to understand this and switch to rich text just to create a summary....!

(btw, I'm using 6.4 with the latest release of FCK and the FCK module)

Issue posted in comments #21 and #22 is discussed in #303726: Split summary at cursor not showing up.

Yeah, sorry!!

I've got a similar problem with 6.x-1.3-rc1 and fckeditor 2.6.3: If "Switch to plain text editor" is disabled, nodes with teaser breaks are saved strangely:

<p>before teaser break</p>
<!--break-->
<p>after teaser break</p>

becomes:

<p>before teaser break</p>
<!--break-->
<p>before teaser break</p>
<!--break-->
<p>after teaser break</p>

- the teaser appears two times. And, if editing such a page, the main text disappears and I get this:

<p>before teaser break</p>
<!--break-->
<p>before teaser break</p>

exactly the same problem with #25

This problem had reared its head again for me. I thought I had fixed it.

How could I missed that? Arrgh

Anyone willing to give a try the latest version of fckeditor.module? It can be downloaded here:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/fckeditor/f...

The whole module will be available tomorrow as a dev release.

Marking as fixed, but I'm not 100% sure if that will work out in all configurations, please post your comments after you test it.

Three days ago I updated Drupal to 6.5, fckeditor .module to 6.x-1.3-rc1 and fckEditor itself to 2.6.3.
This combination had the bug as described by origaman above in #25.

Now I updated to fckeditor.module 6.x-1.3-rc3 and the issue is gone.
Thanks!