Is the rich text editor on for them? If so, try completely removing TinyMCE, deleting all files in the core/cache directory, and reinstalling it.
upgrading or moving a site from development to live server is a simply horrible and very painful even with the current version of modx. I cant even tell you how many times i've resorted to just performing a new install and MANUALLY adding all my pages and resources to the manager just to prevent having to deal with all the errors and issues related to trying to upgrade or move my install.
Realistically speaking, modx gurus, how difficult would it be to have a backup/restore? Is there something in the pipeline?
...i agree, the docs sound straightforward but i'm having no end of problems upgrading here, so painful I'm now faced with rebuilding the site I'm trying to upgrade...great cms, but i'm so frustated it's soul destroying...
...after all it's encouraging to upgrade for security reasons and encouraged by modx to upgrade...part of me wants to upgrade, but the other part of me says i don't have 8 hours or a weekend spare in case of server problems...so now i just don't bother which is a shame really.
-
☆ A M B ☆
- 3,141 Posts
It's funny, cause I personally rarely have any issues running upgrades, while for some who use the same exact procedure it never goes right.. I can't make heads or tails out of it where it goes wrong.
The instructions in the docs are pretty thorough in listing any troubles that may happen.
After backing up, of course, the quick instructions are uploading all the files (merging, not overwriting ie deleting existing files), running setup and be on your way. What are called "minor" releases (2.1 -> 2.2) may have some things that break existing functionality (eg from 2.0 -> 2.1 the long deprecated DBAPI was removed, and 2.1->2.2 had some minor changes in actions, UI, auto-minification of js/css and file handling) which may need to be addressed manually, usually simply by updating 3rd party components / extras.
When moving installations there are some paths here and there that need to be updated. Most are in core/config/config.inc.php and depending on your installation there is a path in config.core.php files in /manager/, /connectors/ and the root of the site. As of 2.2.1 the path in the modx_workspaces table (which was updated by setup before) has been made relative to the {core_path} variable again, and Gallery has also seen its absolute paths deprecated and replaced with variables evaluated during runtime.
If there are any specific issues with updates it's important to find out where it gone wrong and see if it's an exception that needs to be handled in the core, if the server is incorrectly configured or if it's simply a gap in the documentation or the person's knowledge that we need to address. A smooth process start to finish is a big priority and if we can identify where it goes wrong, we can try to make it easier for everyone involved.
My experience has been the same as Mark's. The only times I've had any trouble, clearing the browser cache and cookies took care of it.
I suspect that these are server issues, but they've been very difficult to track down, especially so since the core developers are on well-configured hosts.
Bear in mind that you can back up an entire site in about 15 minutes and restore it in the same amount of time if you have trouble with an upgrade and can't fix it easily.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
