A bit over a month after the release of fourth beta release the Drupal development team is pleased to announce the fifth beta release of Drupal 4.7.0! It is available for immediate download.

This beta release is hopefully the final beta release for Drupal 4.7.0 and marks a significant improvement in the Drupal 4.7.0 codebase. Since beta 4, a lot of critical and non-critical bugs have been fixed. All of these changes are detailed in the changelog. However, there are still more bugs to be found, reported, and fixed before a release candidate can be made. The good news is that, with your help, we can release Drupal 4.7.0 RC1 much sooner.

  1. Download Drupal 4.7.0 beta 5 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.
  2. 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.
  3. Go to the patch queue and review some of the latest patches.
  4. 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

stephenhendry’s picture

Thanks goes to all the people who been fixing bugs in all the beta release. Time to install :-)

--------------------------------------
http://www.stephenhendry.net

capmex’s picture

Thanks for all your efforts! I think now it's time to roll up a few sites on this platform. I'm eager to test the new file cache patch.
--
Webmaster Resources | Canadian Directory

naudefj’s picture

I'm also going to run my sites with the file cache patch installed. Just a pity it will not make it into 4.7.

archetwist’s picture

Thank you. Drupal is a great piece of software but I have to say I don't like the (visual) changes in the book module at all. Old navigation box with 'next' and 'previous' was better and looked nicer. '<' and '>' symbols are less intuitive and new li.leaf image is awful.

Morbus Iff’s picture

That's themable now, btw. Have a blast changing it back. The same new navigation applies to forums as well and, like you, I disliked it immensely. I themed it back into the links location, like before.

http://www.disobey.com/
http://www.gamegrene.com/
Developer of Drupal's Game API

archetwist’s picture

Hmm, I thought one has to edit book.module in order to change it back. Any advice how to do this the smart and fast way? ;)

Morbus Iff’s picture

Assuming you know how to theme, you'd want to override theme_book_navigation().

http://www.disobey.com/
http://www.gamegrene.com/
Developer of Drupal's Game API

archetwist’s picture

Thanks. Old-style navigation is back.

marknewlyn’s picture

Please can you post the snippet?

Mark

archetwist’s picture

I've modified it a little bit so this is neither beta5 nor beta4 version (but similar to beta4)

Put this in your template.php file (PHPTemplate theme required):

function phptemplate_book_navigation($node) {
  $output = '';

  if ($node->nid) {
    $output .= '<div class="book-navigation">';

    if ($tree = book_tree($node->nid)) {
      $output .= '<div class="tree">'. $tree .'</div>';
    }

    if ($prev = book_prev($node)) {
      drupal_add_link(array('rel' => 'prev', 'href' => url('node/'. $prev->nid)));
      $links .= '<div class="prev">';
      $links .= l(t('previous'), 'node/'. $prev->nid, array('title' => t('View the previous page.')));
      $links .= '</div>';
      $titles .= '<div class="prev">'. check_plain($prev->title) .'</div>';
    }
    else {
      $links .= '<div class="prev">&nbsp;</div>'; // Make an empty div to fill the space.
    }
    if ($next = book_next($node)) {
      drupal_add_link(array('rel' => 'next', 'href' => url('node/'. $next->nid)));
      $links .= '<div class="next">';
      $links .= l(t('next'), 'node/'. $next->nid, array('title' => t('View the next page.')));
      $links .= '</div>';
      $titles .= '<div class="next">'. check_plain($next->title) .'</div>';
    }
    else {
      $links .= '<div class="next">&nbsp;</div>'; // Make an empty div to fill the space.
    }
    if ($node->parent) {
      drupal_add_link(array('rel' => 'index', 'href' => url('node/'. $node->parent)));
      $links .= '<div class="up">';
      $links .= l(t('up'), 'node/'. $node->parent, array('title' => t('View this page\'s parent section.')));
      $links .= '</div>';
    }

    $output .= '<div class="nav">';
    $output .= ' <div class="links">'. $links .'</div>';
    $output .= ' <div class="titles">'. $titles .'</div>';
    $output .= '</div>';
    $output .= '</div>';
  }

  return $output;
}

Styles:

.book-navigation {
	clear: both;
	}
.book-navigation ul li {
	margin-top: 0;
	}
