Details
-
Type:
New Feature
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.3.0
-
Fix Version/s: Short Term
-
Component/s: Staff Interface
-
Labels:None
Description
Under Tools in the Staff interface add an option called Environment
- Register a Staff ACL permission to this page, enabled by default if possible on install
- Add a full-sized widget with tabs, the first tab should be labeled "PHP Info". The widget title should be "Environment"
- Inside the PHP Info tab, output phpinfo() details. We may want to break this down by section and output individual items separately. If we output the entire phpinfo() it should be contained within the widget window.
In the future we may wish to add additional tabs to report other environment data.. Requirements Check (Same checks that we do on install, when people move Blesta often they don't meet requirements and have weird issues), perhaps read the log files from ../logs/blesta/, mysql version, IP address, database tables, etc. More discussion warranted
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Paul Phillips
made changes -
| Rank | Ranked lower |
Paul Phillips
made changes -
| Description |
Under Tools in the Staff interface add an option called Environment
* Register a Staff ACL permission to this page, enabled by default if possible on install * Add a full-sized widget with tabs, the first tab should be labeled "PHP Info". The widget title should be "Environment" * Inside the PHP Info tab, output phpinfo() details. We may want to break this down by section and output individual items separately. If we output the entire phpinfo() it should be contained within the widget window. In the future we may wish to add additional tabs to report other environment data.. perhaps read the log files from ../logs/blesta/, mysql version, IP address, etc. More discussion warranted |
Under Tools in the Staff interface add an option called Environment
* Register a Staff ACL permission to this page, enabled by default if possible on install * Add a full-sized widget with tabs, the first tab should be labeled "PHP Info". The widget title should be "Environment" * Inside the PHP Info tab, output phpinfo() details. We may want to break this down by section and output individual items separately. If we output the entire phpinfo() it should be contained within the widget window. In the future we may wish to add additional tabs to report other environment data.. perhaps read the log files from ../logs/blesta/, mysql version, IP address, database tables, etc. More discussion warranted |
Paul Phillips
made changes -
| Description |
Under Tools in the Staff interface add an option called Environment
* Register a Staff ACL permission to this page, enabled by default if possible on install * Add a full-sized widget with tabs, the first tab should be labeled "PHP Info". The widget title should be "Environment" * Inside the PHP Info tab, output phpinfo() details. We may want to break this down by section and output individual items separately. If we output the entire phpinfo() it should be contained within the widget window. In the future we may wish to add additional tabs to report other environment data.. perhaps read the log files from ../logs/blesta/, mysql version, IP address, database tables, etc. More discussion warranted |
Under Tools in the Staff interface add an option called Environment
* Register a Staff ACL permission to this page, enabled by default if possible on install * Add a full-sized widget with tabs, the first tab should be labeled "PHP Info". The widget title should be "Environment" * Inside the PHP Info tab, output phpinfo() details. We may want to break this down by section and output individual items separately. If we output the entire phpinfo() it should be contained within the widget window. In the future we may wish to add additional tabs to report other environment data.. Requirements Check (Same checks that we do on install, when people move Blesta often they don't meet requirements and have weird issues), perhaps read the log files from ../logs/blesta/, mysql version, IP address, database tables, etc. More discussion warranted |