Send development mailing list submissions to
development@drupal.orgTo subscribe or unsubscribe via the World Wide Web, visit
http://lists.drupal.org/listinfo/developmentor, via email, send a message with subject or body 'help' to
development-request@drupal.orgYou can reach the person managing the list at
development-owner@drupal.orgWhen replying, please edit your Subject line so it is more specific
than "Re: Contents of development digest..."
Today's Topics:
1. RE : Creating separate registration forms for each role (fgm)
2. Re: Creating separate registration forms for each role
(rajasekharan)
3. Re: Creating separate registration forms for each role
(Ken Winters)
4. Modify environment before & after block is rendered
(Olivier Jacquet)
5. Re: Modify environment before & after block is rendered
(Daniel Honrade)
6. Re: Modify environment before & after block is rendered
(Olivier Jacquet)
7. Re: Modify environment before & after block is rendered
(Fred Jones)
8. Re: Creating separate registration forms for each role
(rajasekharan)
----------------------------------------------------------------------
Message: 1
Date: Tue, 8 Sep 2009 22:11:59 +0200
From: fgm <
fgm@osinet.fr>
Subject: [development] RE : Creating separate registration forms for
each role
To: "
development@drupal.org" <
development@drupal.org>
Message-ID:
<
AB5758215C066A4D8CE78D21A77DA1FC0981576C25@MBXVS01.hosting01.active24.com>
Content-Type: text/plain; charset="iso-8859-1"
A combination of auto-assign-role and content-profile-register does it. NikLP could tell you more...
________________________________________
De :
development-bounces@drupal.org [
development-bounces@drupal.org] de la part de Ken Winters [
kwinters@coalmarch.com]
Date d'envoi : mardi 8 septembre 2009
21:30
? :
development@drupal.orgObjet : Re: [development] Creating separate registration forms for each role
I believe he wants the actual form to be different.
We did something similar using the Profile module to create the fields
for all roles and then hook_user, hook_form, etc. to make sure that only
the right fields are displayed based on arg(2) (or whatever) and then
processed correctly.
- kwinters
Aradhana wrote:
> Hi,
>
> There is a drupal module names auto assign role.. which provides same
> functionality. We can differentiate forms on the basis of url. e.g
> assign different url for vendors registration and different url for
> customers.
>
>
http://drupal.org/project/autoassignrole>
> Regards,
> Aradhana
>
> rajasekharan wrote:
>> Hi,
>>
>> In a current project, I have to create a separate registration form
>> for each role. For example, "customers" has a registration form and
>> "vendors" have a registration form that is separate. Any idea how I
>> may achieve this using existing drupal modules?
>>
>> Thanks in advance,
>> Raj Sekharan
>>
>
------------------------------
Message: 2
Date: Wed, 09 Sep 2009 02:33:37 +0530
From: rajasekharan <
websweetweb@gmail.com>
Subject: Re: [development] Creating separate registration forms for
each role
To:
development@drupal.orgMessage-ID: <
4AA6C6A9.60603@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks much! I got what I wanted. I am going to use autoassignroles
module and then use the method Ken has mentioned - add profile
attributes and then use the necessary hooks to modify the form to show
the necessary fields.
Ken Winters wrote:
> I believe he wants the actual form to be different.
>
> We did something similar using the Profile module to create the fields
> for all roles and then hook_user, hook_form, etc. to make sure that
> only the right fields are displayed based on arg(2) (or whatever) and
> then processed correctly.
>
> - kwinters
>
> Aradhana wrote:
>>
Hi,
>>
>> There is a drupal module names auto assign role.. which provides same
>> functionality. We can differentiate forms on the basis of url. e.g
>> assign different url for vendors registration and different url for
>> customers.
>>
>>
http://drupal.org/project/autoassignrole>>
>> Regards,
>> Aradhana
>>
>> rajasekharan wrote:
>>> Hi,
>>>
>>> In a current project, I have to create a separate registration form
>>> for each role. For example, "customers" has a registration form and
>>> "vendors" have a registration form that is separate. Any idea how I
>>> may achieve this using existing drupal modules?
>>>
>>> Thanks in advance,
>>> Raj Sekharan
------------------------------
Message: 3
Date: Tue, 08 Sep 2009 17:26:05 -0400
From: Ken Winters <
kwinters@coalmarch.com>
Subject: Re: [development] Creating separate registration forms for
each role
To:
development@drupal.orgMessage-ID: <
4AA6CBED.1040707@coalmarch.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Great!
I just wanted to mention that the hooks method might not be required for
your particular needs.
Autoassignrole plus content_profile are pretty handy, but our specific
case had some elaborate requirements so we needed the hooks
anyway.
- kwinters
rajasekharan wrote:
> Thanks much! I got what I wanted. I am going to use autoassignroles
> module and then use the method Ken has mentioned - add profile
> attributes and then use the necessary hooks to modify the form to show
> the necessary fields.
>
> Ken Winters wrote:
>> I believe he wants the actual form to be different.
>>
>> We did something similar using the Profile module to create the
>> fields for all roles and then hook_user, hook_form, etc. to make sure
>> that only the right fields are displayed based on arg(2) (or
>> whatever) and then processed correctly.
>>
>> - kwinters
>>
>> Aradhana wrote:
>>> Hi,
>>>
>>> There is a drupal module names auto assign role.. which provides
>>> same functionality. We can differentiate forms on
the basis of url.
>>> e.g assign different url for vendors registration and different url
>>> for customers.
>>>
>>>
http://drupal.org/project/autoassignrole>>>
>>> Regards,
>>> Aradhana
>>>
>>> rajasekharan wrote:
>>>> Hi,
>>>>
>>>> In a current project, I have to create a separate registration form
>>>> for each role. For example, "customers" has a registration form and
>>>> "vendors" have a registration form that is separate. Any idea how I
>>>> may achieve this using existing drupal modules?
>>>>
>>>> Thanks in advance,
>>>> Raj Sekharan
>
------------------------------
Message: 4
Date: Wed, 09 Sep 2009
09:13:18 +0200
From: Olivier Jacquet <
ojacquet@jax.be>
Subject: [development] Modify environment before & after block is
rendered
To:
development@drupal.orgMessage-ID: <
4AA7558E.2080100@jax.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
When themename_preprocess_block() is called the content of the block is
already rendered. I am looking for a way to modify the environment
before the block is rendered and a way to restore the environment
afterwards.
The specific use case is that I have two blocks, generated by views, one
showing the terms from one taxonomy and the other the titles
of the
nodes belonging to that taxonomy.
When one navigates to a node the link to that node is active but I would
like the link to the taxonomy to be active as well. An easy way to
accomplish this would be to do a
menu_set_active_item('taxonomy/term/tid') before the taxonomy block is
rendered and reset it afterwards. Unfortunately this doesn't seem to be
possible.
The only other way I can think of is to modify the block content via
regular expressions in themename_preprocess_block().
Thank you for your time,
Olivier
------------------------------
Message: 5
Date: Wed, 9 Sep 2009 17:49:53 +0800
From: Daniel Honrade <
mail@danielhonrade.com>
Subject: Re: [development] Modify environment before & after block is
rendered
To:
development@drupal.orgMessage-ID:
<
db20d290909090249i3ef287b1x1ceb75f412a3ee4e@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
have you tried taxonomy menu module?
On Wed, Sep 9, 2009 at 3:13 PM, Olivier Jacquet <
ojacquet@jax.be> wrote:
> Hi,
>
>
> When themename_preprocess_block() is called the content of the block is
> already rendered. I am looking for a way to modify the environment before
> the block is rendered and a way to restore the environment afterwards.
>
> The specific use case is that I have two
blocks, generated by views, one
> showing the terms from one taxonomy and the other the titles of the nodes
> belonging to that taxonomy.
>
> When one navigates to a node the link to that node is active but I would
> like the link to the taxonomy to be active as well. An easy way to
> accomplish this would be to do a menu_set_active_item('taxonomy/term/tid')
> before the taxonomy block is rendered and reset it afterwards. Unfortunately
> this doesn't seem to be possible.
>
> The only other way I can think of is to modify the block content via
> regular expressions in themename_preprocess_block().
>
>
> Thank you for your time,
> Olivier
>
--
Daniel Honrade, Jr.
mobile: +63 915 903 3561
alternate email:
danielhonrade@gmail.comwebsites:
http://danielhonrade.com http://webtheming.comWhen you signup for PayPal, you can start accepting credit card payments
instantly. As the world's number one online payment service, PayPal is the
fastest way to open your doors to over 150 million member accounts
worldwide. Best of all, it's completely free to sign up! To sign up or learn
more, click here:
https://www.paypal.com/ph/mrb/pal=GE47NYP4D94XA-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.drupal.org/pipermail/development/attachments/20090909/383ee13f/attachment-0001.htm>
------------------------------
Message: 6
Date: Wed, 09 Sep 2009 12:03:37 +0200
From: Olivier Jacquet <
ojacquet@jax.be>
Subject: Re: [development] Modify environment before & after block is
rendered
To:
development@drupal.orgMessage-ID: <
4AA77D79.9020206@jax.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Yes, it doesn't do this at all. Other modules set the active item to the
taxonomy path which activates the link to the taxonomy page but then the
link
to the node is no longer active.
I want to activate two different links in two different blocks on one page.
Daniel Honrade wrote:
> have you tried taxonomy menu module?
>
> On Wed, Sep 9, 2009 at 3:13 PM, Olivier Jacquet <
ojacquet@jax.be> wrote:
>
>> Hi,
>>
>>
>> When themename_preprocess_block() is called the content of the block is
>> already rendered. I am looking for a way to modify the environment before
>> the block is rendered and a way to restore the environment afterwards.
>>
>> The specific use case is that I have two blocks, generated by views, one
>> showing the terms from one taxonomy and the other the titles of the nodes
>> belonging to that taxonomy.
>>
>> When one navigates to a node the link to that node
is active but I would
>> like the link to the taxonomy to be active as well. An easy way to
>> accomplish this would be to do a menu_set_active_item('taxonomy/term/tid')
>> before the taxonomy block is rendered and reset it afterwards. Unfortunately
>> this doesn't seem to be possible.
>>
>> The only other way I can think of is to modify the block content via
>> regular expressions in themename_preprocess_block().
>>
>>
>> Thank you for your time,
>> Olivier
>>
>
>
>
------------------------------
Message: 7
Date: Wed, 9 Sep 2009 13:59:16 +0300
From: Fred Jones <
fredthejonester@gmail.com>
Subject: Re: [development] Modify environment before & after block is
rendered
To:
development@drupal.orgMessage-ID:
<
177c0a10909090359y57d894d4kb35373cb0524154@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
> The specific use case is that I have two blocks, generated by views, one
> showing the terms from one taxonomy and the other the titles of the nodes
> belonging to that taxonomy.
To edit view content, use hook_views_pre_render
------------------------------
Message: 8
Date: Wed, 09 Sep 2009 22:08:02 +0530
From: rajasekharan <
websweetweb@gmail.com>
Subject: Re: [development] Creating
separate registration forms for
each role
To:
development@drupal.orgMessage-ID: <
4AA7D9EA.8060408@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I tried the content_profile method suggested by Ken Winters, for
creating a separate registration form with extra custom fields. I was
able to add fields to the registration form. But now I am faced with
another problem - even the default registration form shows the fields
that I have added for the suppliers' form. Is there anyway some of these
field can be restricted to the reg form for only certain roles? I am
using this in conjunction with the autoassignrole module.
Thanks in advance.
Raj
Ken Winters
wrote:
> Great!
> I just wanted to mention that the hooks method might not be required
> for your particular needs.
> Autoassignrole plus content_profile are pretty handy, but our specific
> case had some elaborate requirements so we needed the hooks anyway.
>
> - kwinters
>
> rajasekharan wrote:
>> Thanks much! I got what I wanted. I am going to use autoassignroles
>> module and then use the method Ken has mentioned - add profile
>> attributes and then use the necessary hooks to modify the form to
>> show the necessary fields.
>>
>> Ken Winters wrote:
>>> I believe he wants the actual form to be different.
>>>
>>> We did something similar using the Profile module to create the
>>> fields for all roles and then hook_user, hook_form, etc. to make
>>> sure that only the right fields
are displayed based on arg(2) (or
>>> whatever) and then processed correctly.
>>>
>>> - kwinters
>>>
>>> Aradhana wrote:
>>>> Hi,
>>>>
>>>> There is a drupal module names auto assign role.. which provides
>>>> same functionality. We can differentiate forms on the basis of url.
>>>> e.g assign different url for vendors registration and different url
>>>> for customers.
>>>>
>>>>
http://drupal.org/project/autoassignrole>>>>
>>>> Regards,
>>>> Aradhana
>>>>
>>>> rajasekharan wrote:
>>>>> Hi,
>>>>>
>>>>> In a current project, I have to create a separate registration
>>>>> form for each role. For example, "customers" has a registration
>>>>> form and "vendors" have a registration form that is separate. Any
>>>>> idea how I may achieve this using existing drupal modules?
>>>>>
>>>>> Thanks in advance,
>>>>> Raj Sekharan
------------------------------
--
[ Drupal development list |
http://lists.drupal.org/ ]
End of development Digest, Vol 81, Issue 7
******************************************