OSI-Certified logo

Installation of the
Content Management module for Phprojekt.

New install in Phprojekt 3.3.

New install of the CMS module (Phprojekt 3.3).

If you are using Phprojekt 3.3 and want to install for the first time the CMS module, these directions are for you:

0) Phprojekt working.
You must have Phprojekt 3.3 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).

2) Unpack.
Extract the files in the phprojekt directory. That will create a "cm" directory with several files inside. This will NOT overwrite any of your original phprojekt files.

3) Change ownership.
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.

4) Run setup.
Point your browser to the phprojekt directory, login and then change the URL to whateverphprojekturl/cm/setup.php. Go through the options in order. First create the config file, change what you want, if unsure, leave the defaults. (Check the Configuration page for details). Then press the "Create config file" button.
NOTE: you must login in phprojekt as the user you will set as superuser (who can change the config data), if not, you will be locked out after creating the config file. For example, if you want "root" user to be the superuser (for the CMS module), login in phprojekt as root and then change the URL to cm/setup.php, there you set the superuser to "root1" (this is the default short name of root in recent phprojekt versions, if unsure, check the database, table "users", field/column "kurz"). In case you end up locked out, just edit the created cm_config.inc.php file.

5) Create database tables.
Choose the option "Create database tables" in the setup page. This will create the database tables. There are 6 tables in the 0.5.0 version, 5 in the 0.4.8 and 3 in 0.4.7, one for content, one for hits, one for user comments, one for user ratings, one for the permission/restriction matrix and one for the log.

6) Create content directory.
Choose the option "Create main directory". This will create the root content directory. If you have defined a directory that is not inside the CM directory, the creation may fail if the web server don't have enough permissions. Anyway you can create the directory manually.

7) Change the permission/restriction matrix.
Suggested values are the default ones. Review carefully your changes and select the "Save restriction matrix" button. If you plan to change this matrix, read the FAQ question "The restriction table seems so complex, give me a hint.".

8) 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. Because this is a new setup, only the nav bar will be displayed.
NOTE: By default, the display.php script file has several syndicated newsfeeds defined. Only a couple are uncommented. Because this is the first time they are get, the main CM page may take several seconds to display (if you are behind a firewall blocking the download, it may take a lot more). If you like the idea of showing some syndicated news edit the display.php file as necessary. I suggest you to edit the dlsynd.php script file and then use cron or Windows Task Manager to load that file once or twice daily (that will download the syndication RDF files).
If you get an empty page, read the FAQ question "All I get is a blank/empty page".

9) Integrate.
Ok, now you will need to edit 2 phprojekt files. Don't worry, you will only change a couple of lines.
First, the main index.php file (from the phprojekt root, not the cm directory). Change the line 82 from:

if (!$mode) {$mode = "1";}

to:

if (!$mode) {$mode = "cm_home";}

This line will set the CM tab as the default start tab. If you don't want this behavior, don't change this line.
Also, at the end of the file, at line 190 or so, add the line:

include_once ("cm/cm_mainindex.inc.php");

This line will include the code to make the content tab to work.
Second, the layout/o.php file. You will add the following line:

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

You can add it at line 29. This will make the content tab to appear just before the Calendar tab. You can change this to appear at other location.

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

11) You are done.
If you are the superuser, you will find some extra icons in the nav bar to create pages.

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