Ben,<div><br></div><div>Are you sure your case statement is correct?</div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">You have:</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "> switch ($form_id) {<br> case 'user_login':<br> case 'user_login_block':<br>
// If the user login form is being submitted, add our validation</span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">...</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">PDD:</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">if ($form_id == 'user_login' || $form_id == 'user_login_block')</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">...</span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br>
</span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">emphasis being placed on the || (or)</span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br>
</span></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div></ryan><br>
<br><br><div class="gmail_quote">On Wed, May 19, 2010 at 9:29 PM, Ryan LeTulle <span dir="ltr"><<a href="mailto:bayousoft@gmail.com">bayousoft@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
nm I see it in ch 6 now<div><br clear="all"><font color="#888888"></ryan></font><div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Wed, May 19, 2010 at 9:27 PM, Ryan LeTulle <span dir="ltr"><<a href="mailto:bayousoft@gmail.com" target="_blank">bayousoft@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Ben, which Pro Drupal Edition are you referring to?<div><br clear="all"><font color="#888888"></ryan></font><div><div></div><div><br>
<br><br><div class="gmail_quote">On Wed, May 19, 2010 at 9:18 PM, Ben DJ <span dir="ltr"><<a href="mailto:bendj095124367913213465@gmail.com" target="_blank">bendj095124367913213465@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anth,<br>
<div><br>
> I feel your pain here. I just went through something similar to have a<br>
> timesheet application up and going. One content type representing a<br>
> timesheet but users with different roles accessing different versions/parts<br>
> of it at different stages of a workflow.<br>
><br>
> What I found a reasonably elegant solution and gave me a bit of re-use was<br>
> to set up different templates in the preprocess function (using template<br>
> suggestions) that will load the same content in a completely different way.<br>
> Using this with a multi form/step I got it all working without doing any<br>
> theme work or worrying how it looked and then added all my theme stuff<br>
> afterwards.<br>
<br>
</div>That's certainly an approach I've considered -- for 'new' form content.<br>
<br>
My "hurdle", atm, is (re)using the existing forms & modules<br>
(user_login, search, captcha, etc -- in my case) to the greatest<br>
extent possible.<br>
<br>
normally, i'd talk to the module designers about extending their<br>
modules -- but, so far, they're basically not interested. which is<br>
fine.<br>
<div><br>
> I do totally agree that this can feel harder than just writing<br>
> your own stuff from scratch sometimes though.<br>
<br>
</div>Tbh, I can get all this 'back end' controller workflow and logic, as<br>
well as site-wide theming, MUCH faster & easier using just about any<br>
PHP framework (Zend, Cake, Symphony), or even some of the newer CMS<br>
(apostrophe). A matter of days-to-weeks -- not this weeks to months<br>
business.<br>
<br>
I keep telling myself that the *eventual* payoff -- huge community and<br>
mgmt of the community/content -- will make itself known using Drupal.<br>
<br>
For quick up-n-running out-of-the-box stuff, Drupal really can't be<br>
beat. But for non-standard extension, although the inner workings are<br>
there, i'm finding it's not the 'friendliest' environments. Like I<br>
said earlier -- *maybe* a lighting bolt will hit. But, atm, I'm<br>
having a Margarita and re-considering the wisdom of my choice -- or<br>
lack thereof.<br>
<font color="#888888"><br>
Ben<br>
</font></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>