We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Glitch with TinyMCE plugin?

Development and Programming

Meir's avatar
Meir
80 posts
17 years ago
Meir's avatar Meir

I installed TinyMCE plugin on my EE install:

  • php 5.2.5
  • MySQL 4.1.22
  • EE 1.6.0 b20070815
  • LG TinyMCE extension v1.3

Installed fine, paths were fine, called the script fine (according to firebug), yet the fields in PUBLISH were coming up as regular textareas. Couldn’t figure it out for the life of me. With IE’s error console I found the problem- it was in this line of code, from the extensions settings page, in “TinyMCE Config”:

# content_css : '/themes/site_themes/default/styles/editor.css?' + new Date().getTime(),

Apparently the pound sign to comment out the line was killing the script. I changed that to // (two slashes) and it worked.

P.S. - Any idea why this would be the case?

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham
I installed TinyMCE plugin on my EE install: * php 5.2.5 * MySQL 4.1.22 * EE 1.6.0 b20070815 * LG TinyMCE extension v1.3 Installed fine, paths were fine, called the script fine (according to firebug), yet the fields in PUBLISH were coming up as regular textareas. Couldn’t figure it out for the life of me. With IE’s error console I found the problem- it was in this line of code, from the extensions settings page, in “TinyMCE Config”:
# content_css : '/themes/site_themes/default/styles/editor.css?' + new Date().getTime(),
Apparently the pound sign to comment out the line was killing the script. I changed that to // (two slashes) and it worked. P.S. - Any idea why this would be the case?

I’m guessing I was in PHP mode when I added that comment! The # is not a javascript comment and would be causing a script error. I’ll update the default install now.

Thanks for picking this up 😊

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Ok fixed and the download has been updated to 1.3.1.

Can you mark this thread as solved?

Cheers Leevi

       
Meir's avatar
Meir
80 posts
17 years ago
Meir's avatar Meir

woohoo I’m not crazy!

thx for the fix leevi

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.