.book-navigation .nav {
	border-top: 1px solid #888;
	border-bottom: 1px solid #888;
	padding-bottom: 3em;
	padding-top: 1em;
	clear: both;
	}
.book-navigation .nav .links {
	clear: both;
	}
.book-navigation .nav .titles {
	clear: both;
	}
.book-navigation .nav .prev {
	float: left;
	text-align: left;
	width: 45%;
	}
.book-navigation .nav .next {
	float: right;
	text-align: right;
	width: 45%;
	}
.book-navigation .nav .up {
	text-align: center;
	}
aplourde’s picture

I've been running the upgrade script on my test site (4.7b4) for about half an hour and it is still going. I figured it stopped working, or completed without giving a message. So I opened another browser window, browsed to the site, a found a whole bunch (and I mean a LOT) of the following error:

warning: reset() [function.reset]: Passed variable is not an array or object in /srv/www/htdocs/update.php on line 402.

If I refresh the screen I get fewer of the same error the second time. This tells me the upgrade script is still running.

Not sure if everything is cool, or if the process broke. My test site was a little flakey (I've been messing with it a bunch) so that may be part of it.

Adam B. Plourde

EDIT: I canceled the upgrade script and the site seems to be working fine. I'm not sure what was happening; but everything looks fine at the moment.

Duplika’s picture

Yup, same happened to me.
--
Duplika | Web Hosting

chrisd’s picture

Something here, I think on the 2nd upgrade (on 2 different sites).

First upgrade went fine.

Second one is still running (been running for 10 minutes?).

Using File Monitor, I can see MySQL hitting real hard the database (for my upgrading
site): sessions.myd and a little less users.myd

No sure about this but I think the first upgrade had the "select version"
expanded, were the second upgrade did not.

When I expanded it, it showed the same version as the first (1.72? not sure about
this version number)  so I proceeded.

It's still going on....will wait an extra 10 minutes and stop it?....

Update 10 minutes later:

I had to stop the update.

Did I reload and got errors...

I restored my database (pre-beta 5  upgrade)...thank you to for point 1
in upgrade.txt.

After reading:
http://drupal.org/node/49501
I decided to run the upgrade.php from Internet
Explorer (was using FF 1.5.0.1)and it worked (so far)!

 

Tech. articles with a WAMP+IIS+Drupal focus:
http://www.sitebuddy.com/

Artem’s picture

I had the same experience. Upgrade progress indicator was running endlessly in Firefox 1.5.0.1, in IE 6 everything went fine

zirvap’s picture

Could these problems possibly be caused by this bug in Firefox? Summary:

window.setTimeout() goes crazy periodically - functions are immediately called repeatedly

or possibly this related bug:

Timers fire way too quickly in some cases.

During heavy page load, our timer code gets horribly confused and starts firing
timers very quickly (a requested delay of 50ms becomes 1ms in some cases).

It's possible that I'm far out in the fields with this guess. I stumbled over a mention of these bugs because of an issue mye webhost is having with another application, but I won't claim to understand much (or any) of the complexities here.

Dries’s picture

We fixed a number of update.php glitches in beta 5, but from the looks, we're not there yet... Give beta 5 a try and report back at http://drupal.org/node/49501.

gdip’s picture

Safari browser seems to hang for a looong time trying to upgrade the database to beta5.
Camino 1.0 went quickly without a hitch.

archetwist’s picture

I've just noticed that the upgrade changed dates of all existing comments to 1970-01-01 01:00.

Dries’s picture

For your information, we fixed about 160 bugs since beta 4. That makes for 5-6 bugfixes a day.

Unfortunately, there are more than 400 active bug reports of which 13 critical bugs that are blocking the Drupal 4.7.0 release. We plan to release a Drupal 4.7.0 release candidate (RC) when there are no critical bugs left. If you want to contribute code, help us fix critical bugs. The focus is very clear. The week there are no critical bugs left, we'll roll a (first) release candidate.

As a reference, there are about 200 active bug reports filed against the Drupal 4.6 releases, of which 14 are critical bugs.

rkendall’s picture

Just to say thanks for being strict on the bug-fixes. It is worth waiting for a quality release.

chrisd’s picture

My 2 cents:

We might want to go for another round (Beta 6?) with no new critical bug
appearing, before a ReleaseCandidate of Drupal 4.7.

I'm kind of new here, so I'm not sure, if the RC evaluation "crowd" will be
that different from the Beta testing "crowd".

If the RC of Drupal 4.7 attracts a "way" larger crowd (press, reviews,
managers ..etc...), I recommend another round of beta with 0 critical bugs,
which in turn should not generate any new "show stoppers" (i.e. critical
bug(?)).

Personally, I did have install/upgrade problems with Beta 3 and Beta 5 (each
time, fixed very quickly) and would "hate" to see people, make a quick and
undeserved opinion, on Drupal 4.7, just because of one of these install issues.

Thank you for the quality work this community is producing,

Christophe



Tech. articles with a WAMP+IIS+Drupal focus:
http://www.sitebuddy.com/

Walt Esquivel’s picture

On 3/3/06, Dries wrote there are 13 critical bugs blocking the Drupal 4.7.0 release.

Five days later, on 3/8/06, I looked at the link he provided and see there are now 16 critical bugs.

In trying to understand the impact critical bugs have on a particular release, do all 16 bugs need to be fixed before the Release Candidate is released? As of 3/8, 11 critical bugs are marked CVS while 5 are marked 4.7.0-beta5, so I'm confused and simply trying to understand which critical bugs are holding up the RC. All 16 or only the 5 marked 4.7.0-beta5?

Any info greatly appreciated. Also, thanks to the many developers for ALL their wonderful contributions to the Drupal project!!!

Thanks,
Walt

P.S. Minor note, but could the Project and Status drop-down boxes be widened so that the full text in them can be read? Many choices in these drop-down boxes are cut off. Thank you!!! :)

