Drupal 7.0 Beta 3 released

Today marks reaching Drupal 7's 0 critical bug milestone! We've rolled one final beta release to shake out any last minute problems and fix strings. Please help!

This release includes:

  • Upgrade to jQuery 1.4.4 and jQuery UI 1.8.6
  • Numerous upgrade path fixes
  • Numerous accessibility fixes
  • All critical bugs fixed!

For the full list of changes, see the release notes.

Hey, wait! But there are 0 criticals! Why another beta?!

As of today, Drupal 7's critical issue queue has reached 0. A huge thanks to the tremendous effort of hundreds of people who have helped bring us to this momentous milestone!

By traditional definition, we should be entering release candidate phase. However, while we have been focused on smashing criticals, we have accumulated a "major" issue queue that's currently 5 pages long, and have been neglecting to prepare for string freeze, which happens at RC1.

So, Dries and I felt that it was appropriate to have one last chance to take a final pass through the issue queue and find any straggler release blockers that might still be buried, and to identify and fix issues that impact string freeze (anything that changes something wrapped within the t() function).

From Here to RC

So. If you're in MAINTAINERS.txt, or otherwise knowledgeable about the issues in the core queue, we urgently need your help in taking one last look at your queues over the next day or two and making sure there aren't any remaining critical issues buried in the "major" list.

Because Drupal is by definition release-ready right now, we are going to strictly timebox the following:

  • Maintainers have until 11:59 PM Pacific US Time Wednesday, November 17 (07:59 AM UTC) to dig up critical issues from their majors queue. Move them from "major" to "critical" so that we can discuss. (Note that these will have to pass an extremely high bar; we've had almost 3 years to identify such issues.)
  • While going through your queues, if you find issues that impact string freeze, please tag them "string freeze."
  • I want to roll RC1 to no later than November 30, 2010 (with the caveat of any new security/data loss issues will block the release if still active at that time). Ideally, we do RC1 even earlier (Dries's birthday is November 19, or failing that, US Thanksgiving represents a GREAT time for many of you to get away from your family and work on Drupal :)).

To be clear, once RC1 happens:

- All strings are frozen.
- All markup is frozen.
- The UI is frozen.
- The API is frozen.
- The theme system is frozen.
- Drupal 7.0's release is imminent.

So please, help do your part to get Drupal 7 DONE!

(What follows is the standard "how to test this alpha/beta release" spiel.)

"Install new module" link missing from Modules page

In a clean install of Drupal 7.0-beta2, while logged in as user 1, on the Modules page (/#overlay=admin/modules), there appears to be no "Install new module" link. I searched the HTML of the page, and the link text is not there. I have not changed the default admin theme from Bartik 7.0-beta2. This is my first encounter with Drupal 7, so I'm not sure, does something extra need to be done in order to enable that link?

Drupal 7 and OOP = learning Drupal from scratch ?

Hi. Im working with Drupal since 5.0, programming since 5.xyz(dont remember). Ive learned PHP just because I wanted to get some things into Drupal that I needed. Sicne then Ive got pretty good with both PHP and Drupal and it became my job.

The problem is that since Drupal wasnt OOP Ive learned to write my code in procedures. Now D7 is rewritten into OOP and Im lost. I know that D7 brings a LOT of new features but I feel like I need to learn Drupal from scratch.

Any ideas how to get back on track for gyus like me? I know there are a lot of us out there.

Modify Field Value based on another Field Value on Submit

Hello,
I'm stuck as to how to accomplish the following:

I have a Content Type with a required text Field_A, and a hidden text Field_B.
When a user submits a new node with a required text field (Field_A), I would like to run Field_A through a few functions, and generate a value for Field_B, so that both Fields are saved when the node is created.

What's the best solution for next / previous node navigation in Drupal 7?

At work I have a Drupal 6 site in which image gallery navigation was done with the Custom Pager module + Views.

For my new personal Drupal 7 site, I need a navigation solution (next / previous links) for my cartoons, which are built as a unique content type. There is no 7.x version of Custom Pager.

I would also like to avoid flash / jquery / popup solutions - I want to keep everything as simple and clean as possible. So what are my options?

CAPTCHA protected content

Hello, i would like to know if its possible to hide/protect a section of content from anonymous and new registered users using captcha, i do not know if I explaining myself well, so i will leave you with the following image:

http://i52.tinypic.com/2db0znd.jpg

Pages

Subscribe with RSS Subscribe to RSS - Drupal 7.x