Hi,
I’m developing a couple of sites on my local machine with a view to hosting multiple sites. For that reason I’ve been using the Revo - advanced package so that I can move the core directory out to another location.
I’ve just tried upgrading from 2.0.6 to 2.0.7 but when I run though the setup pages it recognizes that the core directory is not in the standard place. So I point it at the new core directory location but when I get to the Installation options it will only let me select a new install, the "upgrade existing install" option is disabled. I seem to remember having the same problem on 2.0.5 to 2.0.6 as well.
For mobile working I also have a standard install of Revo on a Netbook, this I could upgrade from 2.0.6 to 2.0.7 without any problems.
As I believe I have the same file settings and permissions on both machines I’m wondering what files or database settings the advanced installation is checking to see whether there is an existing installation to upgrade? Any clues would be appreciated.
Many thanks
Adrian
Maybe the advanced install assumes that if you’re going to move the core, you’ll do it when you first install MODx, not later.
I think this might work for you:
1. Back up your site.
2. Adjust the paths in the four config.core.php files:
§ MODx root directory
§ /manager/
§ /connectors/
§ /setup/includes/
3. Do the upgrade install.
You might have to edit paths in the core/config/config.inc.php file -- I’m not sure, but I don’t think so.
BTW, I don’t see how moving the core directory will help you with multiple sites (though it does make the site more secure). Maybe I just don’t understand what you’re planning.
Many thanks for that - you pointed me in the right direction.
The paths in the root directory, /manager/ , and /connectors/ were all correct.
The path in the /setup/includes/ directory was pointing to the wrong area, i.e. the current root directory. However when I run the setup it recognizes that the core directory can’t be found so it asks you for the location for the core directory so it wasn’t this. However whilst looking at this file I noticed that the ’MODX_CONFIG_KEY’ was different, fortunately this is another option in the installation pages, albeit slightly hidden. Once I’d set the same config key I could upgrade the install. I must make a note in my upgrade procedure because no doubt I’ll forget about ti the next time I want to upgrade.
Perhaps I’ve got it wrong understanding the benefits of the advanced install then - I’m still finding my way around. I thought that by moving the core directory out of the root directory I could then separate my website resources from the core manager functions.
So if I had two websites I could have two root directories, each with their own stack of images and documents etc. Also each would have it’s own CONFIG_KEY and hence it’s own set of database tables. So things like my registered user list can be kept separate. Also moving the data around or making backups I can point it at one root directory and grab everything relevant to that one website.
However by linking them both to one core directory it means that if I update a package, eg. Wayfinder, I do it once and both websites will see the update. If a develop a new snippet I don’t have to copy it to each website in turn as they will all see in from the one core directory.
That’s was what I was planning - although I’m still in the learning stage and running on localhost - so any feedback would be appreciated.
Regards
Adrian
ps. I might have a few more questions later as I’m just having a look a NewsPublisher.
