<p dir="ltr">Re the views part, views have an export function from the ui to create a view in code. Also look at the features module, it provides a ui to create modules from views, content types, panels and more (it's often used for deployment as well). Both use an existing default views hook.</p>
<div class="gmail_quote">On 5 Dec 2013 18:41, <<a href="mailto:Philip_Wetzel@nhd.uscourts.gov">Philip_Wetzel@nhd.uscourts.gov</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi David,<br>
Ah yes, That makes sense to me! And low and behold the Nid is an<br>
available field.<br>
You're right node/[nid]/register is what I want.<br>
<br>
I had started writing PHP that does a db_query for all nodes of a certain<br>
type...<br>
Essentially, a home grown view. That way, I would have the NID at my<br>
disposal.<br>
I think I'll table that and try your way.<br>
<br>
It was a great feeling when views started making sense to me. This could<br>
be better!<br>
I'm trying hard to expand my Drupal horizons while I can. I'm a long<br>
time .Net coder<br>
that fell into this Drupal opportunity 6 months ago. I certainly have more<br>
than I would<br>
if I had done this writing .Net code 6 months ago. Plus, it'll be<br>
maintainable by non-coders<br>
long after I have left.<br>
<br>
I'm trying to visualize how I would take this functionality and package it<br>
up into a module.<br>
Feel free to have fun if I'm way off here. Create a .info and .module<br>
file. In the .module<br>
I would want to write a hook into views that would create my custom view?<br>
It's reasonable to say module writers are PHP coders?<br>
<br>
Thanks a bunch,<br>
Phil<br>
<br>
<br>
<br>
<br>
<br>
From: "Metzler, David" <<a href="mailto:metzlerd@evergreen.edu">metzlerd@evergreen.edu</a>><br>
To: "'<a href="mailto:support@drupal.org">support@drupal.org</a>'" <<a href="mailto:support@drupal.org">support@drupal.org</a>>,<br>
Date: 12/05/2013 11:43 AM<br>
Subject: Re: [support] Registration module question...<br>
Sent by: <a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a><br>
<br>
<br>
<br>
I just got done doing something similar where I was creating a "contest"<br>
node type with associated "entry" nodes. I used entityreference and<br>
entityreference_prepopulate to allow me to create relationships between two<br>
nodes, and again I was left with trying to figure out how to generate a<br>
link for the user to create this content associated with the correct node.<br>
<br>
<br>
The basic strategy for generating the link was as follows<br>
<br>
First create a "view" that shows a single node with fields (or a list),<br>
with whichever of them you'd like to show. Next add the nid as a field to<br>
the view. This field will eventually become your link. In the<br>
configuration of the nid field choose "Rewrite Results". Check the<br>
"Rewrite the output of this field" options and type in the text you want<br>
this link to appear as. Check the "Output this field as a link" option<br>
specify the link path that you'd like to see. In your case it's probably<br>
node/[nid]/register , but in my case I was building<br>
node/add/entry?field_contest=[nid] and entityprepopulate took care of<br>
defaulting in the referenced entity and hiding the field for the user.<br>
<br>
This magic is basically how Organic Groups works these days which is where<br>
I found the information.<br>
<br>
Hope that strategy helps you.<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a> [mailto:<a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a>] On<br>
Behalf Of <a href="mailto:Philip_Wetzel@nhd.uscourts.gov">Philip_Wetzel@nhd.uscourts.gov</a><br>
Sent: Thursday, December 05, 2013 7:39 AM<br>
To: <a href="mailto:support@drupal.org">support@drupal.org</a><br>
Subject: Re: [support] Registration module question...<br>
<br>
Hi Steve,<br>
Thanks so much for taking the time to help me through this. I will do my<br>
best to return the effort somehow.<br>
<br>
I wiped everything out and started over. Followed your steps. I've pretty<br>
much been this far before. Now, when I view the node (logged in as admin)<br>
I see the event content with 4 tabs.<br>
This is fine for the person that is going to administer the event. They<br>
can view/edit the event, see who<br>
is registered, register someone, etc. I've created a view to better refine<br>
that.<br>
<br>
Now, comes my problem. I think I know some of the steps, but can't quite<br>
get it all the way yet.<br>
I want to have anyone off the street be able to go to our site, get a list<br>
of all the events.<br>
No problem there, create a view.<br>
<br>
Each event will have a link to the registration form and will allow them to<br>
register.<br>
This is pretty much where I fall on my face every time.<br>
If I go to the event I created in this case and clicked on the register<br>
tab, the URL<br>
would be localhost/node/467/register. I could easily hard code a link and<br>
do<br>
it manually. Of course, that is no good.<br>
<br>
I can almost see how to do this with PHP, but I imagine there's a way to do<br>
this without.<br>
I find it hard to believe that this wheel doesn't already exist.<br>
You certainly don't want your registrants to see the "manage Registrations"<br>
tab.<br>
But, out of the box this is the only way I see to do it.<br>
<br>
As I said, the Toronto Web Developer guy does exactly that, (with Node<br>
References).<br>
I've been through his video dozens of times, and I always end up close but<br>
no cigar.<br>
As I said, he's on Drupal 7, but I think the video was recorded prior to<br>
the release of the Registrations module. Actually, I just checked on that<br>
a little. The video was uploaded<br>
May 15, 2011. Looks like Entity Registration's first dev release was<br>
released 4 months later.<br>
<br>
At the very least, writing up my little dilemma helps me think it through.<br>
I think a PHP solution<br>
is starting to materialize in my mind. If I was smart I would take this<br>
opportunity to figure out<br>
modules, and hooks, and what not. I saw the Simplest module example and<br>
understand it.<br>
OK, I need to stop finger babbling and get my brain in gear.<br>
<br>
Thanks,<br>
Phil<br>
<br>
<br>
<br>
<br>
<br>
From: Steve Kessler <<a href="mailto:skessler@denverdataman.com">skessler@denverdataman.com</a>><br>
To: "<a href="mailto:support@drupal.org">support@drupal.org</a>" <<a href="mailto:support@drupal.org">support@drupal.org</a>>,<br>
Date: 12/04/2013 03:21 PM<br>
Subject: Re: [support] Registration module question...<br>
Sent by: <a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a><br>
<br>
<br>
<br>
Here is what I do.<br>
<br>
1. Create registration type<br>
2. Create a content type with a registration field.<br>
3. Create a node of the new content field that selects the registration<br>
type that I created.<br>
<br>
This has worked very well for me.<br>
<br>
<br>
On Wed, Dec 4, 2013 at 6:58 AM, <<a href="mailto:Philip_Wetzel@nhd.uscourts.gov">Philip_Wetzel@nhd.uscourts.gov</a>> wrote:<br>
Thanks Steve,<br>
It helps, but it's a bit beyond my current level of Drupal expertise. I<br>
think I'm<br>
so close I can taste it. I think I have everything I need (modules or<br>
coding) and it's just a matter<br>
of setup.<br>
<br>
Yaworski of Toronto Website Developer is doing exactly what I want to do,<br>
but I think the combination<br>
of modules he is using is just prior to when all of this was integrated<br>
into one module (Registrations).<br>
Specifically, he sets up the "Click to Register" feature right about 2:40<br>
in the youtube video below.<br>
<br>
<a href="http://www.youtube.com/watch?v=0CHC8I9xZIg" target="_blank">http://www.youtube.com/watch?v=0CHC8I9xZIg</a><br>
<br>
He uses node references. I go through the steps, but I don't end up with<br>
a<br>
link to my registration page.<br>
I don't end up with a link at all.<br>
I think the answer is staring me in the face, but I just can't see the<br>
trees through the forest.<br>
Phil<br>
<br>
<br>
<br>
From: Steve Kessler <<a href="mailto:skessler@denverdataman.com">skessler@denverdataman.com</a>><br>
To: "<a href="mailto:support@drupal.org">support@drupal.org</a>" <<a href="mailto:support@drupal.org">support@drupal.org</a>>,<br>
Date: 12/03/2013 12:06 PM<br>
Subject: Re: [support] Registration module question...<br>
Sent by: <a href="mailto:support-bounces@drupal.org">support-bounces@drupal.org</a><br>
<br>
<br>
<br>
You have a few of choices.<br>
<br>
You can make a view and use replacement tokens. Using the Views module<br>
you could for example display your listings on a calendar or in a table.<br>
<br>
If you want people to view the specific node then you could edit your<br>
theme<br>
template file to but a button on the node itself. I think you could also<br>
do this maybe even without code using the Display Suite Module (<br>
<a href="https://drupal.org/project/ds" target="_blank">https://drupal.org/project/ds</a>).<br>
<br>
In terms of taking out the tab that would also require changes to your<br>
theme.<br>
<br>
Hope this helps.<br>
<br>
-Steve<br>
<br>
<br>
On Tue, Dec 3, 2013 at 9:34 AM, <<a href="mailto:Philip_Wetzel@nhd.uscourts.gov">Philip_Wetzel@nhd.uscourts.gov</a>> wrote:<br>
I'm using the registration module to create scheduled events.<br>
I have a view that shows the events.<br>
I would like to add a button or a link that would bring up the<br>
registration<br>
form for that event.<br>
<br>
I have the title setup as a link to the original piece of content. If<br>
I<br>
click on it, I get the<br>
tabs (View, Edit, Manage Registrations, Register. I want my button<br>
to<br>
go<br>
strait to that<br>
node.<br>
<br>
For instance, the node for the event is node/457. I click on<br>
the<br>
register tab and I<br>
get node/457/register.<br>
<br>
How can I create a button that would take me strait to<br>
node/457/register?<br>
Also, I would need it to not show the other 3 tabs. I don't want the<br>
people registering for the<br>
event to be able to have those functions available.<br>
<br>
Is that enough information?<br>
Thanks,<br>
Phil Wetzel<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
<br>
<br>
--<br>
Steve Kessler<br>
Owner and Lead Consultant<br>
Denver DataMan, LLC<br>
<a href="tel:303-587-4428" value="+13035874428">303-587-4428</a>--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
<br>
<br>
--<br>
Steve Kessler<br>
Owner and Lead Consultant<br>
Denver DataMan, LLC<br>
<a href="tel:303-587-4428" value="+13035874428">303-587-4428</a>--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</blockquote></div>