site_url settings in MODx 9.2.1

Does anyone know where the settings for the site_url variable are stored? I suspect it is actually the HTTP_HOST variable, but I cannot find any place within the PHP files where the information that is place in the site_url is saved.

Consequently, it might be in the database, but I cannot find which table contains the information.

The version of MODx that my client uses is 0.9.2.1. (They have not allowed an upgrade, although I have recommended it.) The site resides on a ISS/6.0 server.

The reason I need to figure out where the site_url setting is stored is because somehow, someone has changed it so that it now points to microsoft.com rather than my client’s site.

If anyone knows in which this setting is set, please let me know so that I can fix this problem.

Thanks.

Skip Keats

manager/includes/config.inc.php

That’s a pretty old version, but I believe that it also generates that value at run-time; it’s not actually stored anywhere.

That said, I strongly suggest that you upgrade.

If it is being generated at runtime, from where is MODx pulling the information that relates to the base URL info? My client’s information has gotten fouled and the normal site is unviewable (although the manager is accessible).

As for upgrading, I have recommended it repeatedly, but they do not want to allow me the time to do so -- although this problem may force the issue.

Any suggestions?

Thanks.

Skip Keats

You might relay to them that 0921 is also very prone to being compromised (and may in fact be why their site is messed up) due to the third party image browser included with it.

See, subscribe to and follow the recommendations: http://modxcms.com/forums/index.php/board,202.0.html

As far as time goes, it’s merely a matter of doing a full backup (file system + database) which you should be doing from time to time anyway and doesn’t require any downtime, then uploading the new Manager folder and most of the Assets folders, as well as the index.php file (I don’t upgrade templates, snippets or any customized modules and plugins on a version that old), then run the Installer. Again, on the installer snippet selection screen, I only select the modules and plugins to upgrade.

At most an hour. Well, I have had it take two hours when my ISP was bogged down and it took two hours to upload...

I always first clear the cache, the event log and the manager log.

If you have ssh access, you can do it in about two minutes (once you scp and unzip the archive on the server).

Oh, and when you backup the database, make sure to add the Drop Table option, since you can’t revert the database once you’ve upgraded it. The tables need to be dropped and the old ones created again.

Note re: installer and 0961 ... currently there’s a bug that makes upgrading snippets a none or all approach. Should be fixed in 0962.

Well, I never upgrade snippets as part of a general upgrade. They may have changed too much, and until I’m ready to work with them, I’m not ready to have major features of the site break until I figure out which snippet and what parameters were affected. So I upgrade snippets one-at-a-time after the system upgrade, and then only if there is any real benefit to doing so. A menu that works doesn’t really need to be switched over to the latest version of Wayfinder.