Ryan H. Posted January 16, 2012 Share Posted January 16, 2012 One frustration I've occasionally had with IP.Board is how many administrative actions are not logged. I think the logs should cover every action as much as possible--we should never be left saying, 'Well, the logs don't show anything... was something changed?' Someone saves a settings group? Log it. Rebuilds some stats? Log it. Modifies a template bit? Log it. Runs an SQL query? Log it [the query itself!]. Changes ACP Permissions? Log it. Installs or disables an application/hook, or runs an upgrade? Log it. Imports/exports a skin or language pack? Log it.Removes logs? Log it! Yeah? Link to comment Share on other sites More sharing options...
MageUK Posted January 16, 2012 Share Posted January 16, 2012 Agreed, especially the SQL queries. Link to comment Share on other sites More sharing options...
Connor T Posted January 16, 2012 Share Posted January 16, 2012 agreed. Link to comment Share on other sites More sharing options...
Feld0 Posted January 17, 2012 Share Posted January 17, 2012 Great idea. The logging should also extend to all additional applications that come with their own ACP panels, if that's at all possible. Link to comment Share on other sites More sharing options...
Marcher Technologies Posted January 17, 2012 Share Posted January 17, 2012 Great idea. The logging should also extend to all additional applications that come with their own ACP panels, if that's at all possible. it is... the 1st-party ips ones really need a touchup though... for example, my utilities module for ip.content logs more actions than the content app itself does.... :logik: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.