Package not found

Don’t EVER do this! You should create and upload the local DB to the remote server, then run upgrade against that existing database. Never EVER install new, drop the database and import another one.

OpenGeek, what do you mean exactly?

...in case i have a preinstalled MODx version on a live server, couldn’t i drop all tables in that remote db, import the sql dump from my local installation, replace the files on the remote server with those from my local installation and run the installer in upgrade mode? ( MODx Evolution )

thanks, j

Quote from: sharkbait at Mar 30, 2010, 04:41 PM

Don’t EVER do this! You should create and upload the local DB to the remote server, then run upgrade against that existing database. Never EVER install new, drop the database and import another one.

OpenGeek, what do you mean exactly?

...in case i have a preinstalled MODx version on a live server, couldn’t i drop all tables in that remote db, import the sql dump from my local installation, replace the files on the remote server with those from my local installation and run the installer in upgrade mode? ( MODx Evolution )

Sure, running the upgrade on the imported database is the key; I’m just making it clear running a new install and then replacing the database without any further action is not the proper process.

Sure, running the upgrade on the imported database is the key; I’m just making it clear running a new install and then replacing the database without any further action is not the proper process.

thanks! - i was just wondering, because i usually transfer from local to remote (non preinstalled MODx versions) without running the installer at all ... i make the changes in the config file and in the backend (paths) manually ... is there anything else that running the installer will do? never had any problems btw.
for that one project i might have to use the preinstalled db & installation and proceed as i mentioned in the previous post

Quote from: sharkbait at Mar 30, 2010, 05:05 PM

thanks! - i was just wondering, because i usually transfer from local to remote (non preinstalled MODx versions) without running the installer at all ... i make the changes in the config file and in the backend (paths) manually ... is there anything else that running the installer will do? never had any problems btw.
for that one project i might have to use the preinstalled db & installation and proceed as i mentioned in the previous post

The installer will verify that your paths are correct (which might affect a migrated install) and verify that your DB is working and running. I also agree - when migrating from one server (or local) to another, always run setup/ and upgrade.

The installer will verify that your paths are correct (which might affect a migrated install) and verify that your DB is working and running. I also agree - when migrating from one server (or local) to another, always run setup/ and upgrade.

okay thanks

it doesn’t works!!

my DB is right because I’ve imported local version of DB (with right lexicon)

Do I have to copy some files from my local version??


Thanks

it doesn’t works!!

my DB is right because I’ve imported local version of DB (with right lexicon)

Do I have to copy some files from my local version??

you don’t have to copy any files.
you remembered to clear your cache, right?
can you look in the db tables and see you lexicon entries are actually there?