1
chris_h
[SOLVED] xoops install broken -- redefines mimetype for php files.
  • 2017/1/28 21:29

  • chris_h

  • Just popping in

  • Posts: 4

  • Since: 2017/1/28


OK I'm looking for a suitable CMS/BLOG type application to install on the 160 some domains
I own, and operate. In my initial evaluation of XOOPS (2.5.8) I discover that the second page
of the installer (installwizard) redefines the MIMETYPE for the php extension (suffix). WTF?!
Look, anyone installing a PHP script, or PHP based application, will *already* have a
server suitably setup for running PHP scripts. So *why* does XOOPS attempt to define
it at all? New users that may *not* have the proper server environment setup for
running PHP, or XOOPS, will need only read the INSTALL docs to discover how to
get, and setup a proper server, with all the necessary ingredients.
As it sits now, anything past the second screen of the installer, results in being
prompted to download the php file (page_modcheck.php).
Needless to say; XOOPS will not be my choice of CMS/FORUM/BLOG.
Sorry.

relevant info:
PHP 5.3
SERVER Apache 2.2
XOOPS: 2.5.8

--Chris

2
chris_h
Re: xoops install broken -- redefines mimetype for php files.
  • 2017/1/28 22:08

  • chris_h

  • Just popping in

  • Posts: 4

  • Since: 2017/1/28


OK My bad.
I neglected to make the file
include/license.php
writable by the web server. Changing the permissions cured the problem.

Thanks, and sorry for the noise.

--Chris

Login

Who's Online

131 user(s) are online (95 user(s) are browsing Support Forums)


Members: 0


Guests: 131


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits