Starting the new year off with a bang, the Drupal development team is pleased to announce that the third Drupal 4.7.0 beta release is available for immediate download at http://drupal.org/files/projects/drupal-4.7.0-beta3.tar.gz! This beta release marks an important step towards the final Drupal 4.7.0 release and significant progress from our previous beta release: we've fixed over 100 bugs since the last beta release and more than 150 bugs since the first beta release. Here is the changelog. However, there are more bugs to be found, reported, and fixed before Drupal 4.7.0 can be released. The good news is that you can help!
The current focus of the Drupal contributors is very clear: we're fixing the remaining bugs and getting the documentation up-to-date to make 4.7.0 the best release yet. Additionally, work has begun on updating contributed projects to 4.7.0. There are currently over 335 contributed projects (modules, themes, and translations) available for Drupal 4.6. 75 have already been updated to work with Drupal 4.7.
Here are some ways that you can help out with the 4.7.0 release:
- Download Drupal 4.7.0 beta 3 and install it on a test platform. You can use the development module to quickly populate an empty database with sample data or you can upgrade an existing Drupal 4.6 database.
- Get your users to participate on a test site. We've found the best way to discover new bugs is for many people to try many different things with the Drupal site. You may find bugs by looking through the log files as well.
- Participate in the Drupal bug hunt. Prizes are awarded to the people who find the most bugs!
- Go to the patch queue and review some of the latest patches.
- Fix bugs! You can learn a lot about the Drupal system by fixing the bugs others find. You can ask questions and work on debugging with other Drupal developers on our IRC channel, #drupal on the irc.freenode.net IRC network. They're busy fixing bugs too, but many, if not most, are willing to give pointers and assist anyone who wants to help!
Release notes
- Important database changes have been made in this release. If you are upgrading, make sure to run the database upgrade script. Instructions for installing or upgrading Drupal can be found in INSTALL.txt or UPGRADE.txt, as well as the handbook.
- As with anything still in development, take precautions with your data before upgrading.
Comments
Yay!
Thanks to everyone. :)
Update: Beta2 to Beta3 update went smoothly.
--
http://dave.notik.com
Well done, I'll try it now!
and I'll partecipate with happiness at the bug hunt!
Thank you for your wonderful job, guys!
An ex-postnuker, now devoted to drupal :-)
update:
I've just upgraded my test site from beta2 to beta3 with no troubles!
what's changed?
it'd be great to have a link to what's changed between the betas on these pages. i'm sure that somewhere on the site this information exists, we just have to look for it... but it'd be really handy to have this info here, especially since the changelog doesn't have any of it and because searching for drupal 4.7 beta 3 really doesn't do much good.
or maybe just list the highlights: crippling bug x and y changed!
You can get close to knowing
You can get close to knowing what has changed by looking at issue tracker items that are closed or fixed that were in a version of 4.6.3+ or 4.7x or cvs that were last updated in the last few months.
Take a look at this issue query:
http://drupal.org/project/issues/drupal?page=0&projects=3060&versions=97...
Go back a few pages and you can see that there are quickly a large number.
The CHANGELOG.txt is more high level at the "4.6x to 4.7" level of information.
You could also look at the archives of the cvs mailing list log messages, but man would that be tedious to try to do post-hoc.
http://lists.drupal.org/pipermail/drupal-cvs/
Greg
--
Knaddison Family
--
Morris Animal Foundation
link added
i added a link in the story to the cvs changelog
Run update
Nice new beta.
You guys out there trying it out. Even if you have beta2 - login as admin (UID 1) and run update.php, as there are a few db changes.
Gunnar Langemark
http://www.langemark.com
Thanks ...
... to You Drupal people, for Your hard work on 4.7 which is very much appreciated.
I recommend a glimpse to the CVS-changelog to anyone being tempted to ask the "four-letter"-question. ;)
4.7 will be a great release and I'm looking forward to it!
Update error, my mistake
This was my first update, Beta 2 to Beta 3. I made the mistake of not logging in before running update.php. When will I read my instructions? Anway, the original message indicated that I did not have proper access to run the file. So, I logged in and then ran update.php with the same no access messages. A few minutes later, I ran it and everything was fine. The only thing I could think of as to why I couldn't run update.php right after logging in was as anonymous user the results of the update.php (no access) was cached. Does that sound right?
By the way once updated, would it not be safer to then remove the update.php file from the directory? It's probably safe to keep it there, but it seems to be common practice among other CMS I've installed.
Good work to the 4.7 developers. The improvements in all the administrative/settings menus really are a huge leap forward...Drupal feels a lot more solid to me than 4.6.
-Bryan
Under Development Drupal Site:
http://cmsreport.com
New SMF Site:
WebCMS Forum
Simple solution :)
Edit the update.php file. There's an easy to change flag on line 18 that removes the need to log in as admin.
$access_check = TRUE;
should become
$access_check = FALSE;
Then run update.php and alll should be good. Just remember to change it BACK -- this opens up a pretty major security hole, as any user can hit the page and run updates. ;)
--
Jeff Eaton | I heart Drupal.
--
Eaton — Partner at Autogram
Where to start?
From the project's development standpoint, what bugs are most critical to correct at this point: Critical 4.7.0-beta3, 4.7.0-#, or cvs?
Should we verify criticals on previous versions (4.6.#, etc) are corrected?
I've finally gotten some free time in the evenings now that a huge code cycle completed at work, and want to jump in where it will be considered best needed.
I think all of the above
I think all of the above areas need help:
From http://lists.drupal.org/archives/development/2005-12/msg00402.html
This issue list:
http://drupal.org/project/issues?projects=3060&categories=bug,task&prior...
Similarly - from:
http://lists.drupal.org/archives/development/2005-12/msg00427.html
"Just pick the issues that look _fun_ to work on" seems reasonable to me.
--
Knaddison Family
--
Morris Animal Foundation
Most important
Most pressing are critical bugs filed against CVS HEAD, 4.7.0 beta 1, 4.7.0 beta 2 and 4.7.0 beta 3. Any other bug that looks fun to work on is much appreciated as well. Other than that, we welcome performance and usability improvements.
The DRUPAL-4-6 branch is still being maintained so patches that fix bugs reported against Drupal 4.6 are committed and will be part of the next 4.6 release.
Looking forward to your patches/reviews.
Thanks
That was exactly what I was looking for. Looks like about 50 criticals to go for 4.7 RC
GREAT :-) At the moment any bug vs lots of good improvements
We are testing the v4.7.3 with very good improvements.
The event module fits perfectly
http://207.58.183.27/?q=event/2006/04/25/day
Geat job and deserved wait
This is _not_ "v4.7.3" this
This is _not_ "v4.7.3" this is version "v4.7.0 BETA 3".
Very important distinction :)
--
Knaddison Family
--
Morris Animal Foundation
does update.php work?
Has anyone successfully updated from either 4.5.* or 4.6.* to this current beta?
bug: http://drupal.org/node/40646
I did but not with the
I did but not with the official beta 3 but with the CVS version (yesterday). This was the first time it worked for me. tried beta 1 and beta 2 before....
Problems with upgrade
After upgrading my database I browsed to my main page
and I cannot see any blocks.
When going to myhome.com/user and trying to edit my user I cannot change the theme (I think it might be the problem)
the list is just not there
b.t.w I have upgraded from 4.6.3 to 4.7 Beta 3
any ides?
Thanks
How did you upgrade?
How did you upgrade?
Did you install the same themes that you had under 4.6.3 into your 4.7 installation?
Go to http://example.com/?q=admin/themes/ where you should be able to edit the enabled themes and then install from there.
This is reported as an issue here: http://drupal.org/node/42935
Though really, I'm not sure that thierry_gd's solution is the best:
"* check if the theme specified in the DB is one of the one bring with drupal ==> if it not the case set it by default to "bluemarine" else do nothing"
I think this is more of a documentation/installation guide problem which should say "as you upgrade you either need to install the same themes in the new installation or set your system to use the base themes before taking your DB backup".
--
Knaddison Family
--
Morris Animal Foundation
Same thing happened to me
I was also upgrading from 4.6.3 to 4.7 Beta 3 and lost all my blocks.
Even after going manually to www.example.com/admin/themes and changing to one of the default themes, the blocks were not visible.
I ended up going to www.example.com/admin/block and saw that all blocks were disabled (even though they'd been enabled on my 4.6.3 installation). Enabling them fixed the problem.
taxonomy -> category
I read that taxonomy is changing to category, taxonomy_menu is becoming category_menu, and distant parent is now built in. Is there a page describing the changes in that area?
Are there any other modules that are replaced instead of being updated?
petermoulding.com/web_architect
petermoulding.com/web_architect
its only a word
There are some changes in the module itself, but it really still **is** taxonomy. People just wanted to change the word into categories, nothing more.
So, in other words, don't think that finally taxonomy is very easy, just because it is now under a link called categories. It still offers the same huge power, the same complexity that comes with that power.
---
Bèr Kessels
Professional www.webschuur.com
Personal bler.webschuur.com
Category module
I found the module: http://drupal.org/node/39692
The module roles together a few things I use. category_menu adds a couple of things I was about to code for taxonomy_menu. I can throw away my modifications to taxonomy_menu.
petermoulding.com/web_architect
petermoulding.com/web_architect
Great!
No problems here upgrading Drupal 4.7b2 to b3. Running PostgreSQL 8.1.1 and PHP 5.0.5.
We will definitely test
We will definitely test this.
Marcel
http://computingnews.com
Beta 4? RC1?
Is another beta due? Is a release candidate likely?
The CVS version has enough modules converted for me to convert to 4.7 but I do not want to use something as fluid as the CVS version. I prefer a beta version or release candidate because that is at a known point.
petermoulding.com/web_architect
petermoulding.com/web_architect
beta4
http://drupal.org/drupal-4.7.0-beta4
It's my impression that a beta5 and/or Release Candidate (RC) is likely in the next couple of weeks. 4.7.0-beta4 has several problems that have been fixed so if you can wait a little while than the next release might be a good way to go. The database updates between beta releases - while not really super official and supported, I mean, how do you bugfix something like that - work pretty well so you could also just start with 4.7.0-beta4 and use the upgrade to get to the next releases and finally up to the release version.
--
Knaddison Family Blog
--
Morris Animal Foundation