[Bug 487901] Review Request: zikula - web-based CMS

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=487901


Clint Savage <herlo1 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |herlo1 at gmail.com




--- Comment #3 from Clint Savage <herlo1 at gmail.com>  2009-03-01 01:42:21 EDT ---
Reviewing http://ke4qqq.fedorapeople.org/zikula-1.1.1-7.fc10.src.rpm

Couple odd things after installed successfully, probably for upstream:

- The accept licence page has no content.
- The selinux context of the zikula/config.php is incorrect, should be
system_u:object_r:httpd_var_run_t:s0.  Similar to what you did for the
/etc/zikula directory
- Upon login to the administration section, the following errors appear

  *  Stop, please! Installer file 'install.php' and directory 'install' are in
the site root, but must be removed before you can access the Admin Panel.
  * Stop, please! An upgrade script (file 'upgrade.php') is in the site root,
but must be removed before you can access the Admin Panel.
  * Stop, please! An upgrade script (file 'upgrade10xto11x.php') is in the site
root, but must be removed before you can access the Admin Panel.

This could be fixed upstream by doing a little work to the install.php script. 
It could eliminate this unnecessary validation if it just removed/moved/chmod'd
the dirs themselves.

Finally, zikula insists the config.php be writable during the install process,
but once the install is completed, the admin section complains that it is
writable.  Again, the install process could make these changes simply.

Clint

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.