San Francisco Code Sprint - May 24-25 - Post Your Ideas Here

[Dave Greenberg]

Post your ideas for things you'd like to work on during the sprint.

[Coleman Watts]

I'd like to work on the api, especially getting its handling of custom fields in order, which is currently a mess.

[Donald Lobo]

A sampling of things that we'd like to cover:

   •   Increasing unit test and webtest coverage. We will definitely do a session or two on creating and building new web tests.
   •   Adding more functionality to API version 3. On the plate are recurring contributions and custom value API
   •   Building / Reusing code that will make migrations of "meta-data" easier from dev -> staging -> production
   •   Tackle some of the simpler, more significant issues that are not resolved
   •   Fixing notices across CiviCRM 4.0 (which is an issue with Drupal 7 where notices are enabled by default)
   •   Improving current set of reports. Some ideas include: Adding contribition page to contribution reports, Adding primary vs inherited membership filter on membership reports. Adding campaign functionality to various reports
   •   Adding more actions to various component searches. Add to Group and PDF letter seem good ones to add to the list
   •   Extending relationship form to create a new contact

We can get into more detail tomorrow.

lobo

[xavier]

I'd like to work on the api, especially getting its handling of custom fields in order, which is currently a mess.

If you could find a way to translate custom_myname into custom_42 (eg. if the part after custom_ isn't an integer, do a lookup), it would be easier to make modules that deal with custom fields without having to recode the id.

X+

[Donald Lobo]

depends on what the protocol for myname is. If we agree that myname is:

groupName:fieldName (need groupName to make it unambigous), there is a function:

CRM/Core/BAO/CustomField.php, function getCustomFieldID

which takes the label or name and gets the fieldID from the DB

using name might be a bit easier and saner than label and can probably embed it in smarty much easier (i.e. no backquotes etc)

lobo

[xavier]

depends on what the protocol for myname is. If we agree that myname is:
groupName:fieldName (need groupName to make it unambigous), there is a function:
...
using name might be a bit easier and saner than label and can probably embed it in smarty much easier (i.e. no backquotes etc)

Definitely name rather than label. and definitely some form of concatenation of groupname+fieldname if fieldname isn't unique by itself.

I am not 100% sure $_GET ['groupName:fieldName'] or the equivalent in smarty work (ie. if ":" is a valid char) but if it's the case, fine, otherwise whatever is the easiest (custom_groupName['fieldName'] ?)

X+