CiviCRM Community Forums (archive)

The site I am working on has two separate donations pages. One dedicated to one time donations and one dedicated to recurring donations. Right now CIVIContribute lets the users choose whether to check the recurring donation box or not on the monthly donations page. This has lead to a lot of confusions both with the users not making the donations they wanted to and with our system where we recently discovered sometimes it is being counted as a monthly contribution with our payment processor but is not being recorded monthly in CIVICRM (our research has lead us to suspect the two issues are related). What we would like to do is make the recurring donation check box required for the user to submit the transaction. If they do not wish to check the box they can then go or be directed to our one time contribution page. Does anyone have any ideas on how this could be accomplished?

Thanks for everyone's time on the matter!

Another option would be to edit/create a custom version of the contribution page template (saving it in your custom_templates directory) and use the contribution page id to customize the recurring option radio buttons to be what you'd like

FYI here is a link telling where the code for the recurring part of the form is and how to modify it (for a different purpose than what you are doing, but similar enough to give you some hints):

 http://wiki.civicrm.org/confluence/display/CRMDOC/Modifications+to+Contribution+Page+Templates

And here is some template code we used to modify event confirmation emails based on event id.  Your mod to the contribution page template would look sort of similar except, obviously, based on contribution page id.  I confess don't know what the variable name is for contribution page id (or even for certain if it is available to the template without some custom coding).

      {if $event.id  eq '7461'}
             <p>{$event.confirm_email_text|html2text}</p>
      {else}
             <p>{$event.confirm_email_text}</p>
     {/if}

Yes, looking at the tpl more carefully it would have been a mess to try to do that particular mod at that level.

What seems to work is this hook:

function hook_civicrm_buildForm($formName, &$form) {
 //echo $form->_id . ' hi ';
if ($formName == "CRM_Contribute_Form_Contribution_Main" && $form->_id == 35) {
 
    $form->setDefaults(array('is_recur' => 1));
    unset($form->_elements[$form->_elementIndex['is_recur']]->_elements[0]);
  }
}

Obviously, change 'hook' in the function name to match the name of your module.

The $form->_id is the id of your contribution page.  You can see the ID number in the URL if you edit that contribution page etc.

This is based on the comment here:   http://forum.civicrm.org/index.php?topic=17372.15  It has the disadvantages noted in that comment, but it does work and doesn't look terrible.  Presumably you could set the form element to hidden if you want it to look better.  (Though if you do that, you would probably also want to mod the TPL, or removing/modifying the explanatory text that the TPL inserts after the recurring contribution form element somehow, because that text won't make any sense once the recurring options are gone).

Edit: Note that the $formName == part is very necessary and also, must come before the $form->_id == part.  (Often the $form->_id is protected value and so you get a nasty error trying to access it).