Closed (fixed)
Project:
TinyMCE
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2006 at 19:04 UTC
Updated:
2 Dec 2006 at 11:03 UTC
Jump to comment: Most recent file
Comments
Comment #1
michaelfavia commentedI 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?
Comment #2
cbutera commentedI'm also wondering what the timeline or how much work it will take to update this module for 5.0
Comment #3
mosh commentedPatch 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.
Comment #4
umonkey commentedThe 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?
Comment #5
tanepiper commentedSilly question umonkey, but have you downloaded TinyMCE from http://tinymce.moxiecode.com/ ?
Comment #6
tanepiper commentedWhoops, 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:
Comment #7
mosh commentedPlease 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.
Comment #8
tanepiper commentedYea, I can confirm that fixes it :)
Comment #9
michaelfavia commentedI'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?
Comment #10
mosh commentedit'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...
Comment #11
umonkey commentedYes, 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.
Comment #12
ufku commentedi 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)
Comment #13
umonkey commentedThanks ufku, it works (although I had to use the "ignore whitespace" switch). I've added the description and capitalization to the admin page entry.
Comment #14
mosh commentedPlease follow up here: http://drupal.org/node/100864#comment-162236
Thanks