I've read others are having or have had this problem, some seem to get it resolved... not me so far.

I tried updating to the latest version of TinyMCE but ran into a problem that is discussed here http://drupal.org/node/695398

I've never patched a module before so I decided to simply install the latest version to tinyMCE 3.3, which was 3.2.7. So, I have the latest version of WYSIWYG and TinyMCE version 3.2.7. The admin/settings/wysiwyg/profile/ installation instructions section is showing that TinyMCE is installed correctly with a check mark. Other plugins (image assist) are available... but I cannot for the life of me find any sort of plugin selection to check that will offer me a <--break--> option. I've read some people have actually edited the code, others say that is not required...

I installed WYSIWYG with CVS, and have run "CVS update" from the WYSIWYG directory, and the following is returned:

cvs update: Updating .
cvs update: Updating better_formats
cvs update: Updating better_formats/tests
cvs update: Updating better_formats/translations
cvs update: Updating editors
cvs update: Updating editors/css
cvs update: Updating editors/js
cvs update: Updating patches
cvs update: Updating plugins
cvs update: Updating plugins/break
cvs update: Updating plugins/break/images
cvs update: Updating plugins/break/langs
cvs update: Updating plugins/fckeditor
cvs update: Updating plugins/fckeditor/dynamictoolbar
cvs update: Updating po
cvs update: Updating translations

I have also run cvs update -dP DRUPAL-6--2-0 and nothing is returned.
But the module status reports that WYSIWYG is up to date... So, I'm not sure what else to do with this... Is there something I should be doing with any of the files in sites/all/modules/contrib/wysiwyg/plugins/break/ ?

Thanks for any help on this. Getting this working would save endless grief trying to explain to a specific user how to switch from the rich text filter to the html filter...

Comments

twod’s picture

Status: Active » Fixed

I've not seen anyone have problems with enabling the Teaser Break plugin for a long time so I'm a bit surprised by this issue.
The update listing only shows that the folders are there (tho some are now empty and would be pruned with the -P flag). I can't tell what revisions the actual files are, but if the Teaser break plugin does not show up in the [bottom ] of the list, something's wrong. If you accidentally checked out HEAD you'd get in trouble because it is currently adapted for D7, and it would probably throw errors here and there if it was forcibly enabled for D6. It shouldn't be possible to enabled it in D6 tho, so I'm not sure what's wrong. The status page only checks which version is installed from the .info file, not if every other file matches the release.

If you want to run the stable 2.0, I suggest using the pre-packaged release as it makes sure the correct revisions of files are there.
If you have a reason for needing to check it out from CVS, use the -r flag to set the revision: -r DRUPAL-6--2-0 when checking out. As you've already got a checkout, you could run cvs update -dP -r DRUPAL-6--2-0 and it should switch all your files to match the 2.0 release.

You should never need to modify files in the module or an editor library just to get it to work. We always try hard to avoid having our users modify the original files because it makes updating the editor and module harder.

Once Wysiwyg 2.0 is correctly installed the Teaser Break button should show up near the bottom of the list.
If it doesn't, please reopen this issue and detail the exact steps you did during Wysiwyg installation.

kpm’s picture

Thank you TwoD.
I now see the "Teaser Break" choice in the button selection list. The text is not blue in colour like the other plugins in the link, but it is there. I checked it and saved, but I don't see any added buttons to the editor. What I did was as you suggest, updated with the -r switch... I then went back to the WYSIWYG editor config and it was blank... So I went to the status page and saw some errors. So I disabled and re-enable the WYSIWYG module to resolve that. Then I noticed the installation instructions had different paths than previous, so i moved the TinyMCE directory to the new location in /sites/all/libraries/tinymce and that made WYSIWYG plugins installation happy, the TinyMCE section has a green check mark next to it. But, I still don't see any sort of "insert teaser break" button or link...
Thanks again for the assistance.

twod’s picture

Status: Fixed » Postponed (maintainer needs more info)

Ah, sounds like you had an earlier version of the module, looks like you've got the module itself set up correctly now.
The Teaser Break option is simply not blue/(a link) because it has no 'more info'-URL assigned to it. Its icon in the toolbar should look like two white pages with a light blue and dashed line between them.

Are you seeing any JavaScript errors after the editor is loaded? Which browser(s) have you tested with?
Have you tested with just the Garland theme and the Teaser Break button enabled? (Some themes don't print the $closure variable so they don't add all the scripts to the page).
Could you check with Firebug for FF, or a similar too for other browsers, that the break.js file is loaded along with the editor?

kpm’s picture

Status: Postponed (maintainer needs more info) » Fixed

ok... got it going. I checked the admin/reports/status and all looked well, except for the Date module, which mentioned I should have the Jquery UI module installed. I thought I already did intall that module and enabled it (because I read that warning before). So, I re-enabled that module, then I ran update.php, then went back to see if the 'teaser-break' icon would appear. And now I know what it looks like... and it works. Thanks.

What I've learned... use the -r switch when updating modules with CVS. I use CVS to maintain sites simply to make maintenance quicker and easier. So whenever the status page tells me I have a module out of date, I navigate to that directory and tell cvs to update it. So, now I know the status report is only looking at the module.info file, and if that is not updated, and other parts of the module are, status will not inform me of this... So I should probably spend some time updating modules with the -r switch.

Thanks again TwoD

twod’s picture

You will only need the -r switch when changing from one branch/tag to another (or for first-time checkouts) as it's status is "sticky".
Hmm, I'm not sure why installing that module helped, but hey, life's strange sometimes. ;)

kpm’s picture

I suspect it was running update.php... not sure why (cache clearing and what not). I should have done one at a time rather than both at the same time... but, I'm glad its all working now. Thanks again.

Status: Fixed » Closed (fixed)

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