Just nuked my site

Hi guys

Trying to upgrade from 2.2.6 to 2.9 and stupidly overwrote my config file using an FTP app I wasn't familiar with.

I've found an old, outdated config file and am replacing the username and password values with the proper versions but I can't find out what the following should be:

$site_id =
$site_sessionname =
$https_port =
$uuid =

Any ideas?

Alternatively, I did ran a Vapor (MODX Cloud) on my site a few months back and have a transport.zip and a .pl file. Would my complete config files be in these somewhere?

Sorry, Vapor packages use the target site's config files.

Thanks Susan

Upon sound advice from FreelanceWebDev, I started from scratch and did a 2.2.7 upgrade rather than going from 2.2.6 to 2.9.

Site is now un-nuked and a radiation-free zone

And you have established a regular backup routine, I presume?

I do now
Ironically I have regular cloud based backups for my clients but not my own site.
What do you use for automated backups?
P

A slightly hacked version of bkupMODx

Or else, of course, the backup feature of the hosting company if they don't charge extra for it. I must admit, though, that the Cloud does make it amazingly easy to deal with.

It only needs one change, on the line where the config.inc.php file is loaded and scanned. Since it is basically a stand-alone PHP application that can be embedded in an Evo module or a Revo snippet (good for putting in the Dashboard) it can also be run as a cron job. Actually I see that the latest version doesn't even need to read the config.inc.php file.

It wouldn't take too much modification to make it fully Revo-aware, using the paths from the config.inc.php file to get to unconventional names and locations for the various directories. [ed. note: sottwell last edited this post 10 years, 8 months ago.]