CiviCRM modifications needed

[microsyskl]

I am an IT consultant and have setup CiviCRM on Drupal 7.  This is running on a VPS Ubuntu Linux 10.04.4 platform.   It is working fine but my customer would like some tweaks mad that I am unable to produce.  I am Looking  to sub out a couple modifications they are looking to incorporate into the site.

We currently have the CiviContribute and CiviEvent mods operational. 

1) They would like to add the ability for a visitor to DESIGNATE where their contribution would go (as an option - only if they select).
2) Get CRON to run automatically - i have to manually execute for recurring payments, etc.
3) Add addl field/multiplier that would allow someone to purchase multiple quantities of an item.  Currently we have a single contribution page for a single item(book).  Want to give visitor ability to select more than just one and have total calculated for that book.

Can explain more if interested

[joanne]

Have you read the User and Administrator Guide http://book.civicrm.org/user/
and the Administrator's Guide (supplement) http://wiki.civicrm.org/confluence/display/CRMDOC/CiviCRM+Documentation

If you can set up CiviCRM on Drupal 7 then you should be able to do 1) and 3) yourself.  Not so sure about 2) as I have never had to do that  - and I am not an IT consultant.


3) can be achieved using a price set.  http://wiki.civicrm.org/confluence/display/CRMDOC/Contribution+Price+Sets.  You would have a field type of Text/Numeric Quantity and the price would be the cost of one book.

1) can also be achieved with a price set 

[clarkac]

2) Is easy to set up if you have access to cPanel (assuming a Linux server)

[Upperholme]

Hi microsyskl. Did you get these issues resolved?

[microsyskl]

No, unfortunately I  have not.    Can't seem to get things setup properly

[Upperholme]

1. Perhaps the simplest route here is to use a webform instead of the standard Civi contribution form?

2. Cron: If you're unable to set up a cronjob on your server maybe using the CiviCRM Cron module for Drupal 7.

3. Sounds like using a price set could solve this problem.