Re-run set up when site is live

Hi,

I've just built up a site on a temporary domain (ip.address/~username/manager) using modx revo 2.2.0pl for the first time. The site was ready to go live (client domain pointed to cpanel host account), and i activated seo furls. However, i didn't realise i was supposed to re-run set up again before doing this, and i think this caused the site's url's to look like ip.address/~username/seo-furls-here.html instead of how they should read, using the site's real domain. After making changes to the config.inc.php file, it wouldn't save, something went wrong and the site disappeared. My host carried out a roll back of my host account to 15 hours previous which restored the site back.

So second attempt at this, and i just want to double check, making sure i'm about to follow the right steps here-

1. If i re-run set up, this won't affect the site i've just built up, templates, docs, chunks, users, permissions etc.

2. In re-running set up, i use all the exact same details as when installing modx revo the first time round, such as passwords, database etc.

3. Is there anything else i need to do? I have read that re-running set up misses 'instances' in the config.inc.php which i need to amend (approximately 4-6 lines by adding the site's domain name in). My worry here is, last time i changed this file and hit save, i think i got an error message. Either way, the site never displayed again after that.

& the point of these above steps is to get the website domain to appear in the browser as opposed to ip.address/~username?

Once the above is successfully carried out, then i can activate seo furls which i manage to do quite easily..

You don't have to set database and user when re-running setup. You can re-run it any time you like, it is like doing an upgrade. Just copy/overwrite all the files in the install zip file to your site, it includes a setup file.

Then run setup in the browser http://yoursite/setup. It will take all of 30 seconds to do this. In your other thread, it was suggested many times by some very important and knowledgeable people to do this. You should believe them.

Re-run setup as many times as you like, whenever you like. It's not going to ruin the site. That would be counter-productive.

Thanks, i took on board the response covering this topic on another post i made but some points here wheren't mentioned there, and i guess i'm just wanting to make sure. The support is great and has helped me to develop my first (of many?) modx site.

So basically, in the zip file i have (containing modx 2.2.0pl), all i need to do is use ftp to drop all the contents into my root folder again, replacing all the existing files, and then run setup.

Thanks again

Yep. I also recommend that you delete the core/cache folder's contents. I'd do it before running setup personally but afterwards should be fine too (if you've already run setup).

Ok, it's little details like that i haven't found out about yet, so i'll do that as well. I'm supposed to clear cache and flush permissions beforehand as well, is that right? What is the purpose of deleting the core/cache folder contents?

Just log out of the manager, flushing isn't really necessary.

Clearing the cache isn't required, but when you're having issues like you are it's a good way to help solve them. I just recommend it, at some point before you load up the site in a browser to check it. As soon as you load the site, the cache is rebuilt. I suppose that is the point, to re-build the cache.

Ok, Cheers. And sorry if this is a daft question, but i just located the core/cache folder located at the root of my host, and it appears to contain many files and other folders like includes, lexicon, setup, scripts etc. You say i need to delete all the contents of this folder before i copy/replace over all modx files again from the modx 2.2.0pl zip file? (& then run the setup)

(& just to ask, what is the purpose of deleting all these files)

You don't need to do it, but if there's something wonking the install from before, it's a good way to make sure it won't return because a setting or whatnot is cached in there somewhere.

You can delete the cache any time in this way. Similar to doing it within the manager, but it clears everything out and starts anew.

This method of clearing the cache can be helpful when you can't get in the manager to clear from within. It's ok, just delete the files. It won't do anything but rebuild it in short order.

Quote from: jaykaye at Mar 28, 2012, 01:06 PM

(& just to ask, what is the purpose of deleting all these files)

Purpose is to clear the cache and have it rebuilt. That's all. We do this regularly so cached site settings and files are cleared (get used to it). Every save you make does it within Revo, and more often than not... when something is wonky in the manager or site, clearing the cache will fix it. It should be your first choice when debugging wonks. When you post here with an issue, you'll be asked almost every time if you cleared the cache as a first step. Of course, after you're asked what version you're running (if you don't note it in the original post).