<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Thnx Mac</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=maciej.perlinski@gmail.com
href="mailto:maciej.perlinski@gmail.com">Maciej Perlinski</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=development@drupal.org
href="mailto:development@drupal.org">development@drupal.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, March 06, 2008 5:27
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [development] Urgent
Help</DIV>
<DIV><BR></DIV>check theming dr6 handbook how to define new
region...<BR><BR>Mac<BR><BR>
<DIV class=gmail_quote>On Thu, Mar 6, 2008 at 10:56 AM, Surya Namala <<A
href="mailto:surya.namala@valuelabs.net">surya.namala@valuelabs.net</A>>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Hi,<BR>Any
body help me out on below issue.<BR>I have successfully installed Drupal 6.1
in my local environment but I am<BR>not able to create own regions.Please
help me out.<BR><BR>Regards,<BR>Surya<BR><BR>----- Original Message
-----<BR>From: "Steven Jones" <<A
href="mailto:darthsteven@gmail.com">darthsteven@gmail.com</A>><BR>To:
<<A
href="mailto:development@drupal.org">development@drupal.org</A>><BR>Sent:
Thursday, March 06, 2008 3:12 PM<BR>Subject: Re: [development] New
functionality on project nodes installed<BR>ond.o<BR><BR><BR>> Wow,
that's very fab.<BR>><BR>> Just a minor nitpick: The images on the RHS
of the table for dev<BR>> snapshots have an alt and title attribute of
'error', but there isn't<BR>> any error going on. Maybe a text like:'
Snapshots are for development<BR>> only, NOT for production servers' or
somesuch.<BR>><BR>> Otherwise great work.<BR>><BR>> On
06/03/2008, Derek Wright <<A
href="mailto:drupal@dwwright.net">drupal@dwwright.net</A>>
wrote:<BR>>> If you own any project nodes on d.o please read
this...<BR>>><BR>>> I just finished up a patch[1] that was
holding up a string of<BR>>> improvements to project nodes.
The most important new functionality<BR>>> is that you now
have more fine grained control over what releases are<BR>>>
displayed on your project nodes[2].<BR>>><BR>>>
First of all, for each version of core, you now have
separate<BR>>> controls for every major version, where you can
specify if that core/<BR>>> major combination is supported, and
if you want a dev snapshot<BR>>> displayed for it or not.
Then, if you've got multiple major versions<BR>>> for the
same version of core, you get a radio to select which version<BR>>>
is recommended.<BR>>><BR>>> Update status (both in
D6 core and D5 contrib) already knows about<BR>>> all of this,
it just hasn't been visible on d.o yet. So, previously,<BR>>>
when you changed the "recommended version", update status
would<BR>>> immediately warn users they should upgrade, which
caused much<BR>>> confusion and hassle. Now, update status
will only warn users to<BR>>> upgrade once you uncheck the
"supported" checkbox. So, you can have<BR>>> both 5.x-2.*
and 5.x-1.* supported, and 5.x-2.* recommended, and<BR>>> update
status won't bother people still running 5.x-1.*. However,<BR>>>
say you ship a 5.x-3.*, and decide to drop support for 5.x-1.*,
you<BR>>> can uncheck the box and update status will tell them
to upgrade.<BR>>><BR>>> Now, all it means when you mark a
given major version "recommended"<BR>>> is a) it's displayed as
such on the project nodes, b) update status<BR>>> says so in its
status report, and c) it's the version that'll be<BR>>> shown in
the project teaser in the project browsing pages.<BR>>><BR>>>
Furthermore, recommended releases are now colored green on
the<BR>>> project nodes and project browsing pages, whereas -dev
snapshots are<BR>>> always marked as red (to warn people not to
download them for real<BR>>> sites).<BR>>><BR>>>
I also fixed a caching bug where sometimes the release tables
would<BR>>> have "edit" links in them which most users would get
permission<BR>>> denied on, while other tables wouldn't have
edit links for users who<BR>>> could use
them.<BR>>><BR>>> Finally, I fixed a wonky bug that would
require visiting and saving<BR>>> the "releases" subtab of the
edit tab on your project node whenever<BR>>> you added a new
release for a whole new version of core.<BR>>><BR>>>
Enjoy,<BR>>> -Derek (dww)<BR>>><BR>>>
p.s. Thanks to Tao (starbow) for some of the cool jQuery goodness
on<BR>>> that new edit/releases UI.<BR>>><BR>>>
p.p.s. Thanks to Chad (hunmonk) and Adam (aclight) for reviewing
and<BR>>> testing this stuff.<BR>>><BR>>> [1]
<A href="http://drupal.org/node/176776"
target=_blank>http://drupal.org/node/176776</A><BR>>> [2] <A
href="http://drupal.org/node/203313"
target=_blank>http://drupal.org/node/203313</A><BR>>><BR>>><BR>>><BR>>><BR>><BR>><BR>>
--<BR>> Regards<BR>> Steven
Jones<BR>><BR><BR></BLOCKQUOTE></DIV><BR><BR clear=all><BR>--
<BR>-<BR>kindest regards<BR>Maciej Perlinski<BR><A
href="mailto:maciej.perlinski@meant4.com">maciej.perlinski@meant4.com</A><BR><A
href="http://www.meant4.com">http://www.meant4.com</A><BR></BLOCKQUOTE></BODY></HTML>