By Gunnar Langemark on

Hi all,
Maybe I'm just stupid but,

I have my site running and making changes to more than one testsite.
I would very much appreciate this functionality as an administrator:
A page which keeps a log of all modules and stuff - version, when installed, db changes and updates, and a note system where i can make notes about stuff that I should remember to do, such that I can keep track of the development of the site.
It's getting a little too complicated now.

And while we are at it: As we've been discussing it could be cool to have the publishing system have an optional publishing date/time and unpublishing date/time, AND an alert date - to make it possible to keep the system "alive" and up to date. Some posts will have a natural life span.

Gunnar

Comments

moshe weitzman’s picture

moshe weitzman commented

I've kept a log like this just by posting a story and replying to the story with comments every time i want to log something. you could alternatively post a story every time and associate each post with a taxonomy terms like 'todo' or 'database'.

joe lombardo’s picture

joe lombardo commented

I'm running several instances of drupal, mostly versions, and using at least three of them. ( A testament to the utility of the application!) The problem is each one is a different version of drupal. I haven't tracked the version /date.(especially important w/cvs) So when it is time to upgrade, I either choose not to upgrade, don't want to screw things up. Or take a wild guess.

While limiting and stressful, that strategy has mostly worked, until this week. But on my last instance, i guessed wrong. Now the site is throwing all sorts of errors, and certain fields of data seem to be gone.

BTW, my own little trick for tracking version and date is to save the update.php results page with the date as part of the filename. It's too bad I hadn't started this practice sooner!

- Joe

Joe Lombardo | joe@familytimes.com | My Blog