We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 4845 - Application install checks
Application install checks
Status: NEW
Product: OJS
Classification: Unclassified
Component: User Interface
PC Mac OS X 10.3
: P5 enhancement
Assigned To: PKP Support
Depends on:
  Show dependency treegraph
Reported: 2009-10-29 11:39 PDT by James MacGregor
Modified: 2014-08-19 11:45 PDT (History)
2 users (show)

See Also:
Version Reported In:
Also Affects: OCS 2.3.4, OMP 1.0


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2009-10-29 11:39:54 PDT
Add the following pre- and post-install checks to ensure that all system requirements are met; optional extensions are flagged; and errors are properly handled. The purpose of these checks isn't necessarily to remove any possibility for error, but to ensure that users properly understand what's happening when something goes wrong.


-- If possible, add an extension check for MySQL. 

-- Check for optional PHP extension support: libGD, libXSLT, mbstring (maybe others?). If these are missing, flag it as a 'yellow light', maybe explain what is missing and why it could be useful (eg. GD for Captcha), but don't stop the install. 

-- Check for good PHP/Apache configuration parameters. I don't know if this is possible; but it'd be nice to let people know that their allocated memory is probably too low. I would test for PHP's memory_limit; post_max_size; upload_max_filesize; and memory_limit. Possibly also Apache's LimitRequestBody directive, although I don't know if this has been a problem recently. It's hard to have any hard and fast rule about what makes good parameters here, and so hard coming up with a rule; but I'd say if memory_limit is set to 8M, for example, a yellow flag should be raised. 

-- If possible, check for what kind of mail support is available. 


-- display any errors on post-install to the web page. (This should only be done for the one post-install page; the purpose is to avoid "what's going on with this blank page" kind of questions.)
Comment 1 James MacGregor 2009-10-29 12:58:19 PDT
This should also test more carefully an comprehensively for proper file permissions. (Permissions will be made slightly simpler once Bug 1452 has been resolved.)
Comment 2 jerico 2009-11-06 16:32:40 PST
- Please see #4847 for another "yellow"-prio dependency that should be checked on the traffic light page: the tar program
- Also "yellow" should be availability of the perl program

Both are configured in the [cli] section of config.inc.php