Upgrading from v 1.2.0 to v 1.3.0  (PHP)

These instructions must be followed when upgrading from versions 1.0.x, 1.1.x or 1.2.0. Before upgrading, you may want to check the list of new features.

New features

• Document sorting: The default sort order for documents is now according to a new system field called '$DOCORDER'. This allows you to change the sort order of documents by using the new allow sorting option in the fIndex component. When enabled and if the query that fIndex executes is sortable, the administrator can simply drag and drop the fIndex record movieclips in order to change their order. These changes are saved to the backend. Sortable queries are all queries that return documents of the same type and with a simple relationship (if this exists).

• Simplified fCMSBackend path settings: There are only 2 parameters now: 'fCMS Server Path' and 'fCMS File Root' (which should have same value as set in the config.xml file). fMaster will automatically detect if the swf is running inside the Flash authoring enviroment (IDE), in which case it will search for the modules folder inside the same folder where fla file is located. We therefore suggest setting your publishing settings to publish the SWF to the same location as your .fla.

• fHTML component: This is a new component for entering text. The difference between this component and the fString component is that text containing HTML tags won't have the HTML tags stripped when written to the database.

• Improved backend thumbnail autocreation: Use the new thumbExplorer application located at http://www.fcmspro.com/thumbExplorer/ to create thumbnail definitions and to see exactly how the thumbnails will look.

Upgrade procedure

1. First, backup your database and verify you are not using document types that begin with "_". The simplest way to backup your database is using phpMyAdmin. Select your database, click on the Export tab, select the tables of the fCMSPro and "SQL" export from the left side of the screen and select the "Save as File" option from the bottom of the screen. Click the "Go" button. A save file dialog should appear, prompting you for the location of the file to save. In the event that you have any problems with new version of the fCMSPro at a later stage, you will be able to revert to the previous version.

2. Upload the entire content of the php-1.3.0 upgrade only folder, overwriting all files. Note: If you have the option to "merge" select this option instead as you want to retain the existing config, imgRoot and ioncube folders. In the event that you edited some of the files, be sure to backup them and apply same changes to new files.

3. Open your webbrowser and run the upgrade script by accessing "http://www.yourdomain.com/fCMSBackend/admin/upgrade.php" and follow the instructions (replace yourdomain.com with your URL).

4. Close Flash and double click on the fCMSPro.mxp file that is included with your download in order to install the new version of the fCMSPro components. Please ensure that you have the latest version of Adobe extension manager.

5. Backup your current .fla before editing it with the new components.

6. Open the .fla that you wish to apply the update to. Open the Components panel and drag and drop the updated fCMSPro components to the library of your fla file. When prompted, choose to "Replace existing items". If you previously disabled the "Export in first frame" option for the fCMSPro components, you will need to disable them again after the component update. Note: If you placed the previous fCMSPro components in a folder in your library, you should drag the updated components into the same folder in order to update them.

Upgrading from v 1.1.0 to v 1.2.0  (PHP)

These instructions must be followed when upgrading from versions 1.0.x and 1.1.x. Before upgrading, check the list of new features. Also, make a backup of your database.

New features

• The main new feature is support for tagging and relations. This feature requires the upgrade of the database. However, the functioning of the previous features is not affected and the old application can continue to function after the upgrade (except in one special case, see the next note).

• The only change in the backend functionality is that document types that begin with "_" are considered special. They are automatically excluded from the queries unless the query specifically asks for them. In case your application uses document types that begin with "_", it is not possible to upgrade unless the application is modified.

• The new version supports automatic thumbnail generation. This feature is disabled by default. To enable it, you have to have a file thumbs.xml in the config/ directory. You can check the example file from the distrubution archive. In order to use thumbnails, you have to have GD library installed for PHP.

• The main html template (index.php) has changed. Now, the document type index page contains <meta name="robots" value="noindex" >  which prevents it from being indexed by the search engine. For that reason, it is no longer necessary to have a corresponding template in the flash (only home page and fullstory templates are required). Also, the new version of swfobject is used.

• In the fcms_html.php, there is another parameter $EXCLUDE_DOCTYPES to exclude doctypes from the HTML template.

Upgrade procedure

• First, backup your database and verify you are not using document types that begin with "_".

• Inside fCMSBackend/ directory, replace following 3 folders admin/, includes/ and modules/.

• Upgrade your database by accessing the url http://<your site>/fCMSBackend/admin/upgrade.php

• The distribution archive has the new versions of the index.php and swfobject.js which are located in the folder that contains 'fCMSBackend/ in your installation. If you haven't modified these files, just replace them. Otherwise, you must apply the changes to the new files.

• The distribution archive has the new version of the fcms_html.php file which is located in the folder that contains 'fCMSBackend/ in your installation. Check all the parameters at the begining of the file in your installation, and setup the file from the distribuition accordingly. After that, replace this file with the version from the distribution.
• The new version supports automatic thumbnail generation. This feature is disabled by default. To enable it, you have to move a file thumbs.xml in the config/ directory. You can check the example file from the distrubution archive. In order to use thumbnails, you have to have GD library installed for PHP.
• New error description is added to fCMSBackend/config/config.xml file. Update it for proper error reporting when using auto thumbnail generation, by adding the following line in the error list:

<e key="ThumbnailProblem">Thumbnail Creation Error</e>

Upgrading from v 1.0.0 to v 1.1.0

Please follow these important instructions if you are upgrading from fCMSPro 1.0.0 to fCMSPro 1.1.0:

Flash Update:

To update fCMSPro to v1.1.0 you will need to update all of the fCMSPro components in your .fla.

1. After installing the .mxp file, open the .fla that you wish to upgrade in Flash 8.

2. Locate the fCMSPro folder in the Components panel and drag each component to the library (or directly onto the stage). A dialog box will appear. Choose Replace existing component and click the OK button for each component. If the replace component dialog does not appear, you probably have your fCMSPro components inside a folder in the library. In this case drag the components from the Components panel to the folder in the library where the components reside.

Note: If you disabled the Load at first frame option for each component in order to create a preloader, you will have to do this again after updating the components.

PHP update:

To update the PHP files to v1.1.0, you will need to replace all of the files in the fCMSBackend/includes/ and fCMSBackend/modules/ folders with the files included with version 1.1.0.

Note: Before any backend update it is highly recommended to backup your fCMSPro database.