* make visible in the admin interface which version of drupal and modules are used (x.y.x where z 0!)
* optionally find out on drupal site what current major/minor version is and a list of known bugs that are solved
* optionally (long term) make a webbased install (get file, unpack, update.php etc..)
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | version.patch | 2.65 KB | profix898 |
Comments
Comment #1
moshe weitzman commentedComment #2
Philippe commentedCould we modify the build daemon (or is it a cron job?) to do keyword substitution (perhaps only in one file)?
Any other ideas?
Comment #3
Philippe commentedCould we modify the build daemon (or is it a cron job?) to do keyword substitution (perhaps only in one file)?
Any other ideas?
Comment #4
jose reyero commentedI'll rise the priority of this one as I think it is very important for support issues and also when you are administering a number of Drupal sites it is a very important information, for security updates too.
Comment #5
judah commentedI'm thinking that we create a few new variables, major and minor version, in the drupal core module or base system. Then with a couple new functions we can access those variables with variable_get or the functions show below:
We could also add a function that would parse the base system or any file for that matter and pull out the revision number:
i don't remember if cvs revision numbers are global to the modules. if they are then the revision number would be useless.
Comment #6
webchickI think this is already in system.module in 4.7.2+?
Comment #7
killes@www.drop.org commentedThe version is defined in system module as of 4.7.2, bu tit isn't shown to the admin yet.
Comment #8
profix898 commentedWhy not add a simple line at the top of modules page (admin/modules)?
Comment #9
bertboerland commentedby now this is fixed. even with dependecies and modules that need updating.
only the installer isnt there yet but /me thinks that will be a contrib around 7 or so :-)
Comment #10
(not verified) commented