Idan, all:<div><br></div><div>In Drupal there are a gazillion ways to do things...</div><div><br></div><div>Managing taxonomy is more complex than the UI that I'm talking about providing. But let's say there is a site that uses taxonomy in rich complicated ways, a bunch of vocabularies, etc... most of which content admins don't fuss with. There is only one "administer taxonomy" permission. I may only want to give editors access to one vocab in that case. And I also have to explain things like "Term" and "Vocabulary" etc... This module would be about providing a very lightweight alternative to a specific task. It's certainly not for everyone, for every site, or for every select-list solution.</div>
<div><br></div><div>Shai<br><br><div class="gmail_quote">On Thu, Jan 28, 2010 at 8:09 AM, Idan Arbel <span dir="ltr"><<a href="mailto:idan@arbel-designs.com">idan@arbel-designs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">How about using taxonomy for select lists?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Idan</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:development-bounces@drupal.org" target="_blank">development-bounces@drupal.org</a> [mailto:<a href="mailto:development-bounces@drupal.org" target="_blank">development-bounces@drupal.org</a>] <b>On
Behalf Of </b>Shai Gluskin<br>
<b>Sent:</b> Thursday, January 28, 2010 3:04 PM<br>
<b>To:</b> <a href="mailto:development@drupal.org" target="_blank">development@drupal.org</a><br>
<b>Subject:</b> [development] Module Idea for Feedback: Select Option Values</span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">Development Peeps,</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I'm thinking of a module called: Select Option Values</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">It would pull out part of CCK's text.module functionality
from admin/content/node-type/<type machine
name>/fields/field_<field name> and put it on its own admin page with
it's own permission. The problem with the location of the setting, as it is
now, is that you have to have "administer content-type" permissions
in order to get there and that is something rarely given to a client, at least
in my experience.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">But the allowed values maintenance for a select list is
something I <i>want</i> to give over to client content-editors/admins.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">My current workaround is that I designate the body field of
a particular unpublished node for that purpose and provide a link to it in a
the custom admin area I typically build for site editors.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I put the following code in the "<span><span style="font-size:9.0pt">Advanced
usage only: PHP code that returns a keyed array of allowed values.</span></span><span><span>":</span></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">$node
= node_load(17); // Replace "17" with node id of node containing
options.</span><span style="font-size:10.0pt"></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">$body
= strip_tags(str_replace("\r\n","~",trim($node->body)));</span><span style="font-size:10.0pt"></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">$arr
= explode("~",$body);</span><span style="font-size:10.0pt"></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black">return drupal_map_assoc($arr);</span><span style="font-size:10.0pt;color:#500050"></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>That
work-around is okay, but it does feel like a work-around better solved by a
module.</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>Does
this exist and I didn't find it? Is it needed in your estimation?</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>Shai</span></span></p>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>