CMS module for Phprojekt

CMS module for Phprojekt
Tasklist

FS#39 - Setup routine to overcome PHP safe-mode problems.

Attached to Project: CMS module for Phprojekt
Opened by Mario A. Valdez-Ramirez (mvaldez) - Wednesday, 07 July 2004, 17:42 GMT-6
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Sunday, 11 July 2004, 12:43 GMT-6
Task Type Bug Report
Category Backend / Core
Status Assigned
Assigned To Mario A. Valdez-Ramirez (mvaldez)
Operating System All
Severity Low
Priority Normal
Reported Version any
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Possible solutions:

a) Use a PHP-script installer.
A PHP-script installer is one script which create all other scripts from an encoded string (efectively creating them with webserver ownership). I have never seen one standalone version, only ad-hoc scripts for this (for example, smartBB and FUDforum use this approach to install).

b) A FTP autoinstaller, a variation of the previous one, where the script download all files from the same server (or other) using FTP to the webserver (efectively donwloading them with the wevserver ownership). This is the approach taken by Mambo CMS.

c) Store all in a single directory and let the CMS code to keep track of the files/directories (an approach followed by the filemanager of Phprojekt, where dirs are really virtual). I'm seriously considering this solution for the next version (a hashed two-level fixed dir tree). This would only need to set permissions, not ownership.

d) Store everything in the database, including files. The original design of the CMS was planned with this. However, earlier testings when developing the CMS module led me to abandon this idea (because of very poor performance with big files). Retest again for the next release.
This task depends upon

Comment by Mario A. Valdez-Ramirez (mvaldez) - Sunday, 11 July 2004, 12:43 GMT-6
This bug should be solverd by a PHP-script installer.

The option C and D should be addresses in different bug reports.

Loading...