Re-run set up when site is live

Insofar as your issue with moving the development folder, there's some good pointers and options within the thread below, take a read through.

https://forums.modx.com/thread/?thread=73954#dis-post-410673

Thanks, i don't use a development folder though. I installed everything at the root first time, running set up, and used ip-address/~username to view site and /manager to access modx backend. The cpanel account was named the same as the domain that would eventually point to this host.

I've been looking thru the post and links you provided, thanks, looks like i could learn / better understand this process using these. Another daft question?- I've just replaced all the files from my original modx zip file into my site, replacing all the modx files that where there. Now i'm running setup again, i chose english on the first screen drop down obviously, and on the next screen there's 3 options- New Insatallation, Upgrade Existing Install, & Advanced Upgrade. I'm guessing i choose the 2nd option- 'Upgrade Existing Install', this is right isn't it?

Yes, it's an upgrade (of sorts).

Ok,Brill, that's all worked and i was able to log back into manager without needing to clear browser cache. However, i notice the url's for each of the pages read domain.com/~username/index.php?id=20 for example, and i'm sure the username shouldn't be displaying in there. I've read that after running setup i need to fix 4 instances in the config.inc.php file which setup seem to miss.. is this what's causing the username to appear in the url, and is this something i need to amend before activating furls.

Fix the config.inc.php file, see what happens.

FURLS can be turned off and on at will. I don't think it matters if you do it before or after editing. It's only rewriting the filename, not your domain or directory unless you tell it to in the .htaccess file.

In .htaccess, leave the rewrite rule subdirectory blank since the install is in the root.

I am unfamiliar with developing a site with a temporary user folder like you did, sorry I can't help more.

Clear the cache too, you won't hurt the install and it might even solve your problem with the url's. Seriously, just delete the core/cache contents. Why do you fear this?

No, sorry, i did delete the core/cache content entirely before re-running setup. I totally get what you say about the furls, this is how i've activated them before. On the config.inc.php file, i'll just have to take a deep breathe and hope it's the right move.

make a copy of the original before you edit it. If it wonks, just replace the file and look to see what you might have done wrong.

One character out of place or missing can wonk it, look closely. It sounds like this might have happened when you did this the first time (possibly).

I'm nervous to make any amends to the config.inc.php file despite the fact i can backup that particular file. The only reason being, even though i did this the last time, replacing the original file seemed to make things even worse after i'd got it wrong the first time and then replaced that file back to original state. It's just these '4 instances' to change that i've come across in other posts, which say to 'fix them' but i'm not sure what that means. I may open another thread just to throw the net out and see if anyone knows what i might need to change here. I have to thank you again for walking me through the stages i've just carried out, especially since i'm inches away from having published my first revo site!

It's ok, just make a copy. If it wonks, replace the wonked one with the copy. FTP.

fine, here's the paste with the exact info you need.
found here:http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server

*****************************

Updating your Config Files

Once you've deployed files to the new server, you need to update the main configuration file: core/config/config.inc.php. You have to update paths to 6 different resources. Open the file and update the values for the following variables doing a find and replace:

/* PATHS */
$modx_core_path= '/path/to/modx_doc_root/core/';
$modx_processors_path= '/path/to/modx_doc_root/core/model/modx/processors/';
$modx_connectors_path= '/path/to/modx_doc_root/connectors/';
$modx_manager_path= '/path/to/modx_doc_root/manager/';
$modx_base_path= '/path/to/modx_doc_root/';
$modx_assets_path= '/path/to/modx_doc_root/assets/';
 
/* HOST (used for command-line PHP stuff) */
$http_host='yoursite.com';

If you are also moving your site into or out of a subfolder, be sure to update the variables such as $modx_connectors_url, $modx_manager_url, and $modx_base_url. They should generally
end with a slash (e.g., $modx_base_url='/' for a site not in a subfolder).
Permissions
Before you can edit your config file, you may need to loosen up the permissions. After you've edited it, be sure you restore the read-only permissions on the file.

There are also 3 additional configuration files that contain two PHP constants:

	
define('MODX_CORE_PATH', '/path/to/modx_doc_root/core/');
define('MODX_CONFIG_KEY', 'config');

/config.core.php
/connectors/config.core.php
/manager/config.core.php

Make sure you update the paths in these files as well.

[ed. note: frogabog last edited this post 14 years, 7 months ago.]