/
Proposing new "System Configuration" installation step

Proposing new "System Configuration" installation step

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/d1ebd77cc3da4b9a#

Hello everyone,

For In-Portal 5.2.0 we are proposing to add new System Configuration step to Installation process + Update System Configuration option for "Installation Maintenance" (to make changes after the installation). The purpose of this step would be to manage System Settings which can't be saved in the Database due to code architecture and must be accessible before connection to the database for better performance.

Below is description of how it can work.

1. New Installation:

Add System Configuration step (after Basic Configuration step) and make this step to be visible *ONLY* when Debugger is ON.

It will list the following variable (all MUST be saved in system/config.php):

  • WriteablePath (string, default "/system")
  • AdminDirectory (string)
  • AdminPresetsDirectory (string)
  • ApplicationClass (string)
  • ApplicationPath (string)
  • CacheHandler (drop-down with current options)
  • MemcacheServers (string)

2. Installation Maintenance:

Add Update System Configuration option after Update License Information option.

  • WriteablePath (string, default "/system")
  • AdminDirectory (string)
  • AdminPresetsDirectory (string)
  • ApplicationClass (string, visible with Debug ON)
  • ApplicationPath (string, visible with Debug ON)
  • CacheHandler (drop-down with current options)
  • MemcacheServers (string)

Description (right hand side) for this new section can read something like this:

These are system advanced settings and must be changed with caution. It's not recommended to change these settings unless you know what you are doing. These settings will be stored in system/config.php file and can be changed manually if needed.

Let me know what you think.

Related Tasks

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.