[support] Registration module question...
Steve Kessler
skessler at denverdataman.com
Mon Dec 9 20:12:45 UTC 2013
Make sure you are setting the permissions for *each* of your registration
entity types. If you let people register for others in the configuration
make sure this permission is set as well. In this same manner by not
allowing the register other permission this will suppress the registration
for others.
I think this will get you to a next strong milestone.
On Mon, Dec 9, 2013 at 8:07 AM, <Philip_Wetzel at nhd.uscourts.gov> wrote:
> My implementation of Entity Registration is coming along, but I have a few
> deal breaker
> issues, that I don't know how to fix yet. I haven't had to write any PHP
> code (or modify
> theme) at this point, but I think I'm going to have to in order to achieve
> the behavior I
> need.
>
> "Modify the theme" is still a hurdle I haven't cleared yet. I believe
> it involves writing
> hooks, which is a new concept for me. I think when you see an example of
> a hook,
> you will see it in the form "hook_SomeFunction". When you write the hook
> for your implementation
> you replace the word hook with the name of your theme. SomeFunction is a
> function that
> does already exist, and you are overriding it. Is that all correct?
>
> Here are the specific tasks I need to accomplish.....
>
>
> · David's suggestion on how to create the "Click to Register" Link
> works great, except I still
> get all 4 tabs (view, edit, manage registrations, register). I just
> need the register form with no
> other tabs.
>
> · Need to allow users to register when not logged in. Out of the
> box,
> you get 403 :Access denied.
>
> · When I do manage to get around this, I will also need to suppress
> the
> dropdown
> after "This registration is for" (Myself, other account, other
> person). And the email box needs to
> be required. Also, that email must be the one used when sending an
> email to all registrants.
>
> · When creating an event, there is a required comment field. I think
> this is not a deal breaker,
> but I would like to get rid of it. It's not part of the
> registration type or content types I'm using.
> Where is this?
>
> · Wait list is not working. Nothing seems to happen when capacity
> is
> exceeded . I remember
> seeing discussion activity on this somewhere.
>
>
> That's my list. I imagine these issues would be relatively easy for a
> seasoned Drupal
> developer. I think/hope they are not out of my capabilities, but I expect
> will be some what
> challenging. I appreciate any and all help.
> Thanks in advance,
> Phil
>
>
>
>
>
>
>
>
> From: Philip_Wetzel at nhd.uscourts.gov
> To: support at drupal.org,
> Date: 12/05/2013 12:41 PM
> Subject: Re: [support] Registration module question...
> Sent by: support-bounces at drupal.org
>
>
>
> Hi David,
> Ah yes, That makes sense to me! And low and behold the Nid is an
> available field.
> You're right node/[nid]/register is what I want.
>
> I had started writing PHP that does a db_query for all nodes of a certain
> type...
> Essentially, a home grown view. That way, I would have the NID at my
> disposal.
> I think I'll table that and try your way.
>
> It was a great feeling when views started making sense to me. This could
> be better!
> I'm trying hard to expand my Drupal horizons while I can. I'm a long
> time .Net coder
> that fell into this Drupal opportunity 6 months ago. I certainly have more
> than I would
> if I had done this writing .Net code 6 months ago. Plus, it'll be
> maintainable by non-coders
> long after I have left.
>
> I'm trying to visualize how I would take this functionality and package it
> up into a module.
> Feel free to have fun if I'm way off here. Create a .info and .module
> file. In the .module
> I would want to write a hook into views that would create my custom view?
> It's reasonable to say module writers are PHP coders?
>
> Thanks a bunch,
> Phil
>
>
>
>
>
> From: "Metzler, David" <metzlerd at evergreen.edu>
> To: "'support at drupal.org'" <support at drupal.org>,
> Date: 12/05/2013 11:43 AM
> Subject: Re: [support] Registration module question...
> Sent by: support-bounces at drupal.org
>
>
>
> I just got done doing something similar where I was creating a "contest"
> node type with associated "entry" nodes. I used entityreference and
> entityreference_prepopulate to allow me to create relationships between two
> nodes, and again I was left with trying to figure out how to generate a
> link for the user to create this content associated with the correct node.
>
>
> The basic strategy for generating the link was as follows
>
> First create a "view" that shows a single node with fields (or a list),
> with whichever of them you'd like to show. Next add the nid as a field to
> the view. This field will eventually become your link. In the
> configuration of the nid field choose "Rewrite Results". Check the
> "Rewrite the output of this field" options and type in the text you want
> this link to appear as. Check the "Output this field as a link" option
> specify the link path that you'd like to see. In your case it's probably
> node/[nid]/register , but in my case I was building
> node/add/entry?field_contest=[nid] and entityprepopulate took care of
> defaulting in the referenced entity and hiding the field for the user.
>
> This magic is basically how Organic Groups works these days which is where
> I found the information.
>
> Hope that strategy helps you.
>
> -----Original Message-----
> From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
> Behalf Of Philip_Wetzel at nhd.uscourts.gov
> Sent: Thursday, December 05, 2013 7:39 AM
> To: support at drupal.org
> Subject: Re: [support] Registration module question...
>
> Hi Steve,
> Thanks so much for taking the time to help me through this. I will do my
> best to return the effort somehow.
>
> I wiped everything out and started over. Followed your steps. I've pretty
> much been this far before. Now, when I view the node (logged in as admin)
> I see the event content with 4 tabs.
> This is fine for the person that is going to administer the event. They
> can view/edit the event, see who
> is registered, register someone, etc. I've created a view to better refine
> that.
>
> Now, comes my problem. I think I know some of the steps, but can't quite
> get it all the way yet.
> I want to have anyone off the street be able to go to our site, get a list
> of all the events.
> No problem there, create a view.
>
> Each event will have a link to the registration form and will allow them to
> register.
> This is pretty much where I fall on my face every time.
> If I go to the event I created in this case and clicked on the register
> tab, the URL
> would be localhost/node/467/register. I could easily hard code a link and
> do
> it manually. Of course, that is no good.
>
> I can almost see how to do this with PHP, but I imagine there's a way to do
> this without.
> I find it hard to believe that this wheel doesn't already exist.
> You certainly don't want your registrants to see the "manage Registrations"
> tab.
> But, out of the box this is the only way I see to do it.
>
> As I said, the Toronto Web Developer guy does exactly that, (with Node
> References).
> I've been through his video dozens of times, and I always end up close but
> no cigar.
> As I said, he's on Drupal 7, but I think the video was recorded prior to
> the release of the Registrations module. Actually, I just checked on that
> a little. The video was uploaded
> May 15, 2011. Looks like Entity Registration's first dev release was
> released 4 months later.
>
> At the very least, writing up my little dilemma helps me think it through.
> I think a PHP solution
> is starting to materialize in my mind. If I was smart I would take this
> opportunity to figure out
> modules, and hooks, and what not. I saw the Simplest module example and
> understand it.
> OK, I need to stop finger babbling and get my brain in gear.
>
> Thanks,
> Phil
>
>
>
>
>
> From: Steve Kessler <
> skessler at denverdataman.com>
> To: "support at drupal.org" <support at drupal.org
> >,
> Date: 12/04/2013 03:21 PM
> Subject: Re: [support] Registration module
> question...
> Sent by: support-bounces at drupal.org
>
>
>
> Here is what I do.
>
> 1. Create registration type
> 2. Create a content type with a registration field.
> 3. Create a node of the new content field that selects the registration
> type that I created.
>
> This has worked very well for me.
>
>
> On Wed, Dec 4, 2013 at 6:58 AM, <Philip_Wetzel at nhd.uscourts.gov> wrote:
> Thanks Steve,
> It helps, but it's a bit beyond my current level of Drupal expertise. I
> think I'm
> so close I can taste it. I think I have everything I need (modules or
> coding) and it's just a matter
> of setup.
>
> Yaworski of Toronto Website Developer is doing exactly what I want to do,
> but I think the combination
> of modules he is using is just prior to when all of this was integrated
> into one module (Registrations).
> Specifically, he sets up the "Click to Register" feature right about 2:40
> in the youtube video below.
>
> http://www.youtube.com/watch?v=0CHC8I9xZIg
>
> He uses node references. I go through the steps, but I don't end up with
> a
> link to my registration page.
> I don't end up with a link at all.
> I think the answer is staring me in the face, but I just can't see the
> trees through the forest.
> Phil
>
>
>
> From: Steve Kessler <skessler at denverdataman.com>
> To: "support at drupal.org" <support at drupal.org>,
> Date: 12/03/2013 12:06 PM
> Subject: Re: [support] Registration module question...
> Sent by: support-bounces at drupal.org
>
>
>
> You have a few of choices.
>
> You can make a view and use replacement tokens. Using the Views module
> you could for example display your listings on a calendar or in a table.
>
> If you want people to view the specific node then you could edit your
> theme
> template file to but a button on the node itself. I think you could also
> do this maybe even without code using the Display Suite Module (
> https://drupal.org/project/ds).
>
> In terms of taking out the tab that would also require changes to your
> theme.
>
> Hope this helps.
>
> -Steve
>
>
> On Tue, Dec 3, 2013 at 9:34 AM, <Philip_Wetzel at nhd.uscourts.gov> wrote:
> I'm using the registration module to create scheduled events.
> I have a view that shows the events.
> I would like to add a button or a link that would bring up the
> registration
> form for that event.
>
> I have the title setup as a link to the original piece of content. If
> I
> click on it, I get the
> tabs (View, Edit, Manage Registrations, Register. I want my button
> to
> go
> strait to that
> node.
>
> For instance, the node for the event is node/457. I click on
> the
> register tab and I
> get node/457/register.
>
> How can I create a button that would take me strait to
> node/457/register?
> Also, I would need it to not show the other 3 tabs. I don't want the
> people registering for the
> event to be able to have those functions available.
>
> Is that enough information?
> Thanks,
> Phil Wetzel
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
> --
> Steve Kessler
> Owner and Lead Consultant
> Denver DataMan, LLC
> 303-587-4428--
> [ Drupal support list | http://lists.drupal.org/ ]
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
> --
> Steve Kessler
> Owner and Lead Consultant
> Denver DataMan, LLC
> 303-587-4428--
> [ Drupal support list | http://lists.drupal.org/ ]
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
--
Steve Kessler
Owner and Lead Consultant
Denver DataMan, LLC
303-587-4428
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20131209/7531b2eb/attachment-0001.html
More information about the support
mailing list