-----
Walt Esquivel, MBA, MA, Captain - U.S. Marine Corps (Veteran)
President, Wellness Corps, LLC
-----
Drupal Users and Developers by Geographical Location
http://drupal.org/node/46659

Dries’s picture

Walt, all critical bugs files against Drupal 4.7.0-beta1 and above (including 'cvs' or 'CVS HEAD') need to be fixed before we can roll a release candidate. That is, we need to fix all 16 of them. Hope that helps. Please help us fix those pesky bugs! :)

celticess’s picture

Just when you think the number is down it's up. j/k ;) I heard the podcast and it was 8 then 12. I don't suppose you've noted the bug I ran into where it dumps UID1 and prints to screen the new password though seems to keep the UID name because it also prints that to screen? That was the only bug I've had with it but due to the nature of it, well it's also the reason I took 4.7 out. :( I love the changes in 4.7 and I'm really looking forward to it's release though.

Since I've downgraded to 4.6.5 I now have that weirdness(fresh install too just like the 4.7 was) where I'm getting access denied on my own posts for editing. I'm puzzled at that as in past 4.6's I've used I've never had that happen nor the missing "content type" list for editing the default posting options for them.

celticess’s picture

But then I downgraded back to 4.6.5. I don't know why but it seemed to of lost UID one stuff and it dumped out a password and notification I was user 1 to screen. The day after I did my install. The day of my install I had no problems. I have no idea what caused the weirdness and despite lack of some of the modules being in 4.7 version now I'd of perferred to keep the site 4.7

Unfortunately now 4.6.5 also borked for me. :( I've used several of the 4.6's and this is the first time that when I've gone to edit my own blog entry I get "access denied" and I'm logged in as admin. First time content types aren't listed for me to edit defaults.

If your wondering my hosting I've turned on php5 and run as cgi, I also have mysql 4.1 they claim(but the drupal 4.7 sysinfo module says it's 5.0.1 mysql)

I don't suppose you have an idea to fix the problem in either 4.7 or 4.6.5? I might wipe the db again as it was a fresh install and reinstall all over again. *sigh* (that's in the 4.6 as I see that dumping UID 1 in 4.7 as a security issue... btw that was the only 4.7 bug I ran into)

killes@www.drop.org’s picture

Can you make a copy of your pre-upgrade database available for debugging?
--
Drupal services
My Drupal services

celticess’s picture

