Announcing DRUPAL-7-0-UNSTABLE-3
Hello, devel list! :) Due to travel and other factors, it has been about a month since our last unstable release. There are some really exciting, big patches coming down the pipe, so I wanted to roll this interim release so contributed module developers interested in chasing HEAD have something a bit more current to build from. See http://drupal.org/node/224333#UNSTABLE-3 for the full list of API changes this release. Here are some of the things we've been up to for the last month. Once again, I encourage contributors to use http://groups.drupal.org/patch-spotlight as a place to organize, prioritize, and coordinate on patches they'd like to see in Drupal 7. For developers: =============== - drupal_set_title() now check_plain()s by default, which should help developers prevent XSS. - Performance improvements: the registry now keeps a record of all modules that implement a given hook, and caches registry lookups. - Taxonomy gets some love, with new hook_taxonomy_term_load/insert/update/delete() hooks and various standardization/consistency improvements. - SimpleTest now remembers the tests that were last selected so they can be re-run (WOOHOO) and can catch errors and warnings that come up during test runs, even if they're not part of an actual assertion. - Improvements to drupal_add_js(), which now has some cleaned-up parameters and a full-on weighting system for scripts. More drupal_add_js() improvements are in the pipeline, and expect them to make it over to drupal_add_css() as well. - Ground work has been laid in the database system for supporting of more exotic database drivers. Expect to see SQLite support in UNSTABLE-4! - Also on the database side of things, numerous files and modules have been converted from legacy syntax to the new DBTNG syntax. A great place to help out if you're interested in learning this stuff hands-on in advance of when you are forced to. ;) For users: ========== - New, swanky password checker during installation and on the my account page. - Cron is automatically run once upon installation so that Drupal doesn't immediately clobber you with a nasty error as a way of saying "Welcome." - The content types administration screen shrinks down the "in-your-face-ness" of the machine name of the type. - It is now possible (though not easy ;)) to upgrade from Drupal 6 to Drupal 7! Unfortunately, this currently still requires some manual futzing with settings.php. See http://drupal.org/node/304163 if you'd like to help. Looking forward to your patches/reviews in the issue queue! :) -Angie -- Join us at Do It With Drupal! A large scale, curated education event December 10-12, New Orleans http://www.doitwithdrupal.com
Nice to see more unstable releases coming, this (coupled with the advances in automated patch testing) is really moving core development to a new level of maturity. Yay. However... On Nov 13, 2008, at 12:19 AM, Angela Byron wrote:
- Cron is automatically run once upon installation so that Drupal doesn't immediately clobber you with a nasty error as a way of saying "Welcome."
Where's the issue nid for this change? This seems like a regression to me (this means the requirement check for cron not running is now totally useless, since cron will always have run once, giving site admins a false sense that everything's ok). However, I'd like to argue about this in the appropriate venue. ;) Thanks, -Derek (dww)
On Thu, Nov 13, 2008 at 10:27 AM, Derek Wright <drupal@dwwright.net> wrote:
Where's the issue nid for this change? This seems like a regression to me
http://drupal.org/node/93509 It seems like your concern is at least somewhat addressed in the discussion and implementation of the issue. I found this with: cvs-release-notes.php DRUPAL-7-0-UNSTABLE-2 DRUPAL-7-0-UNSTABLE-3 | grep cron <li>- Patch <a href="/node/296321">#296321</a> by pwolanin, swentel: link to cron.php broken when clean URLs are disabled.</li> <li>- Patch <a href="/node/93509">#93509</a> by catch: automatically run cron after installation, improve the cron notifications.</li> Yay cvs-release-notes.php! @Webchick - maybe when you make these announcements you could put the results of cvs-release-notes.php at the end of the announcement? Thanks, Greg -- Greg Knaddison Denver, CO | http://knaddison.com | 303-800-5623 Growing Venture Solutions, LLC | http://growingventuresolutions.com
On Nov 13, 2008, at 9:37 AM, Greg Knaddison - GVS wrote:
It seems like your concern is at least somewhat addressed in the discussion and implementation of the issue.
Mostly. Reading the patch did, however. ;) They removed the "cron never ran" requirement check entirely, and now rely on the "it's been a while since cron ran" warnings to remind admins they have a problem. That works. Sorry for the false alarm... -Derek (dww)
Derek Wright wrote:
Where's the issue nid for this change? This seems like a regression to me (this means the requirement check for cron not running is now totally useless, since cron will always have run once, giving site admins a false sense that everything's ok). However, I'd like to argue about this in the appropriate venue. ;)
Thanks, -Derek (dww)
Lacking an issue link, I'll add my cents here... 1.) Yes, it's necessary to inform admins that they need to set up cron. 2.) It's also annoying to formulate this information as an error message. It's a bit like showing a "This password is incorrect" message on a login form before you enter anything. Considering that the "cron has never run" case can /only/ happen just after installation, perhaps there should be no drupal_set_message() warning at all, just a step in the site setup process? "1. Configure your website: Once logged in, visit the administration section, where you can customize and configure all aspects of your website. {You need to set up a cron-job on your server to perform regular database maintenance.}" Something like that? -- Arancaytar ---------------------- Nothing beside remains: Round the decay Of that colossal wreck, boundless and bare The lone and level sands stretch far away... ---------------------- PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x27CA5C74 XMPP: arancaytar.ilyaran@gmail.com AOL: 282026638 / RealArancaytar URL: http://ermarian.net
participants (4)
-
Angela Byron -
Arancaytar Ilyaran -
Derek Wright -
Greg Knaddison - GVS