drupalbreak

Duh.. I'd used the tags in my last post's parenthetical and the site interpreted them. So, what I changed was:

--pagebreak-- to --break-- in the 2 .js files (I've left off the < and > to avoid the interpretation).

Eh, nevermind, that doesn't work either. See bug report here http://drupal.org/node/259737

Hi fred0,

I can certainly see the problem (which seems to also be a problem for the tinymce module), namely that the clever javascript in Drupal 6 does not take account of tinymce.

My proposal is to do 2 things:
- Disable Drupal6's javascript which creates the "Split summary at cursor" button and also splits a page when you load it. (I've no idea how to do this so that will be tricky.)
- Bundle a complete implementation of TinyMCE in with my module. This makes it a bigger download but should simplify setup. The reason for doing this is that I can modify the TinyMCE code so that the pagebreak button inserts a Drupal break (<--break-->) in the same way that you have done.

This should give the user a really neat way of specifying where the teaser break goes - just click on the button in the editor.

Do you think this would be a good solution? I'm interested in your views.

Steve

What about option 2 but instead of bundling a complete implementation of TinyMce, is it possible to just include the code which allows the entering of <--break-->?

Hi jk,

I've done just that - the latest development snapshop will contain:
- modified portions of TinyMCE
- code to disable Drupal's teaser break feature

Steve

Thanks!

Just checked by installing it, it replaces some of the files in the moxie tinymce package is that right? Is it supposed to be like that?

If possible, also help to release it as an official version if it is ready. Thanks!

Hi JK

Yes - the installation is meant to override part of Moxiecode's package. I don't particularly like this approach as it makes the installation more complicated (the very thing I was trying to avoid). That's why I hesitated to make an official release.

I still think my preference is to bundle tinytinymce together with a modified version of Moxiecode's software. That would make it a very simple installation package (just copy all the files in one go, set the permissions and it's working!)

Steve

Hmm... Think it is a good idea to bundle tinytinymce together with Moxiecode software because it would save the user the hassle of downloading it.

The latest release of the module now includes a full version of tinymce, with a small patch to handle Drupal breaks