Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
As the title says I would love to know if it is possible to use the teaser break plugin with TinyMCE 3 via WYSIWYG API.
Comments
Comment #1
sunNot yet. It will in 6.x-2.x, after #319363: Rewrite editor plugin API has landed.
Comment #2
psynaptic CreditAttribution: psynaptic commentedOh awesome. Thanks for all your work on this.
Comment #3
mailme.eva CreditAttribution: mailme.eva commentedComment #4
nquocbao CreditAttribution: nquocbao commentedI will look forward to this feature. I'm using wysiwyg with fck and I can't create teaser.
I hope this will be finished soon.
Comment #5
xurizaemonIn the interim, you might want to consider a solution like CCK Teasers, so you can have a modern TinyMCE AND editable teasers.
Comment #6
sun6.x-2.x is already available. Closing this issue.
Comment #7
wouter99999 CreditAttribution: wouter99999 commentedToday I downloaded and installed the new version 5-1.0. But it seems that teaser-break plugin still does not work with TinyMCE 3, is that correct? wysiwyg.plugins.inc makes an exception for version 3. Would be nice to add a readme file in the plugin folder explaining things about plugins.
Comment #8
luvcatzzz CreditAttribution: luvcatzzz commentedI've create document to configure them.
Fix with this: http://www.bekatul.info/content/creating-teaser-break-drupal-6-wysiwyg-w...
Hopefully that's help.
- d
Comment #9
gbaudoin CreditAttribution: gbaudoin commentedYour walkthrough works perfectly, thanks !
Comment #10
sunSorry, but this is just plain wrong. All you need to do is to install Wysiwyg API 2.x.
Comment #11
luvcatzzz CreditAttribution: luvcatzzz commentedsun indeed correct for us to put the state of using version 2.x. but the state is still development. what i want to have when first trying to get the module is using the latest recommended status version and hope that it works. but this version is just not working, so to make a work around. people might want to tweak it on their own.
- d
Comment #12
rakugaki CreditAttribution: rakugaki commentedthanks luvcatzzz, works a treat if you don't want to use dev module.
sure there must be a reason it was disabled so your mileage may vary.
Comment #13
sunI don't know what makes you people mystify development snapshots. I even created a handbook page to explain that both 1.x and 2.x are working modules, none of them can trigger major bugs (because this is mostly a connector module), and 2.x will constantly be improved. We cannot create releases for 2.x, because this would add needless burden to the current development process.
I am using 2.x on all of my production sites, if that matters.
I wonder what I can do to clarify this even more.
Comment #14
kiwi_steve CreditAttribution: kiwi_steve commentedSun, I'm not sure why you are having a fit about this - luvcatzzz resolution worked for me after hours of fruitless searching. I'm not a code expert (to borrow someone elses expression, I'm a caveman coder - I find code and bash it with a club until either it works, or its dead :)
If there is a better way to get the
working, then please either post it here in clear detail, or post a link to it, but like I said, I spent literally hours searching and breaking things only to find this page eventually which resolved my problem.
I appreciate the hours and hours of effort that people put in to make Drupal what it is, and as someone who doesn't understand code at all I appreciate it when I find that someone else has solved my issue and posted the resolution... So thankyou Sun, and thankyou luvcatzzz :)
Steve