Imported my site’s plain html files on to modx in xampp. Worked fine - made a lot of changes and it all worked OK on localhost. Then uploaded the sql file to the server - that went OK. Then uploaded the manager and assets folders from xampp local onto server into root and after that uploaded the install folder and other files, also into root, as suggested by the wiki (which explains how to move local dev to server). But somewhere I’m doing something wrong. Can you help fixing it? How much? The site is didyouknow.org.
Thats looking like the default install, did you run the installer when you uploaded it all ??
If so try dropping the database in import the one off your localhost, you will also have to change the details in the config file in the manager folder.
After uploading the install folder, I pointed mu browser to mysite.org/install but it did not give me the option to run upgrade (as the wiki suggested) - instead, it only gave me option to run special/expert (or something like that, the 3rd option). It hooked on to the database OK. Now, all the config files that are on the server point to the correct database host name and sql file. But when I log into mysite.org/manager, I don’t see my files in the tree and all the other files in the modx manager looks like a new install (in fact, it tells me it is a new install). And on the server, I only see the modx introduction page.
To recap: I developed on localhost, imported the sql to the new database I created on the server, then uploaded manager and assets folder and htaccess, index.php and index-ajax.php files. (I changed the path in the htaccess file to point to the root, which should be correct.)Then uploaded the install file and ran the installer. Installer ran but the rest is as above. Any ideas? Help is most appreciated.
It appears that your config file was missing, so you didn’t get the upgrade message, and you have a new install.
On the server just drop all of the tables in the database and import your sql file into the database. That will probably get the site running. After that, just check the configuration settings in the manager and fix any paths that might be wrong.
Thnx 4 the replies. Found my problem: when I created the database on Xampp I called it modxx2. Now the tables names (on the server) are wrong as there are both modx and modxx2 tables names within one sql db and it appears as if the modx upgrade only looks for the modx prefix in the db (the db name in the config file is correct). Major rework, major pain. Will leave it for now - worried about losing traffic (and money). I’ve re-pointed my site to the old design.
I believe MODx will use the table prefix you have told it to use...
cheers/k
Quote from: txtface at Sep 02, 2009, 06:50 AM
Thnx 4 the replies. Found my problem: when I created the database on Xampp I called it modxx2. Now the tables names (on the server) are wrong as there are both modx and modxx2 tables names within one sql db and it appears as if the modx upgrade only looks for the modx prefix in the db (the db name in the config file is correct). Major rework, major pain. Will leave it for now - worried about losing traffic (and money). I’ve re-pointed my site to the old design.
If I’m understanding you correctly, this should set things straight:
1. Back up everything!
2. Edit manager/includes/config.inc.php on the remote site to hold the name of the database/user from remote site *and* the table prefix from the XAMPP site (modxx2_ if I’m reading you right).
3. Repeat the install on the remote site -- looking to make sure the DB name and prefix are the same as in #2. If it doesn’t offer the option of an upgrade install, abort, but as long as manager/includes/config.inc.php is there, you should get the option to upgrade.
That should make the remote site match the local XAMPP site. You may have to edit the file manager path in tools |config.
Once everything is stable, you can delete all the tables with the modx_ prefix.
"A bad jockey blames the horse." I said that. Aha, so that’s what I did wrong!
Will point config file to $table_prefix = ’modxx2_’;. That should do the job. Wasn’t sure if I could delete the original modx tables but will do so now locally and then upload the edited db (after making sure it is stable locally). Thnx BobRay. Thnx all.
