CiviCRM Community Forums (archive)

In 4.6.beta1, the default frequency unit is now 'weekly' which I think is the natural default.

The reoccurring charge is set to the "Hour" ?
Normally they are ran as a batch item at mid-night. ( or at a predefined time for the day as set by administration able to take into account high-volume traffic hours.
#just saying.

I am new here but have been checking out the drupal version of this software for a bit over a month now off and off and on.

Since you're the bigboss nerd, do you mind me asking, a question? if so, skip the next part
============
Pre::  If you don't mind me asking, and keeping in mind business patterns, scale-ability & performance. I'm a bit confused, because it seems to me this is not an enterprise piece of software. As more "satellite" instances of the civiCRM are allocated it seems like the performance level could get totally out of hand very quickly, not to mention the security risks, and of course the ability to loose all aspects of robust behavior.  One person makes a bad db
mod update, and until someone else rolls it back,  your system is 'down', not to mention other scenarios which could compromise/challenge the concept of robust behavior.
===
So, my questions are:
1. Is my assessment of this way off-base?  I'm honestly, not very familiar with drupal.
2. Are there plans in the future to make this a true a) three-tier architecture /compiled data layer and b) client/server app?
or is there a project road-map someplace I missed? (entirely possible on both points.)

Thanks, I asked these questions to better understand the overall picture of the project and it's future directions.


~thanks
~e

Coleman, I've just sent a PM to @LindseyM asking for his thoughts on hourly recurrences. He's a champion for recurring events/activities so may have a view on that.

Another thought on this issue. If I remember correctly the model for how CiviCRM should implement recurrence was "how Google Calendar does it".

I just checked on Google Calendar and the recurrence options are "Daily, Weekdays, Mon/Wed/Fri, Tue/Thu, Weekly, Monthly, Yearly". So there's no "Hourly" option.

I'm not suggesting we drop "Hourly" solely on that basis, but it there is no clear use case, and there are implementation issues, should it be a 4.7 enhancement?

@LindseyM,

Thanks for your input. is there a specific use case for hourly? Do you or Veda have something in mind?

Ken

Thanks Deepak. I think you're right that hourly is unlikely to be relevant to recurring events but may well be relevant to recurring activities. On that basis it's worth keeping it as an option but perhaps make the default weekly instead of hourly as that's more relevant to the majority? Is it possible for 'hourly' to be in the Option List 'recurring frequency units' so that people can disable it if necessary (as I think Coleman mentioned that at present it requires code rather than UI action?