Does SiteDoc Record the sequence and/or date of a module installation?
| Project: | Site Documentation |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
I've yet to do a quick test of the module and actually a bit frantic at the moment with a "MySQL Server has Gone Away" message when accessing "admin/build/modules". Not the first time i've had this happen after I've installed modules to a site build and gotten to far ahead of myself and not recalling what was the last module installed that mayb cuasing the problem. As a result, and from my own mistakes I know that in the system table modules can be turned off by setting "status" to "0" but it would be nice if the standard Drupal build include this with statussince i've seen this quite often. So the question is "Does SiteDoc record and report the sequence and/or date of a module installation?" I pose the question and will get back quick with best answer i can but i thought to post the question first since others who "get ahead of themselves" and dont always do a database/fileset backup everytime will likely encounter the same.
#1
The anwser to the above question is NO - SiteDoc does not record and report the sequence and/or date of a module installation? Drats!
Any one know of another module thant does track this or the core settings to report it?
#2
The problem your having is probably down to memory issues. If you have a lot of modules you have a lot of variables. I have had similar issues of late, and usually the simplest solution is to turn off the 'Update status'
Though the idea of knowing which module was installed when might be useful, you can find the sequence from teh System table of the database, though I am not sure how ininstalling affects the sequence, nor would i suspect it helps with updates
#3
As far as I know, there is no tracking of when a module is enabled. I would suggest opening a core issue to do that. They could add a timestamp to the system table rather easily. As another choice, they could log it.
Yes, this module can be memory intensive, especially in the Variables and URL Alias areas, which can be very long lists. Plus, the HTML output can get very large too. It would be nice if everyone would follow the Theme method of settings in an array, so there is only one variable created.