Item10616: When installing an extension, the logs should be saved
Current State: Closed
Released In: 1.1.4
Target Release: patch
Applies To: Engine
When an extension is installed, there is lots of nice information given on the webpage about what changed. It would be nice if everything was stored in a logfile for future reference. There are two ways to do this: store the raw actions in a text file, or save the result page as a static HTML page.
- 08 Apr 2011
Probably needs to be done by recording the text output of the installation. Extensions can be installed from either the Web, or from the shell, so capturing results page as HTML wouldn't apply to the shell installation.
- Write a summary record to
- File format doesn't really support logging an install. Needs some discussion. Format is tabular, for example:
- Write the detailed report to
Not sure if this one needs a feature proposal. Probably does if any log file formats are changed. To make the log format more useful, add an Action column, Set, Install, Remove, Passwd, Set being the current format of Variable / Value? Proposed revised layout:
To late for 1.1.3, but this could probably make it into 1.1.4.
- 09 Apr 2011
Committing the change to extension installation to log the results of the install. This needed some refactoring. The
method was renamed to
method was modified to be consistent with
, they now both run the pre and post (un)install routines and log all results.
- 20 Jul 2011