Author Topic: Where does price set structure come from? (Read 1315 times)

qjensen · September 11, 2010, 06:24:44 pm

I am working on a module to provide permissions settings for price set options. The idea is that you can select groups that have access to specific price set options. As part of the process I also created a price set hook similar to the buildAmount hook (with much help from Lobo).

My hook is in CRM/Price/BAO/Set.php at the end of getSetDetail and is being called as expected.

I am modifying the price set structure and removing any of the price options that are not accessible to the current registrant. Using XDebug I can see that the option is removed from the structure, but when the form renders, it still shows the option. I've stepped through the code and haven't found any other location where the price set is modified.

I cleared the drupal cache, removed cached docs in templates_c, cleared the browser cache and recreated the price set just to be safe.

Is there another place in the code that I should place this hook? I assume I am overlooking another location where the structure is setup, or a different structure is being used to build the form and I am missing it completely.

Thanks for your help,
Quint

Donald Lobo · September 12, 2010, 08:51:13 pm

can you post your patch. we'll apply it and take a look at whats happenign and why

thanx

lobo

qjensen · September 13, 2010, 01:33:43 pm

Hi Lobo,

Patch files are attached.

Thanks for taking a look.

Quint

qjensen · September 17, 2010, 02:53:21 am

OK - I think I've got it. Even though it looks like there is a nice price set structure used to build the form, that isn't really the case. When the actual form is built, the field id is passed to CRM/Price/BAO/Field.php::addQuickFormElement. That function ends up getting the price field options directly from the db using getOptions.

Now that I understand what is happening, I am a little confused. It seems like there is a lot of work and copying going on to build a structure that never really gets used. We end up with $priceSet and $form->_values, both of which have a copy of the price set structure. $form->_values gets used once, just to get the individual field ids and start the price set form, but the rest of the structure appears to be unused. Then, after we already have 2 copies of the price set structure, we go and ask for all of the price field options one more time, just to be sure, in the addQuickFormElement function.

I think I may have to rewrite my hook as a price option hook instead of a price set hook, since there doesn't appear to be a price set structure to modify like there is with the buildAmount hook.

I am relatively new to digging around the internals of CiviCRM so if any part of this is wrong I claim safe haven in my newbie status

CiviCRM Community Forums (archive)

News:

Author Topic: Where does price set structure come from? (Read 1315 times)

qjensen

Where does price set structure come from?

Donald Lobo

Re: Where does price set structure come from?

qjensen

Re: Where does price set structure come from?

qjensen

Re: Where does price set structure come from?