CiviCRM Community Forums (archive)

This question was posted in a 2 year old thread so I thought a new one might be more appropriate.

In our work we are trying to avoid modifying core civi code as much as possible and using hooks for all modifications.

Using a form_hook we were able to set the options in the list. This would have been a lot easier except for limitations in the PEAR HTML_QuickForm_Select class.

The class contains no method to remove options from the list. After racking my brain for a while I resigned myself to a single line change in the PEAR class. (\sites\all\modules\civicrm\packages\HTML\QuickForm\select.php).

Basically I made the option list ($_option) a public property. Then in the hook I unset the option array and used the loadArrary() method to repopulate the list.

I'm thinking of submitting a more substantive update (a real removeOption method) to PEAR team but didn't know how this would find its way back into the Civi release.

How frequently do you integrate new PEAR releases?
Also it looks like the HTML_QuickForm package is deprecated and HTML_QuickForm2 is only alpha.

What's the best option for getting this into the code base.

Thanks

Basically I made the option list ($_option) a public property. Then in the hook I unset the option array and used the loadArrary() method to repopulate the list.

I'm thinking of submitting a more substantive update (a real removeOption method) to PEAR team but didn't know how this would find its way back into the Civi release.

We are planning to move away from PEAR / QF in CiviCRM v4.0 . Also i dont think QF is being updated any more

Assuming kiran's solution does not work, For now, i'd go with changing $_option to public. File an issue with the patch and we'll add it for 3.1.x

lobo