Documentation Mailing Lists FAQ Frequently Asked Questions v2

How to transform the old slice (from AAv1.2-) to the new database structure (used in AAv1.5+)? Author: Honza actionapps@ecn.cz

Related Categories: System Administrator **Unspecified**   Add Comment

There is script /misc/oldDb2Db/move.php3. Script move.php3 is database trnansformation script, which copies whole slice from ActionApps v1.2- to the new database structure, which is used for ActionApps v1.5+.

1. Go on Admin - Slice structure Import
2. Copy the content of the /misc/oldDb2Db/oldSliceTemplate.txt file to the import area and press 'Send the slices structure' button. (This slice is then used as template for all imported slices. It makes no sence to repeat steps 1) and 2) for importing second slice !!!
3. Modify next few lines in this script and fill the
   
   • OLD_DB credentials to be able to connect to source database
   • owner id
   • old (source) slice id
4. Remove the line just before this coment
5. Run this script (you have to log as SuperAdmin, then)
6. Done

What is Done:

• New slice in new database is created based on oldSliceTemplate (the slice id is the same as in old database)
• old format strings are copied to the new slice
• all fields in new slice are set is in old slice (defaults, visibility, required, ...)
• categories are copied and added to constants as it is obvious in AA v1.5+
• all fields of all items in source slice are copied to the new database
• relation table is updated and feeding relations is stored there

Limitations:

• permissions for slice is not copied in case you are using SQL version of permission system (in fact, the oermission is not copied in LDAP version too, but it is obvious, that old AA and new AA share the same LDAP tree, so the copy of permissions is not needed)
• field names are allways the same and it comes from en_news_lang.php3 (see Admin - Fields for change the names)
• Show on URL (redirect) field is copied to the new database, but alias (_#HDLN_URL, ...) do not count with this field. You should set the new alias in order you get the same result as in old database
• the defaut expiry date can be set different in old and new database in some cases (see Admin - Fields - Expiry date Edit - Default)
• automatical search form is not implemented in AA v1.5+ - all search settings are removed

After import you have to change the include lines in the pages in order the new slice is called - for example change old line in *.shtml file:

<!--#include virtual="/aa12/slice.php3?slice_id=4e6577735f454e5f746d706c2e2e2e2e"-->

to point to new AAv2.0 installation directory:

<!--#include virtual="/aa20/slice.php3?slice_id=4e6577735f454e5f746d706c2e2e2e2e"-->

The slice id is the same. After that, you shoud review all public pages to make you sure, it works as expected. I do not expect many problems. All features of AAv1.2- as possible to implement in AAv2.0. The biggest problem should be the search form, but it is quite easy to create it manually.

Last Edit: Aug 17 2011

<aafaq id=1727> ~ToDo: 1727 How to transform the old slice (from AAv1.2-) to the new database structure (used in AAv1.5+)? </aafaq> 

This FAQ interface was developed by Jason at Commons.ca

APC ActionApps is a free software content management system initiated by the Association for Progressive Communications (APC) APC - Internet and ICTs for social justice and development