9/1/2023 0 Comments Fm 2005 patch 5.0.3![]() This applies to data and to string field definitions. There is also another reason to migrate data (irrespective to db schema) and that is the encoding conversion that is required. There is no practical way to patch an existing site to the new code. ![]() The changes that argue against an upgrade path are the code base and it's structure. The only thing that almost has almost no changes is the database schemal Besides two field renames, there are a few additions which usually don't affect upgrade or migration. The developer team have been claiming all along that they weren't going to change the database schema because of compatibility issues with previous versions - now you're saying that there is no way outside migration - so the question really is why you don't do schema upgrades as well since 1.5 is so significantly changed? Add foreign keys to all the tables at least, so one can reverse engineer it properly, this won't change the schema at all. The core data migration does reconstruct menu items for core elements and also keeps core module records with configuration settings. Extensions need to be installed and configured as if the site is new. The concept is to build a new site and to migrate data from the old site. This is the reason that we are providing a migration path. Joomla 1.5 is so significantly changed from 1.0 that there is no 'upgrade' path.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |