Upgrading MODX questions

Hi,

I have just been asked by a friend if I can help upgrade his version of modx as his website has crashed and he was told it is due to the modx version being outdated. I can't login to the website manager as when I attempt to it lists errors but will not actually login, so I am unsure how to check what version of modx the website is currently running. I can access the website files via ftp. Is there a way to check the version through one of the files located on the server as I see from researching there are different methods of upgrading dependant on versions.

Thanks for any and all help.

Updating rarely fixes a crashed site. A crashed site most likely means corrupted database tables, or a corrupted cache.

Look in the files to see if there is a core directory and/or connectors directory; if not then it's an Evolution site. The index.php file will also say something in the leading comment section if it's Revolution; not sure if Evolution does.

Specific version information should be in the cache files, if Evolution it'll be in the main assets/cache/something.idx.php file (not the sitePublishing.idx.php file). If Revolution, it'll be in the core/cache/system_settings/config.cache.php, the 'settings_version' line.

Thank you very much for your reply and the information. There are not core or connector directories present so it must be an Evolution site. It's running version 1.0.5 I'll do some research into your suggestions of corrupt database tables or a corrupted cache unless you have recommendations or ideas on them.

Thanks again

If it is Evo, then the installed version could be found in system_settings table of the database.

Most Evo sites are not crashed these days because of a corrupted database or cache. Often it is a PHP version issue. 1.0.14 is compatible with 5.2-5.4. ManagerManager needs 5.3+ as far as i know. Versions before 1.0.9 are compatible with PHP 5.3 and less.

And in the worst situation the crashed sites is hacked …

Thanks for all your help guys. I completed an upgrade to version 1.0.14 and everything seems to be back up and running.