OSI-Certified logo

Installation of the
Content Management module for Phprojekt.

Upgrading in Phprojekt 4.2.

Upgrading the CMS module (Phprojekt 4.2).

If you are using Phprojekt 4.2 and want to upgrade the CMS module from version 0.5.1 or higher, these directions are for you:

0) Phprojekt working.
You must have Phprojekt 4.2 installed, configured and working.

1) Get the files.
Get the files from http://www.mariovaldez.net/software/cm_4p/ (There are zip and tar.gz files available). Note that you require version 0.6.0 or higher. (Version 0.5.1 will work but you cannot use the database table prefix feature of Phprojekt and will miss several CMS enhancements).

2) Backup your files and your database.
As a safety measure, backup your cm directory and backup the data in your database (the exact steps to backup your database depend on the brand, check the administration manual of your software).

3) Take note of any customization you have made.
If you changed the code of the CMS module, check what are your changes and apply them again in the new code. This includes changes to display.php for the syndicated newsfeeds (if you upgrade to version 0.6.0 or higher, you can add your newsfeeds using the syndication newsfeed manager). If your customizations are more complex, don't fall to the temptation to leave old scripts mixed with the new ones. You should review your changes and integrate your code again.

4) Delete previous CM code (preserve the CM root dir!).
You can overwrite the old files if you wish, but better is to delete the old files and directories. Be careful and don't delete the CM root directory (usually is the directory named cm/root/).

5) Unpack.
Extract the files in the phprojekt directory. That will store the files in the "cm" directory.

6) Change ownership.
If needed, change the ownership of those files to the user used by your web server (usually "nobody" in Unix/Linux).
To change the ownership in Linux/Unix, you execute in a shell terminal in the server the command chown:

chown -h -R nobody:nobody cm/

In Windows environments, using the Windows Explorer, check the Security tab of the Properties dialog of the directory, and set the permissions so that the user IUSR_servername has permissions to read and write on the CM directory.

7) Run setup.
Point your browser to to whateverphprojekturl/cm/setup.php and login. Change what you want, if unsure, leave the defaults. (Check the Configuration page for details). Then press the "Create config file" button.
NOTE: This is a required step even if you are only upgrading. Some new options are only enabled if you run the setup. Also, don't leave any field empty.
NOTE: If you login directly while accesing the setup.php page you will be redirected to cm/index.php page and you may get an error message if your configuration is not complete (which may happen with new options after upgrading). If this happens, just try to access the cm/setup.php again.

8) Update database tables.
Choose the option "Create database tables". This will create any new database table. If some tables already exist, there will be some error messages. That's ok. Check for any error in the new tables or in any UPGRADE message.

9) Test.
To test that everything is ok, point your browser to whateverphprojekturl/cm/ (or choose "Go to the Content Management module homepage") and see if the page is displayed.
If you get an empty page, read the FAQ question "All I get is a blank/empty page".

10) Integrate.
If you are upgrading from 0.5.1 to 0.6.0 or higher, you can optionally do this integration change if you want to have a list of recent articles in the Summary page of Phprojekt, you need to edit the summary/summary.php file and add the following around line 370 (as the last PHP line, before the ?> symbols):

include_once ($path_pre."/cm/cm_summary.inc.php");

11) Test again.
To test, point your browser to the phprojekt URL.

12) You are done.
Check the new features. For a list of new features, read the version.txt file included with the CMS module.

NA fum/lmd: 2006.09.25
Copyright ©1994-2018 by Mario A. Valdez-Ramírez.
no siga este enlace / do not follow this link