By Dries on

The past month we have been hard at work getting ready for the Drupal 4.2.0 release; we have been squashing bugs and made small improvements all over the map. We are now in the final phase of the code freeze which means we are down to a few remaining issues that need to be resolved. If you haven't already, please help us test. Report back your findings in the comments below or, if you found a bug, file a bug report.

The release candidate is available at:

http://www.drupal.org/drupal/drupal-4.2.0-rc.tgz

If you are using CVS, please take note that I created a DRUPAL-4-2-0 branch in our main repository. This branch will be used to harden the Drupal 4.2.0 code base before and after the release. As a consequence the HEAD branch is opened up for development. There are already a dozen of interesting patches waiting to be applied.

I'll create a DRUPAL-4-2-0 branch for the contributions repository as soon we made a change that could break backward compatibility.

Comments

Anonymous’s picture

(not verified) commented

Hi - Great news!

I'd suggest editing the post to give an explicit download link, or mention that this codebase is available as the 4.2 RC download (for those not familiar with CVS and branch naming).

Some less technical users may think they need to download the 4.2.0 branch directly from CVS (they don't right? The RC download is the frozen version? I'm confusing myself now...)

Anonymous’s picture

(not verified) commented

I've been following the Drupal 4.2.0 RC release, but now you got me confused also!

Dries’s picture

Dries commented

I updated the announcement a bit; I added a download link, rephrased some sentences and added some links. Thanks for the suggestions, and hopefully it is better now.

Clancy Ratliff’s picture

Clancy Ratliff commented

Would I be able to upgrade from my current version easily? I don't know jack about the inner workings of software, but would the new version just overwrite some stuff and add new features where applicable?

krose’s picture

krose commented

I'm posting this bug here because I can't get the bug submission forum to accept a new bug. (is this broken? if it's just my stupidity, which is highly likely, I apologize for putting this here)

Since loading the latest release candidate last night, several (but not all) of my rss "content syndication > news aggregation" feeds are not working. When trying to "update items" I get a screen that says "terminated request because of suspicious input data". For example, for "http://dijest.com/aka/rss.xml" the following is in the monitoring log...

Type: warning
Date: Tuesday, July 8, 2003 - 05:46
User: krose
Location: /drupal//?q=admin/syndication/news/update/19
Message: terminated request because of suspicious input data: (... detail supplied on request ...)
Hostname: 65.29.178.151

However, for some feeds (for example "http://www.elearningpost.com/index.xml") syndication is still working fine.

Anonymous’s picture

(not verified) commented

Hi all,

I just put up a Drupal 4.2 system to manage my blog from the SuperNova conference (this hopefully will get the project some attention also since this conference has a number of (spare me) a list bloggers present) and its going great.

Its here:
http://feedster.com/superblog/

And a quick review of 4.2 is here:
http://feedster.com/superblog//?q=node/view/3

Anonymous’s picture

(not verified) commented

Forgot to log in dag nab it.

kika’s picture

kika commented

Thanks for your kind review!
I try to comment some of the points you are making:

When I am logged in as an author using the xTemplate theme, I don't see a wysiwyg environment. Now this doesn't bother me but it was surprising.

Yep, currently you have to download an optional plugin

Registration for adding comments is required and
that's just plain wrong. Sorry. Its just plain wrong.

Enable "post comments" permission for anonymous users.
Does it work now?

The CENTER tag is allowed even though I didn't
specifically enable it

I do not get it. When I add <center> tag to text here, its getting filtered out. How it is allowed in your site?

There is no default permalink for an entry in the
xTemplate theme (or the marvin theme).
That's a big mistake imho.

You mean permalink icon or "#" mark? Should it be next to blog entries or next to all content items?

Thanks again, keep us posted

moshe weitzman’s picture

moshe weitzman commented

The CENTER tag is allowed even though I didn't specifically enable it

i think there is a permission to avoid tag filtering. I bet Scott has this permission (or he is user #1).

You mean permalink icon or "#" mark? Should it be next to blog entries or next to all content items?

IMO - All content, including comments. I think these should be emitted by node_link() and comment_link() respectively. We should remove the blog_link() icon thing

cel4145’s picture

cel4145 commented

"You mean permalink icon or "#" mark? Should it be next to blog entries or next to all content items?"

How about making the title a link? There are so many links already in the nodelinks area, adding permalink or # just, in my mind, will make it more cluttered (especially, thinking of what a weblinks node with multiple categories looks like).

While certainly this is not the most popular convention--for some reason blogs have standardized with "permalink" or "#" or the date--it is used with PostNuke and some other CMS's.

Dries’s picture

Dries commented

I'll add a permalink later today. Stay tuned.

jcwinnie’s picture

jcwinnie commented

Am I misperceiveing or did this fail to happen?

ax’s picture

ax commented

(using the xtemplate theme)

Mike@frazierhome.net’s picture

Mike@frazierhome.net commented

Very nice site Scott and nice review of Drupal. I tried logging in to your site using my account from my Druapl site (same one I use here) and it worked (as far as letting me be logged in) but I had no privs to do anything (including seeing any content on the front page).

You need to go into the admin page, user management, user permissions and then make sure everything is setup there properly for the various roles.

Also, the account you are blogging with is the #1 user (Drupal Superuser if you will). This is why you can use tags you thought you shouldn't be able to use.

Anonymous’s picture

(not verified) commented

Thanks for the feedback. Sigh. I always get the perms wrong when all I'm trying to do is setup a simple blog w/ drupal.