Hi,

Has anything been done so far to get tinyMCE ready for 5.0?

Thanks,

Jim

Comments

michaelfavia’s picture

I havent heard of anything but i depend on this module and im starting to move everything towards 5.0 myself. Is any interested in collaborating on getting this updated?

cbutera’s picture

I'm also wondering what the timeline or how much work it will take to update this module for 5.0

mosh’s picture

Title: Drupal 5.0 plans? » Patch for Drupal 5.0 beta 1
Version: master » 4.7.x-1.x-dev
Status: Active » Needs review
StatusFileSize
new7.54 KB

Patch for tinymce-4.7.x-1.x (4.7.x-1.x, 13/11/2006 - 01:15, 29.68 KB) to get it work with Drupal 5.0 beta 1.

umonkey’s picture

The patch applied clearly, but the editor doesn't show up. I get the "disable rich-text" link below the text area, but it doesn't do anything either. I have no idea on how to debug this. Did anyobody actually see this combination working?

tanepiper’s picture

Silly question umonkey, but have you downloaded TinyMCE from http://tinymce.moxiecode.com/ ?

tanepiper’s picture

Whoops, I spoke to soon - my apologies, as the last time that happened to me, it was because I hadn't uploaded TinyMCE to my server, just the module. But yep, all that's showing up is the 'disable rich text'.

When I click it, I get this JS error:

Error: this.settings has no properties
Source File: http://212.105.190.160/nhm/modules/tinymce/tinymce/jscripts/tiny_mce/tiny_mce.js
Line: 1
mosh’s picture

Please take a look at your 'page.tpl.php'.
This error comes up if you load $head before $scripts in page.tpl.php.

If i load $scripts before $head everything is working fine here.

<head>
  .
  .
  <?php print $scripts ?>
  <?php print $head ?>
  <?php print $styles ?>
  .
  .
</head>
tanepiper’s picture

Yea, I can confirm that fixes it :)

michaelfavia’s picture

I'll confirm also. However this is the default order of head, styles, script in the new default theme. Is this another issue or just an outstanding issue with tinymce?

mosh’s picture

it's a good question. However, at this time i don't know if the order of head, styles, script does matter, but i think it's not a huge problem. It seemes that there is no problem to change the order...

umonkey’s picture

Yes, this simple patch helps. I figured the problem with the order of javascript, but couldn't find a "legal" way to fix it, without interferring with the drupal core. In older 5.0 snapshots the order was fine, I think this issue needs to be reported elsewhere.

Thanks again.

ufku’s picture

StatusFileSize
new9.01 KB

i changed the patch a little.
package is now "Input helpers" to make it go under the same category with FCKeditor.
inline javascripts are added by drupal_add_js(). (no need to edit page.tpl.php)

umonkey’s picture

StatusFileSize
new9.54 KB

Thanks ufku, it works (although I had to use the "ignore whitespace" switch). I've added the description and capitalization to the admin page entry.

mosh’s picture

Status: Needs review » Closed (fixed)

Please follow up here: http://drupal.org/node/100864#comment-162236
Thanks