Problem with tinyMCE

I don’t know if this has been solved (I also hope this is the right place to post this)

A friend of mine has a site that is built with modx evo 0.9.6.3 and his old developer is no longer around,

I have been trying to work out what the problem is and whether on not I should update, as well as how to update it, if that proves to be the solution.

The thing that is currently causing trouble is that TinyMCE has stopped appearing in the editor window and this is how my friend updates his site (he doesn’t know anything about code or html).

Currently TinyMCE (3.2.0.1) is installed, as I recently discovered some of the older JavaScript editors can stop working (or appearing) in newer browsers. I don’t know if/how this plug-in can be upgraded by itself without upgrading the rest of the cms, as I want to create a local version of the site first to ensure that nothing inside the templates break when upgraded.

Any help you can offer or if you can point me in the right direction, will be much appreciated.

Thanks in Advance,


Michael

You should most definitely upgrade the site.

Is that a hard thing to do?

With a version that far out-of-date, here’s how I do it:

1. Back up the whole site, database and all.

2. You did back up the site, right?

3. Download the latest version and unzip it on my local machine. Rename the top-level files and folders, adding .new to the end of each one’s name (index.php.new, assets.new, manager.new, etc).

4. Upload all the new stuff.

5. Copy files/folders like your images folder, the js folder and the templates folder (and any other folders you may have added to or modified, or custom snippets, plugins, modules etc.) from the old assets folder to the new one. Copy the manager/includes/config.inc.php file to the new manager/includes folder.

6. Log in to the old site, clear the cache and empty the reports. Log out, and make sure your browser cache and cookies are cleared for the domain.

7. Now the site goes down for a few minutes. Rename the original files/folders to add a .old suffix to them all. Rename the .new files/folders to remove the .new suffix.

8. Run the installer in upgrade mode. Be careful to make sure you don’t install the demo content! If the installer doesn’t allow upgrade mode, make sure the config.inc.php file has been copied to the manager/includes folder and is read/write. You can change that to read-only after the upgrade.

Now check your site; some of the snippets may have changed how the parameters work, and you may need to tweak some of the snippet calls. Also check the plugins to make sure the OLD ones have been disabled, and you’re now using the NEW ones (once you’re sure all is well you can delete the old ones). You might have to empty the site cache file (assets/cache/siteCache.idx.php), go to the Configuration and save it to rewrite the cache file.

I’ve never had this fail, but if it does you can quickly rename the files/folders and restore the database from your backup and recover the site within a few minutes.

I take it I should be upgrading to the latest evo and not to revo?

Right. Moving to Revo is another story; it’s doable but not pretty.