Updating the ezpublish web site database?

Next topic

Author	Message
Jorge estévez	Monday 12 July 2004 6:31:46 pm I would like (working offline developing new options) to update the clients database, but without erasing the information that his database has due to the use of the intranet/web site (eg. forums) Please can someone point out the tables within the database taht should be updated and the ones that should not be touched. If this is not the solution, please tell me what to do. thanks! Diseño Web Cuba Web Design Cuba www.elfosdesign.com
Silke Fox	Tuesday 13 July 2004 6:30:41 am You should use the database update scripts which are provided with newer eZ publish versions. See http://ez.no/ez_publish/documentation/installation/upgrading/upgrading_ez_publish_from_3_a_b_to_3_x_y And you can use the database diff tool after updating to check if it was successful... ;) http://ez.no/ez_publish/documentation/development/scripting/supplied_scripts/database_diffing_tool
Jorge estévez	Sunday 18 July 2004 4:19:26 am Thanks but that was not my question... (Thanks anyway)) I am not upgrading no a new ez version... within the same version 3.4 y have my development site (offline) and the client's site (production)... The client’s site is doing well and the client uses it every day... in the meantime I keep adding new links, sections, etc, to the development site (offline)... At the moment of updating (once I test that everything is doing fine) I upgrade all the files of ez publish to the server... BUT!!! When it comes to the data base I should not erase the old data base and copy the new one because I erase data that has been posted to the database by the client itself (e.g. forums etc)... so only some tables should be updated... Does somebody now wish ones should I update? Any IDEAS? Diseño Web Cuba Web Design Cuba www.elfosdesign.com
Silke Fox	Monday 19 July 2004 12:52:37 am For the future, I would recommend that you perform major changes on the client's database directly and then import that db to your development environment. For now... it's no good idea to update some tables of the database, as this will probably result in an inconsistent database. Try to use packages for content class and content object export/ import. http://ez.no/ez_publish/documentation/ez_publish_3_4/content_object_import_and_export Sections, roles etc. have to be created manually though. Maybe there are better ideas around here... ;)