CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Remove/Change Year Requirement on Price Sets
Pages: [1]

Author Topic: Remove/Change Year Requirement on Price Sets  (Read 1642 times)

dtheweather9

  • I post occasionally
  • **
  • Posts: 57
  • Karma: 1
    • Students for the Exploration and Development of Space, USA
  • CiviCRM version: 4.4.0
  • CMS version: WordPress 3.8.1
  • MySQL version: 5.1.56
  • PHP version: 5.4.11
Remove/Change Year Requirement on Price Sets
April 02, 2013, 10:47:54 am
Greetings,

Our organization has it setup so that between November and Mid April, dues will cover the current year, then from Mid April to November, the price stays the same, but the length of the term effectively becomes two years (the remainder of the current year and the following year).  In our case its due to the primary services we provide occurring in the September through April timeframe, but I could see other organizations having a cut off date with the fixed terms so that it also applied to the following term.

  Basically we can do the two ( or 1 and a half) terms with the # of terms set of '2' for each membership, and the timeframe in the 'Active on' and 'Expires On' settings.  That being said, the 'Active On' and 'Expires On' appear to require a date tied to a year, as opposed to 'every year on 4/1'.  I suppose it'd be possible to create a cron or a scheduled task that would change those each year so it isn't forgotten about to make it as autonomous as possible, but would it instead be possible to make the active on and expires on field can also be set to a month/day and not require (but still allow) a year? 

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Remove/Change Year Requirement on Price Sets
April 02, 2013, 12:13:58 pm
Have you looked at covering those rules into the Membership Type configuration (Administer > CiviMember > Membership Types? At first glance it seems like you could set up a Fixed period membership type with:
- fixed period start date = Nov 1
- fixed period rollover date = April 15

You can then offer that membership type as part of a price set if needed (i.e. you want to include other 'purchase-able' items).
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Remove/Change Year Requirement on Price Sets

This forum was archived on 2017-11-26.