Thanks for the note Korbus!<br><br>I've fixed the error.<br><br>Robin<br><br><div><span class="gmail_quote">On 1/12/06, <b class="gmail_sendername">Dries Buytaert</b> <<a href="mailto:dries.buytaert@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
dries.buytaert@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>Begin forwarded message:<br><br>> From: "Kobus Myburgh" <
<a href="mailto:itbjdm@puknet.puk.ac.za" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">itbjdm@puknet.puk.ac.za</a>><br>> Date: Thu 12 Jan 2006 07:52:40 GMT+01:00<br>> To: <<a href="mailto:info@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
info@drupal.org</a>><br>> Subject: [droppies] Re: [documentation] [Drupal newsletter] Drupal
<br>> Newsletter for Winter,2005/06 -- DRAFT 1<br>> Reply-To: <a href="mailto:droppies@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">droppies@drupal.org</a><br>><br>> In the last paragraph of Angie's Interview, there is this:
<br>><br>> But everyone has been so supportive and encouraging to me,
<br>> receptive to my input a nd feedback,<br>><br>> There is a space between the a and the nd of and.<br>><br>> That is all I noticed that wasn't noticed by someone else, so hope<br>> this helps!<br>>
<br>> Kobus<br>><br>><br>><br>><br>>>>> "<a href="http://Drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Drupal.org</a> newsletter" <<a href="mailto:info@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
info@drupal.org</a>> 1/12/2006 4:07:27 AM >>>
<br>><br>> ------------DRUPAL NEWSLETTER FOR WINTER, 2005/06 -- DRAFT<br>> 1------------<br>><br>> Please comment on this draft and fill in the gaps.<br>><br>> I'm afriad I have less time to work on generating content, and I
<br>> thank Steve<br>> Dondley for his work on this.<br>><br>> Robin<br>><br>> -----------------------------------------------------------<br>><br>> Editor's overall comment: Newsletter seems really geared to
<br>> developers. Is<br>> that desired?<br>><br>> (We can only publish what we get, more user content submitted, more<br>> gets<br>> published. Feel free to submit some. --Robin)<br>><br>> Not yet written...
<br>><br>> Module review: Views<br>><br>> *In this issue...*<br>><br>> * Upcoming Events – Learn about upcoming Drupal-lover events.<br>><br>> * Drupal Interview – This month's interview with Drupal
<br>> contributor, Angie<br>> Byron.<br>><br>> * Summer of Code Projects – Google's "Summer of Code" heats up<br>> Drupal<br>> development.<br>><br>> * Module Spotlight - A look at "Views," a powerful new third-
<br>> party module.<br>><br>> * Drupal Development Quickies – What have the developers been<br>> working on<br>> lately?<br>><br>> * Drupal Tips – Tricks to help you harness the full potential of
<br>
> Drupal.<br>><br>> * Status Update - In writing, please hand in.<br>><br>> ------------UPCOMING EVENTS------------<br>><br>> OPEN SOURCE CMS SUMMIT<br>><br>> All Drupal developers should plan to make their way to the west
<br>> coast of Canada<br>> for the event to kick off your year: the Open Source CMS Summit and<br>> DrupalCon,<br>> [<a href="http://drupal.org/conference-vancouver-2006" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/conference-vancouver-2006
</a>] February 7th thru<br>> 9th. As the<br>> event page says, this will be a developer-centric event focused on<br>> collaborating together on future directions and everyone's<br>> favourite topic --<br>> APIs!
<br>><br>> With it being peak ski season, developers will get a chance to<br>> enjoy British<br>> Columbia's coastal mountains, including the famous Whistler, for<br>> some of the<br>> best slopes in the world. For those who don't ski, there will be
<br>> plenty of<br>> beer going round at the lodge!<br>><br>> Chad Phillips and Angie Byron are the two main Drupal organizers,<br>> with Boris<br>> Mann and Roland Tanglao doing the Vancouver local organizing and
<br>> helping with<br>> the summit as a whole. Please join the Drupal conference mailing list<br>> [<a href="http://drupal.org/mailing-lists" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/mailing-lists</a>] and/or check out the wiki<br>> [
<a href="http://2006.northernvoice.ca/wiki/open-source-cms-and-blogging-" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://2006.northernvoice.ca/wiki/open-source-cms-and-blogging-</a><br>> tools-summit]
<br>> to add your own ideas to make this a great gathering of Drupalites.
<br>> Oh, and of<br>> course, flip the switch in your user profile to get listed on the<br>> attendees<br>> page [<a href="http://drupal.org/profile/conference-vancouver-2006" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/profile/conference-vancouver-2006
</a>].<br>><br>> ---------- Digitalclouds.Net - your Web Presence Provider ----------<br>> no more limits<br>> ... unlimited domains, unlimited MySQL dbs, unlimited e-mail ...<br>> 10% donated to Drupal,
1.5 GB extra disk space, 90 days money back<br>> <a href="http://www.digitalclouds.net/goto/xref/offers/supportdrupal/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.digitalclouds.net/goto/xref/offers/supportdrupal/
</a><br>> --------------------------------------------------------------------
<br>><br>><br>> ------------DRUPAL INTERVIEW------------<br>><br>> For this issue of the Drupal newsletter, Robin Monks interviews<br>> Angie Bryon,<br>> (a.k.a. "webchick."). Angie came to our community at the end of
<br>> June 2005<br>> through Google's Summer of Code [<a href="http://code.google.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://code.google.com/</a><br>> summerofcode.html]<br>
> program designed to help bring new talent and support to important
<br>> open source<br>> projects. Angie's current focus is improving documentation and<br>> generally<br>> helping out wherever she can with graphics work, user support, module<br>> extensions, and the countless other tasks that go into the Drupal
<br>> open source<br>> project. Read on to learn more about Angie's self-styled "Winter<br>> of Code"<br>> program and what motivates her to stay involved.<br>><br>> *So, how did you originally find Drupal?*
<br>><br>> Back a year or so ago, I came across the SpreadFirefox.com website,<br>> and was<br>> involved there for a little while making some posters. Their site<br>> was clean and<br>> easy to use, so I did some "homework" and determined that it was
<br>> running<br>> CivicSpace, which is based off of Drupal. That's how I initially<br>> heard of the<br>> project. Then it kind of moved back under my radar again until<br>> Summer of Code.<br>> When I saw Drupal on the list of projects, I immediately wanted to
<br>> get involved<br>> with something that was allowing a grassroots activism movement to<br>> work so well.<br>> And now I've had the opportunity to actually dig into Drupal's<br>> "guts" a bit. :)
<br>><br>> *So how did that opportunity actually come about?*<br>><br>> One of my instructors from my college found out about the<br>> opportunity and<br>> e-mailed myself and a few other students from my class. Getting
<br>> involved in an<br>> open source development project is something that's been on my<br>> "life goals"<br>> list for quite a few years, so when I saw the opportunity, I jumped<br>> on it. I<br>
> was especially excited about helping with Drupal, both because a)<br>> it was being<br>> used as a tool in activism, so I feel like a contribution there is<br>> helping make<br>> the world a better place (very important to me), and b) the
<br>> particular project I<br>> took on (quiz module) was to help further Drupal's ability to be<br>> used within<br>> education, another extremely important issue to me.<br>><br>> *I understand you did some work on the forms API, would you care to
<br>> comment on<br>> that?*<br>><br>> While I've not done work with the Forms API directly (Adrian is the<br>> guru there<br>> who allowed it to come to be), I have been trying to do a lot of<br>> work in making
<br>> the transition between 4.6 and 4.7 as easy for developers as<br>> possible, and a big<br>> part of that is the effort being put into the documentation for the<br>> new forms<br>> API.<br>><br>> *What kind of documentation improvements have you been working on?*
<br>><br>> The first effort has been to try and centralize a "resource center"<br>> for<br>> developers to go to to learn everything they need to know to<br>> convert their<br>> modules to the new API. You can find the result of that here:
<br>> <a href="http://drupal.org/node/33338" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/33338</a>. This area will include everything from<br>> step-by-step documentation to answers to frequently asked
<br>> questions, to tips<br>> that have been submitted by other developers to aid people in their
<br>> form<br>> conversions.<br>><br>> The second area is the Forms API reference, available here:<br>> <a href="http://drupaldocs.org/api/head/file/contributions/docs/developer/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupaldocs.org/api/head/file/contributions/docs/developer/
</a><br>> topics/forms_api_reference.html<br>> which is a comprehensive listing of *all* form elements and<br>> attributes, along<br>> with descriptions about what they do, where they can/should be<br>> used, and "real
<br>> world" examples from Drupal core on how they're used.<br>><br>> The final piece of this will be a complete step-by-step run-through<br>> of how the<br>> Project module was converted (this module is particularly good for
<br>> this because<br>> there is just about *everything* a module developer will run into),<br>> as well as<br>> documentation of the new hooks provided by the Forms API and that<br>> sort of<br>> thing. I'm working closely with Chad (hunmonk) on these, and Kieran of
<br>> CivicSpaceLabs has a huge hand in helping fund their development.<br>><br>> *Great! So what do you do when not working on Drupal?*<br>><br>> Sleeping and eating. Every other waking moment is taken up by
<br>> Drupal. ;) No,<br>> actually, I also do volunteer work with a few other online<br>> communities. One of<br>> these is CyberArmy.net, which is a community of primarily young people<br>> interested in open source, privacy, computer security/"hacking" and
<br>> so forth<br>> and we try and hook them up with constructive opportunities to help<br>> out the<br>> Internet as a whole. I also enjoy playing video games, drawing/<br>> sketching, and<br>> doing logic puzzles and the like (yes, I'm a big nerd ;)).
<br>><br>> *Any final comments for our readers?*<br>><br>> Only that I'd like to sincerely thank everyone in the Drupal<br>> community for<br>> really welcoming me here and making me feel like "one of the guys."
<br>> I didn't<br>> have a lot of confidence initially when I first started with this<br>> project,<br>> since I was just kind of some mostly self-taught random girl coming<br>> from a<br>> community college. But everyone has been so supportive and
<br>> encouraging to me,<br>> receptive to my input a nd feedback, and constantly throwing new<br>> opportunities<br>> my way. I've met so many friends and learned so many things since<br>> first coming<br>
> here, that this experience has been literally life-changing. Thank<br>> you!<br>><br>> ------------VIEWS MODULE EXTEND'S DRUPAL FLEXIBILITY------------<br>><br>> Anybody who's spent any time cruising Drupal's forums knows that
<br>> one of the<br>> most commonly asked questions is something along the lines of "How<br>> do I display<br>> a list of nodes of a certain type on a page sorted by author and<br>> then by date?"
<br>> The answer used to be "dust off your favorite PHP and MySQL<br>> reference works and<br>> get cracking."<br>><br>> But a new module, developed by Earl Miles (a.k.a. merlinofchaos),<br>> promises to
<br>> make customized displays of content much more attainable for the<br>> average user<br>> and save bundles of time for even the most experienced Drupal<br>> developer. It's<br>> called "views" and can be downloaded from
<a href="http://drupal.org/node/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/</a><br>> 38878.<br>><br>> The views module is feature packed, providing a whole host of
<br>> options that<br>> allow site administrators to pull content from the database and
<br>> display it in<br>> just about every conceivably useful way, all without knowing one<br>> line of PHP.<br>> Want your content paged so only 5 entries show up on a page at a<br>> time? No<br>> problem. Sorted by one, two, or more fields? Of course! Listed
<br>> in a table?<br>> Yup, can do that, too. How about output to a block? Easy as pie.<br>> Can you<br>> filter output based on arguments supplied by the url? Yes, sir!<br>><br>> And amazingly, all of this flexibility, and much more, is provided
<br>> by simply<br>> selecting options on one single web-based form. And, yes, the web<br>> form can be<br>> a little intimidating, especially for newer Drupal users. But no<br>> worry here<br>> either. Views has an export/import feature that lets you share
<br>> views with<br>> other users. If the views module takes off, and I think it will,<br>> there will<br>> soon be an entire library of views at the Drupal site which can be<br>> imported in<br>> a matter of seconds with a cut, a paste, and a click.
<br>><br>> If all that doesn't impress you, Earl has also thrown in some<br>> additional<br>> features to win over the hearts and minds of Drupal developers and<br>> designers.<br>> For example, views has its own API so that other modules can let
<br>> views do the<br>> work of displaying output. This will save developers time when<br>> creating<br>> sophisticated modules needing to output data in many different<br>> ways. And views<br>> can even be themed so that designers can give them their own
<br>> distinctive look.<br>><br>> Just as the flexinode module created flexible ways for<br>> administrators to input<br>> data into nodes, views promises to do the same for node output.<br>> There's little
<br>> doubt in my mind views will become a staple of many Drupal<br>> installations. The<br>> module is still in beta and needs testers to find any bugs and help<br>> improve<br>> usability. If interested, just download the module at
<br>> <a href="http://drupal.org/node/38878" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/38878</a> and report your findings at<br>> <a href="http://drupal.org/project/issues/views" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/project/issues/views</a>. Be one of the first to
<br>> check it out<br>> this amazing piece of code!<br>><br>> ------------DRUPAL DEVELOPMENT QUICKIES------------<br>><br>> * DriesK separated introduced 'administer access control'<br>> permission which is
<br>> now separate from 'administer users'. (Patch #32669<br>> [<a href="http://drupal.org/node/32669" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/32669</a>])<br>>
<br>> * kbahey added 'site offline/maintenance' feature. (Patch #32622
<br>> [<a href="http://drupal.org/node/32622" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/32622</a>])<br>><br>> * Countless bugfixes against form API. Most of them by asimmonds,
<br>> chx and<br>> hunmnonk.<br>><br>> * Steven made huge improvements to Drupal's search feature.
<br>> Indexing has<br>> been made smarter and more robust and several advanced search<br>> operators (e.g.<br>> phrase, node type, ...) have been added. The result rankings are now<br>> customizable. (Patch #28159 [
<a href="http://drupal.org/node/28159" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/28159</a>])<br>><br>> * Steven introduced a user-friendly error screen for users with
<br>> unsupported<br>> database software.<br>><br>> * Stefan increased a designer's ability to theme Drupal. Chief
<br>> among these<br>> improvements is the ability to theme poll results.<br>><br>> * ax made blogapi autodiscovery (rsd) work with the Flock browser<br>> (and any<br>> other standards-chasing RSD using client). This lets you post to
<br>> your blog<br>> without even visiting your site. (Patch #34749 [<a href="http://drupal.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/</a><br>> node/34749])<br>
><br>> * m3avrck and deekayen cured an immense number of PHP5 warnings.
<br>> (Patch<br>> #30930 [<a href="http://drupal.org/node/30930" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/30930</a>])<br>><br>> * the documentation team, Kieran and webchick introduced much
<br>> improved admin<br>> help in core modules. This is the "mega patch" season... (Patch #26139
<br>> [<a href="http://drupal.org/node/26139" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/26139</a>])<br>><br>> * Richard Archer integrated primary links into the menu system.
<br>> This was much<br>> needed. (Patch #22215 [<a href="http://drupal.org/node/22215" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/22215</a>])<br>><br>> * Morbus improved handling of temporary files/directory. (Patch<br>> #26249<br>> [<a href="http://drupal.org/node/26249" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/26249</a>])<br>>
<br>> * Cvbge did an awesome job to make pgsql and Drupal work better<br>> together. Too<br>> many patches to list.<br>><br>> * Robert added permission to enable/disbale theme switching by<br>> users. (Patch
<br>> #38981 [<a href="http://drupal.org/node/38981" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/38981</a>])<br>><br>> * saerdna et al. added a 'change own username' permission. (Patch
<br>> #39547<br>> [<a href="http://drupal.org/node/39547" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/39547</a>])<br>><br>> * One of those rare moments when two maintainers work on one<br>> patch: JonBob<br>> and Richard separated callback handling from menu handling. (Patch<br>> #35768
<br>> [<a href="http://drupal.org/node/35768" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/35768</a>])<br>><br>> * Morbus optimized performance of URL aliasing for newly
<br>> installed sites.<br>> (Patch #29326 [<a href="http://drupal.org/node/29326" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/29326</a>])<br>><br>> * drumm introduced the first piece of an install: an SQL updater<br>> you can hook<br>> into. (Patch #35924 [<a href="http://drupal.org/node/35924" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/35924
</a>])<br>><br>> * Though we rarely mention fixes here, big kudos to Morbus,<br>> webchick and<br>> tangent for fixing the order of node(api) form fields. (Patch #34920<br>> [<a href="http://drupal.org/node/34920" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/34920</a>])<br>><br>> * chx broke the record of 'added code' per 'comment needed for<br>> the code'<br>> ratio with #40886 [<a href="http://drupal.org/node/40886" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/40886
</a>]. Reference<br>> counting is tricky.<br>> Thanks goes to Goba.<br>><br>> * Richard and chx made it possible to link to the front page.<br>> (Patch #36465<br>> [<a href="http://drupal.org/node/36465" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/36465</a>])<br>><br>> * Steven introduced some javascript to make textareas in forms<br>> resizeable<br>> (Patch #42446 [<a href="http://drupal.org/node/42446" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/42446
</a>])<br>><br>> * Richard and Steven made it possible to use external URLs in<br>> menus (and made<br>> url() more flexible). Extra Druplipoints to them for this. (Patch<br>> #32785<br>> [<a href="http://drupal.org/node/32785" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/node/32785</a>])<br>><br>> Karoly Negyesi,<br>> <a href="http://drupal4hu.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal4hu.com/</a><br>><br>> -------------SECURITY UPDATES-------------
<br>> Get the latest security updates
<br>> right in your inbox! Subscribe to the<br>> Security Announcements mailing list today!<br>> <a href="http://drupal.org/security" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/security</a><br>> ------------------------------------------
<br>><br>> ------------DRUPAL TIPS------------<br>><br>> Editor: Should put in a couple more tips. And ones that are of<br>> interest to<br>> admins, not just developers (unless we want just developer tips).
<br>><br>> *Track activity and changes on your favorite projects with RSS*<br>> (Contributed by<br>> Bèr Kessels)<br>> The CVS log is often underrated as a means of tracking what happens to<br>> your favorite project.
<br>><br>> Let us take as an example the project named "shazamgallery": Visit<br>> the link<br>> <a href="http://drupal.org/cvs?file=/modules/shazamgallery/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/cvs?file=/modules/shazamgallery/
</a> to see the<br>> latest commits to<br>> that project. The /modules/shazamgallery/ in the url can be<br>> replaced by<br>> anyhting of your interest. You can even track changes to one file.<br>> For<br>
> example, <a href="http://drupal.org/cvs?file=/modules/shazamgallery/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/cvs?file=/modules/shazamgallery/</a><br>> shazamgallery.mysql
<br>> lets you track changes to the database file only.<br>>
<br>> The most interesting part, however, is the RSS feed that comes with<br>> that<br>> at <a href="http://drupal.org/cvs?rss=true&file=/modules/shazamgallery/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/cvs?rss=true&file=/modules/shazamgallery/
</a><br>><br>> Use this to track your own contribs (to see if some other contributor<br>> slips in features, or bugs, by accident). Or to track changes of the<br>> projects you use on your drupal site.<br>>
<br>> ------------USER GEARED CONTENT. PLEASE WRITE,<br>> VOLUNTEERS?------------<br>><br>> Talk about how artists on a tight budget can build powerful web<br>> sites to help<br>> them spread the word about their art. Do they have podcasts/sample
<br>> work.<br>> Might be interesting to mention.<br>><br>> ------------COMING UP IN DRUPAL 4.7------------<br>><br>> Editor's note: Seems like we're missing some other major changes like<br>> forms.api
. Specifically, what's the big deal about forms api?<br>><br>> (doc team, thoughts? --Robin)<br>><br>> One of the most obvious changes involves the Menu module. No<br>> longer will the<br>> primary and secondary links be a custom template configuration
<br>> issue. The<br>> control of these links has been moved into the menu module. After<br>> turning on<br>> menu module, you can go into *administer >> settings >> menu*<br>> ?q=admin/settings/menu You will find a new option Primary links
<br>> settings. If<br>> you do not have separate menu's yet, you will need to create them<br>> and then<br>> designate them here. This will involve some minor code changes to<br>> any custom<br>> templates you have and you can see examples in the included Blue
<br>> Marine theme.<br>> You will also have the option to add items directly to the menu<br>> when you first<br>> create them.<br>><br>> In the aggregator module, the 'Allowed HTML tags' control has been
<br>> exposed<br>> through the GUI so that you can edit for what html tags you will<br>> allow for in<br>> the rss feeds you pull from other sites. As an example, by default<br>> the tag is<br>> not allowed, but now you can change this through the *administer >>
<br>> settings >><br>> aggregator* settings instead of in the code itself.<br>><br>> The configuration for your node type workflow (published, promoted<br>> to front<br>> page, etc) has been moved from it's semi-obscure location in
<br>> content >><br>> configure to a more sensible and consistent *administer >> settings<br>> >> content<br>> types*. This will help new neophytes and experienced admins all<br>> around.
<br>><br>> Some new settings have been added to the user module in access control<br>> *administer >> access control*. Added permissions are 'administer<br>> access<br>> control' and 'change own user name'.
<br>><br>> While it is exciting that blocks are now able to go into a number<br>> of different<br>> regions (left/right sidebar, header, content, footer) now, that is<br>> nothing<br>> compared to additional controls added to block configuration
<br>> settings. You now<br>> have an experts mode option to control visibility based on php code<br>> added to the<br>> block configuration<br>> as well as some radio button options to control site wide user
<br>> visibility<br>> settings.<br>><br>> The help files have had a serious going over and many now include<br>> links back to<br>> the <a href="http://Drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Drupal.org</a> site so that you can take advantage of new and updated
<br>> information from links right in your own installation.<br>><br>> Contributed by,<br>> Steven Peck<br>><br>> /For more information about Drupal, visit our website at http://<br>> <a href="http://drupal.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
drupal.org/</a>.<br>><br>> Content donations can be sent to the editor using the form at<br>> <a href="http://drupal.org/contact" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/contact
</a> .<br>><br>> This work is licensed under the Creative Commons
<br>> Attribution-NonCommercial-ShareAlike License. To view a copy of<br>> this license,<br>> visit <a href="http://creativecommons.org/licenses/by-nc-sa/2.5/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://creativecommons.org/licenses/by-nc-sa/2.5/</a>
. /<br>><br>><br>><br>> --<br>> Footer will be appended here<br>> --<br>> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://drupal.org/project/issues/documentation/</a><br>
> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.drupal.org/pipermail/documentation/</a><br>> _______________________________________________
<br>> droppies mailing list<br>
> <a href="mailto:droppies@drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">droppies@drupal.org</a><br>> <a href="http://lists.drupal.org/listinfo/droppies" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.drupal.org/listinfo/droppies</a><br><br><br>--<br>Dries Buytaert :: <a href="http://www.buytaert.net/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.buytaert.net/</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Robin Monks,<br>CSL Web Administrator<br><a href="mailto:robin@civicspacelabs.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
robin@civicspacelabs.org</a><br><br>( <a href="http://gmking.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://gmking.org</a>, a gamers dream )