Update.php
Nexus5.01 - July 25, 2008 - 09:59
Hey,
Okay, I'm not too sure on what to do with update.php I run it and then I have to change the values? to what?
I think this is the problem, seen as i don't know what to change and haven't changed them after updating a module is that what is causing this?
http://i279.photobucket.com/albums/kk127/nexusv2/update_problems.jpg
It's asking me to update to the current version I have installed.....
I would appreciate any help :)
update.php is mainly used
update.php is mainly used for database updated by modules - you need to install new versions of the modules first though.
The update status screenshot is telling you which modules to upgrade - so you should follow the download links, extract them into your sites/all/modules directory, and only then do you have to visit update.php. The dropdowns on update.php shouldn't be changed at all.
Sometimes D6.x will do that
Sometimes D6.x will do that - if you are using dev versions of a module, it will show error and recommend you to upgrade to itself.
- Alexei Rayu.
Drupal Related Services | SiteHound Drupal Free Distro
note, that all of the 'dev'
note, that all of the 'dev' versions flagged in your screenshot as dated do have a more recent release (see the dates in parentheses).
that's a problem with development snapshots: the actual version number (e.g. 6.x-1.x-dev) will not change, even if a new version has been released. this is by design (i assume) since the development snapshots should be considered experimental.
in any event, as catch says above, keep in mind that not every new version of a project/module running on your site will have corresponding database changes. the 'available updates' screen shows the version of the code, while update.php handles the database changes -- update.php will often not have any work to do after you update the code.
That is not good
It's kind of devastating that the arguements around whether D6 is ready for production are still heard, some modules like "panels" are still in the devs, and we already have full-scale developement of D7. Just when D6 will become mature enough, D7 will be out. I believe this is counterproductive.
- Alexei Rayu.
Drupal Related Services | SiteHound Drupal Free Distro
totally agree
i absolutely agree with you (though i'm sure there are other forum threads and communication channels dedicated specifically to this) -- when CCK and Views are still in release candidate status this long after the latest major release of Drupal, that's a huge problem. i know many developers have been saying this for a long time... in a word: it seems that the release of major new versions of core should slow down!
though i'll be sure to say in the same breath how grateful i am for the tireless work of the Drupal community in providing this incredible CMS!
=-=
It seems to me that the largest changes in drupal and it's API's took place in drupal between version 5 - 6. Those changes afforded module developers the opportunity to do rewrites and expand on their ideas. I wasn't around previous to Drupal 4.7.2 so I can't comment on versions or lag time before then.
Drupal 7 is still a long way away and has no impact or effect on D6 at all. There are 172 pending issues for D7 at the time of this writing. Obviously they won't all be fixed in a few weeks or months.
Core developers are core developers. It's what they do. The idea that core should slow down because contrib modules haven't caught up yet is odd to me. Halting core won't make contrib modules get updated any faster. Core Developers open up new options to allow contrib developers to do more things as well as continue to focus on the things that drupal core needs to do better to make working with easier/cooler for both developers and users.
Panels, CCK and views are three really large modules. and they all work in tandem which makes things a bit more time consuming if not difficult for the developers of these modules.
I do not think that what has happened between D5 and D6 is common. There wasn't much lag between D4.7.x and D5 and I don't expect there to be between D6 - D7 as developers will be more intune with all the changes that have taken place.
I make it a common practice not to run to the next version just because it is the newest version. I work one version behind in 80 - 90% of cases because I understand the stability of that version and because there are usually more developers still developing for that version. When D7 is released, any site I've got that isn't at least at 6, will be during that time.
Everybody heard that?
I make it a common practice not to run to the next version just because it is the newest version.
This needs to be written in gold.
- Alexei Rayu.
Drupal Related Services | SiteHound Drupal Free Distro
as far as not running the
as far as not running the latest version -- i totally agree in terms of only running stable code. if the code (of e.g. a contrib module) is in development or release candidate status, you shouldn't be surprised if you run into problems. but, as far as stable code goes i find it pretty important to be running the latest version just to keep up. obviously only the last 2 versions of core are supported, so i try to dig in on upgrading all of my sites as soon as all of the contrib modules used by that site are stable for the next version of Drupal (or, once we've migrated from an abandoned or deprecated contrib module to a newer one, which can be painful and labor-intensive...).
like you said, CCK and Views are obviously crucial, and many other contrib modules can't/won't upgrade until they do. so it just makes me nervous how fast core seems to keep pushing forward while 6 months after the latest major core upgrade, those 2 modules aren't ready yet.
anyway, i only started at 4.7, too. hopefully you're right that the 5 to 6 upgrade was a bit of an aberration this way... and again, i'm completely and utterly grateful for the time that all the developers put in -- this is not a complaint, just head scratching and looking for administrative sanity!