CMS Made Simple Forums

Hi

I'm using version 1.1 and everything's working great so far with one exception...

When I go to edit global content in the admin of my site, the TinyMCE editor controls aren't displaying right.  The same controls display fine when I go to edit pages.  It's interesting that I'm not having this problem on my local copy of the site.

Basically what it's doing is: instead of the buttons for Bold, Italic and Underline, it shows what appear to be Smarty tags like {lang_bold_desc}, {lang_italic_desc}, etc.  Also in the combo boxes that normally show Styles, Format, Font Family, etc.  I see more Smarty tags like {lang_theme_style_select}, etc.

Can anyone help?

I have been unable to recreate this problem, but there have been quite some fixes since the version included in cmsms 1.1. Please try out the newly released version 2.2.3 of the Tiny-module. One fix has also been made to the core, concerning wysiwyg. It's due in the upcoming 1.1.1-release.

best regards
Morten/Silmarillion

Hi Silmarillion,

Thanks very much for the response.  I upgraded to 2.2.3 as you suggested, but it didn't seem to make a difference.  Here is some more information that may help:

The problem is specific to one server running PHP Version 4.3.4 (It's Linux/Apache 2.0) and only occurs when I'm editing a global content block -- not when I'm editing content pages.  The problem seems to be that some of the javascript is not loading correctly because a null string is passed as the "language" parameter to tinyMCE.init

It seems that this parameter is passed in line 88 of tinyconfig.php in the following statement:

language: "GetPreference("live_language","en"); ?>"

I haven't been able to figure out where the GetPreference() function is defined.  The thing that puzzles me is how the same function call to GetPreference() could work fine when I edit a content page but fail when I edit a global content block.  In both cases, the source shows:





Best regards,
Dow/Agedman

Silmarillion,

You were right, version 2.2.3 fixed the problem.  I'm pretty sure I did the upgrade incorrectly the first time.

Thanks for the help!

- Dow/Agedman