Cannot Edit Database After Migration To New Server

Hi,

We’ve tried to move MODx sites from one server to another several times, and using several different techniques, never having much success. We can get the site to look the same and function, but when we go to edit it on the new server, our changes are never saved. This is one feature of a CMS that’s kind of crucial! I’ve looked into the "Moving Sites To New Servers" in the wiki, and can’t for the life of me figure out what step I’m missing.

We all love MODx, and sing it’s praises, but moving sites across servers is something we cringe at. Does this issue of not being able to modify the database sound familiar to anyone? Does anyone have any ideas as to how to fix it?

We tried a fresh install of MODx onto our new server, then importing the database to the new database, then pointing the config.inc.php file to the new database. The site works but we can’t edit it. We’ve tried reverse engineering the database by just importing the tables with pertinant info (ie. content, not logs) into a fresh install. Again, the page displayed, but we couldn’t edit it.

From what I’ve read, MODx is portable, can someone tell me what I’m doing wrong? Thanks in advance for your help!!!

Can you explain what you mean by can’t edit it? If the site works and accesses the database, then something else is wrong; either database user permissions on the new server, or perhaps something else in the server configuration is preventing you from saving changes? What happens when you try to save a change? Give us something to help you diagnose the specific problem you are having...

Sure,

Let’s say I want to change a link in a page, or a name is misspelled. I go to the page and click edit. In the content area I change the link or fix the spelling error and click save. After it saves, I click edit again, and the change reverts, like I never edited it. It doesn’t seem to save what I changed.

Thanks again for your help!

Hi,

I’m having the same trouble with migrating my modx sites to another server.

Cant seem to log on to the Manager. sometimes get errors like

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at ...

although the site works ok, i assume from the cache pages.

I did a full mysql backup of the original database and copied all the files, then copied them to the new server and installed the database tables an data.

Is there something I’m missing? The config.inc.php file has been updated with the new mysql database connection parameters.

Any help appreaciated!

Quote from: kenqwin at Mar 03, 2008, 06:09 PM

Sure,

Let’s say I want to change a link in a page, or a name is misspelled. I go to the page and click edit. In the content area I change the link or fix the spelling error and click save. After it saves, I click edit again, and the change reverts, like I never edited it. It doesn’t seem to save what I changed.

Thanks again for your help!

http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me

Quote from: webcomsystems at Mar 19, 2009, 10:21 AM

Hi,

I’m having the same trouble with migrating my modx sites to another server.

Cant seem to log on to the Manager. sometimes get errors like

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at ...

although the site works ok, i assume from the cache pages.

I did a full mysql backup of the original database and copied all the files, then copied them to the new server and installed the database tables an data.

Is there something I’m missing? The config.inc.php file has been updated with the new mysql database connection parameters.

Any help appreaciated!

Did you run the installer in upgrade mode in the new location, otherwise, you have data cached from the old location, AND, make sure any files you moved in assets/cache/ are writable by the PHP process.

Slightly off topic, and might not be the same issue but I’ve run into this a couple of time on my XAMPP installs. The most obvious sign is when you try to run update, for some reason it will crash or stall half way down the Install results.

Unfortunately I can’t remeber how I identified the offending tables.. But I remeber narrowing it down using the SQL query in phpMyAdmin per table.

Mssg: Broken tables in the database. ’Table is marked as crashed and should be repaired’.

You could open each table name in phpMyAdmin select table Operations => Repair

Or use an SQL query:

REPAIR TABLE "table name (without quotes)"

Might be worth a shot. Not sure why tables would have crashed in the first instance.

Hi OpenGeek,

Thanks for your suggestion.

I got it working now and what i found is the following...

1. when I transferred my mysql database it didnt carry over the "auto-increment" value for certain ID fields on some tables. I had to update this manually. No fault of MODX just something funny with MySQL exports.
2. I then ran the install again and it worked.

Previously I had run the install without the table update and it failed.

Maybe someone can offer help with respect to MySQL database exports and imports allowing the auto-increment attribute to be imported correctly?

thanks

I recall something similar happening when moving from more recent versions of MySQL to older versions. Is that the case?

No it was exporting from MySQL version 4.1.20 and then importing into 4.1.22.

I was using phpmyadmin 2.7.0-pl1 for the export and 2.11.9.4 for the import, if that make any difference.

theres also different compatibility modes for the import in phpmyadmin. So far i’ve tried "MYSQL40" option and "NONE" option and both dont import the auto increment.