Moving modX to different hosting

Hi all!

I've been developing a website on my machine locally and everything went great. Now the time has come to move it and make it accessible to the whole world!
But that's where I'm stuck. I've followed a guide (http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server) step by step but unfortunately to no avail.

I've noticed that some things are different in the guide than they are for me. For example, the guide mentions to update the config.core.php files:

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');

But when I open up these files they say something different:


Also when updating the workspaces in the database the guide makes it look like there should be a relative path to the core folder, except when I open it up it says "{core_path}".

I did update the config file in the core folder (and to my knowledge I did that correctly), but when I go to the manager it says:


And when I try to re-run the setup it's giving me three errors:


Does anybody know what I've done wrong?

Details:

• PHP 5.3.27
• MySQL 5.5.34
• ModX 2.3

Hi

Did you change the configuration setting in modx manager site_url? this config value needs to be changed before you go ahead and move the site.

also have you checked the .htaccess file for any paths relating to the unc path to the website i.e you may find something like c:\wamp\htdocs\website\ rather than the path in the new hosting environment i.e /var/www/domain/

also clear all the contents out of the core/cache folder and delete all your local browser cache. [ed. note: comp_nerd26 last edited this post 11 years, 11 months ago.]

Hi

I've disabled the .htaccess file by renaming it to ht.access. Also, I checked it and it doesn't make any reference to the old environment. And yes, I did clear the cache folder.

But I'm not sure how to change this site_url config value as I can't login to the manager. Can I look this up in the database perhaps?

have you tried re running the setup with the upgrade option?

also check that the folder permissions are 0775 reoccursive for the following folders:

core/cache/
core/export
core/packages
core/components
/core/config/config.inc.php (file)
assets
setup (if the folder exists)

Why 0775 instead of 0755?

I've tried to run the upgrade option, but then it's giving me errors on not being able to find certain folders, even though they're there.

Of course those folder are writeable and accessible by the server (I've triend 755 and 777). What's even more strange is that it can't find the public_html folder, but can find core/cache folders.

The paths for those 3 are wrong by the looks of it, shouldn't it be /home/sandyv85/.....

Check the paths in the core >> config >> config.inc.php [ed. note: paulp last edited this post 11 years, 11 months ago.]

Thanks for your reply.

I've tried that, but then I end up with this error message:



I've changed the paths from:
/domains/sdekroon.nl/public_html/core/
to:
/home/sandeyv85/domains/sdekroon.nl/public_html/core/
Which results in the error message above.
(This is an example, I did change the other paths too)

it looks like that one of the config files is still pointing to the old location.

found an article that might help you
http://wiki.modxcms.com/index.php/Moving_Site_To_Another_Location

was the setup folder copied from the local environment to the live environment, if yes then that will cause an issue. delete the setup folder from the live environment and copy across the setup folder to the live environment from a new downloaded copy (using the same version of modx your running) [ed. note: comp_nerd26 last edited this post 11 years, 11 months ago.]

The odds are really good that one or more paths or URLs is still incorrect in core/config/config.inc.php. Search it for 'sdekroon'. That shouldn't be there.

Also, make sure the paths there all end with a slash.

site_url, BTW, is not there. It's created dynamically based on the URL the user comes in on.