[support] Some last tweaks needed to registration module.

Prothero William waprothero at gmail.com
Fri Jan 10 20:08:31 UTC 2014


I had the WSOD problem and it was fixed by increasing the maximum allowed packet size in mySQL. It was set a 1Mb and the help guy said it is usually 16M. Fixed the problem nicely.
Best,
Bill

William Prothero
http://es.earthednet.org



On Jan 8, 2014, at 10:19 AM, Philip_Wetzel at nhd.uscourts.gov wrote:

> Well, I have 2 days left before I officially declare NH District Court
> Website is complete
> and move on to Probation (their website).   I had my dog and pony show
> yesterday,
> which went pretty well.   I think we all agreed that I met expectations.  I
> do however,
> have a list of "it'd be nice if you could...." items.
> 
> One thing I really want to figure out is with the registrations module.
> Out of the box you can
> list registrants with the standard columns.  If you add custom fields, such
> as LastName, FirstName to
> your registration type, you can list them here (with work).    I ran into
> trouble when I tried to make LastName
> sortable.  What's weird is it will sort once (and spew out errors).
> 
> Delving further.....  registration_registrations_page function...  It first
> builds the header.
> A standard column looks like this....
> 
>  $header = array(
>    array(
>      'data' => t('id'),
>      'field' => 'registration_id',
>      'type' => 'property',
>      'specifier' => 'registration_id',
>    ),
> 
> .....
> 
> I was hoping I could take my custom field and do something like this......
> 
>    array(
>      'data' => t('Last Name'),
>      'field' => 'field_last_name',
>      'sort' => 'desc',
>      'type' => 'property',
>      'specifier' => 'field_last_name'
>    ),
> 
> It doesn't like 'type' at all.....  SQL error.  Looking further you can see
> that the standard columns are in
> the table 'registrations' in this case.  My custom field is in a separate
> table.   field_data_field_last_name.
> (field_last_name is the name of the column).
> 
> The SQL query is expecting everything to be in the 'registrations' table.
> Is there some way I need to tell it
> to look in the other table for last name?    I haven't been able to figure
> out where in the code this query is happening
> (if that's even possible).  Currently out of ideas.
> 
> Anyone?
> Thanks in advance,
> Phil
> 
> PS: on that very page they indicated that they would like a button to press
> to print all registrants and
> a button to dump all registrants into a comma delimited .CSV.  I have no
> clue how to do that - haven't
> had time to search on it.  Thought I'd throw that one out too.
> 
> -- 
> [ Drupal support list | http://lists.drupal.org/ ]



More information about the support mailing list