When using WYSIWYG module, does it has a config file where you can set Drupal and Drupal Break buttons to be enabled (like the fckeditor module I think allows in its config file).
seems like the /plugins/break plugin is only coded for TinyMCE, true?

CommentFileSizeAuthor
#11 pagebreak.zip2.3 KBjenlampton

Comments

sun’s picture

Status: Active » Fixed

You need to use 2.x if you want to have a Teaser break button in both TinyMCE and FCKeditor.

jorditr’s picture

Where's the documentation to implement it? I've upgraded to the 2.0-dev release and the button is not on the list.

sdmaxey’s picture

For me, not only is there no "Teaser Break" button in the TinyMCE (which I take it is expected behavior in this version), but when WYSIWYG API is activated, the entire "Show Summary in Full View"/"Split Summary at Cursor" dialog is completely gone. It doesn't appear over the body field on the content creation field, even when I switch to a different input format--e.g, "Full HTML"

Is there any combination of modules at this point that can be used on a production site that will allow use of "Image Assist" and some level of control over the Teaser?

jorgesimon’s picture

Component: Code » Editor - TinyMCE
Status: Fixed » Active

Is there a way to get the buttons break and pagebreak back to TinyMCE using WYSIWYG API? Cause all solutions i've found so far are for earlier versions, so didn't work for me. Any workaround?

Thanks in advance.

guillaumeduveau’s picture

The Teaser break button works with WYSIWYG API 2.x-dev and TinyMCE 3.2.3.
You have to activate the Teaser break button in Buttons and plugins in admin/settings/wysiwyg/profile/edit/N where N is your input format used by default on your node-edit textareas.

sun’s picture

Status: Active » Fixed

Thanks, guix.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jenlampton’s picture

Status: Closed (fixed) » Active

That addresses "Teaser Break" but not the "Page Break" question in the title. TinyMCE had nice integration with the Paging Module that seems to have gotten lost in the push to WYSIWYG API. I think it was a TinyMCE plugin called "drupalbreak" that used to insert the page break tags.

What's the right way to get that into wysiwyg api? a wysiwyg_drupalbreak module?

Jen

guillaumeduveau’s picture

Yeah just copy teaser break, but maybe a module for this seems a bit too much ?

sun’s picture

Status: Active » Closed (fixed)

The Paging module should integrate with Wysiwyg: #269039: Provide WYSIWUG API module support for Paging

jenlampton’s picture

StatusFileSize
new2.3 KB

I also needed this for D5. I was able to get it working quickly by duplicating the break functionality for pagebreak and wanted to post this somewhere for others. unzip the attached and place the pagebreak directory and pagebreak.inc within wysiwyg/plugins. Must have Paging module enabled for the plugin to be available.

It would be better to move this into the pagebreak module for D5 (even though Pagebreak maintainers won't support new features in D5), but I was unable to find accurate documentation for hook_wysiwyg_plugin in D5. I'll open a separate ticket for that.

corbacho’s picture

Hi sun,
I just wanted to say that is confusing that when WYSIWYG module is enabled, the "Split Summary at Cursor" button is completely gone and only shows ""Show Summary in Full View" checkbox when creating new content (page or story)

I understand that can happen when you have a editor library installed, but when you still don't have anything, only WYSIWYG enabled, should still show the button.

corbacho’s picture

Status: Closed (fixed) » Active

I'm talking about Drupal 6.14 and WYSIWYG 2.0

twod’s picture

Status: Active » Closed (fixed)

Leaving the "Split Summary at Cursor" button there would probably cause conflicts and duplicate/lost teasers if an editor is activated later. If you don't have an editor library, you don't need the Wysiwyg module anyway. ;)

unfalln’s picture

Actually it's a valid point, as I don't want TinyMCE when I edit using the administrator-only PHP Code Input Format, but I do still want to have separate teaser and full-page. Perhaps this should be considered?

jenlampton’s picture

Yikes, please don't use the PHP Code Input Format. PHP in your database is always a terrible idea. PHP should go into files and be version-controlled. :)