I wiped the db and did a fresh install of 4.6.5 which fixed the 4.6.5 error(not sure what was making it weird but glad it's gone). The 4.7 error I should of maybe screenshot but I had posted the screen output I think in my post asking when the final release of 4.7 might be. Basically it said on main page in a message box that I was UID1. It then had the right UID1 user name but gave a generated password. I considered that a really bad thing so immediately took it off my hosting. Because though I was the one to see that it could of been anyone visiting my site. Had I been busy they could of done who knows what having admin access.

Oh and editing this because I forgot to mention. When I had 4.7 beta 5 in it was a totally fresh install. I didn't use my original 4.6x db or anything. So the problem isn't an upgrade problem. It was something that happened to a totally clean/fresh install. When I down graded because of the error on 4.7. I am aware the database mysql was likely different so I totally wiped the db I'd created dropping all. Then I used php admin and loaded the one for 4.6.5 and did a fresh install on my website of the 4.6.5. The only thing I put in 4.6.5 from my original 4.6x site was a theme I'd made.(Marvin Black if you look at my website now it's working and it's the theme in use)

vph’s picture

I think there's a bug ... don't remember the specific as I can't look at the codes right now. But basically, when I tried to implement a callback, passing parameters to function doesn't work. Only the first parameter is obtained properly.

Something like this:


function tax_menu($may_cache) {
  $items = array();

  if (arg(0) == 'node' && is_numeric(arg(1))) {
    $node = node_load(arg(1));
    if ($node->nid && taxonomy_get_vocabularies($node->type) != NULL) {
        $items[] = array('path' => 'node/'. arg(1) .'/tax',
          'title' => t('tax'),
          'callback' => 'tax_edit',
          'callback arguments' => array(arg(1)),
          'type' => MENU_CALLBACK);
     }
  }

  return $items;
}

where tax_edit is defined as ...

function tax_edit($node_id) {
  $op = $_POST['op'];
  $edit = $_POST['edit'];

  if (empty($op)) {
    $op = arg(2);
  }

  switch ($op) {
    case t('Submit'):
      // other stuffs
      $output = tax_view($node_id, 1);
      break;
    case t('Submit2'):
     // other stuffs
      $output = tax_view($node_id, 2);
      break;
    default:
      $output = tax_view($node_id, 3);
  }


  print theme('page', $output);
}

and then ...

function tax_view($node_id, $extracted=0) {
   // other stuffs
   return $output;
}

The thing is the parameter $extracted in the function tax_view above doesn't seem to get the values passed to it. I don't recall having this problem when modifying 4.6.5

kvarnelis’s picture

i found that my update went awry because i inadvertently started the process a few seconds before the turn of the hour.

the update never completed, but when i dumped the database and restored it from a backup, it was fine. either the dumping/restoring cleaned things up or the first time failed because the hourly cron.php cycle kicked in (something that the logs indicated did happen).

BryanSD’s picture

As far as I know, I survived the update from 4.7 B4 to B5. Though I recall doing a refresh a couple times in Firefox 1.5 before getting the screens I needed. As others noted, I too had problems being logged as UID 1 but not really having access. I closed the browser and when I opened back up, logged into Drupal and all was fine. No errors were logged within Drupal. Just strange...

Drupal Test Site:
CMSReport

celticess’s picture

Just went straight b5. I had tried two different browsers. I got the error initially in firefox. I sort of thought "huh what? ok lets try that again in opera" Same error. I figured if I did go in and set my UID1 password again it was likely to spontaneously do this weirdness again. Simply because it did it in 2 browsers. I'm using the latest opera and firefox too as I'm using AMD64 with accept keywords in Gentoo Linux.

The only error other than the print to screen one involving UID1(which was odd because I'd config'd it to not print to screen only to log). Were ones that involved me attempting to use CVS modules I thought might work too. Little things I missed like recipe and paypal. So the errors in the log I saw for those were the php form errors due to changes. When someone later pointed out that yea there was an issue that way I just turned off the modules affected and it was fine. Well til it burbed on UID1.

peterx’s picture

Has tried 4.7 on 5.1.2? I just switched a 4.6.5 site from PHP 5.0.5 to 5.1.2 and had to remove an XML feature because it no longer worked.

petermoulding.com/web_architect

celticess’s picture

I had no problems until a day after the install when I had it do the print to screen of UID name and a generated password. Which is why I took it out of my hosting and replaced it with latest 4.6x

toma’s picture

Check out

http://www.drupaldemo.org

Enjoy

Drupal 4.7 beta 5 demo
http://www.drupaldemo.org