Many modern web applications have a lot of spam deterrent such as Captcha, Bayesian filters, URL, ip detections etc. One example is trying to do 2 consecutive search on the CiviCRM.org forum and you will get a an error that look like
"Your last search was less than 5 seconds ago. Please try again later."
The concept behind this is flood control is to prevent a webbot (automated script) that is trying to spam and flood the server.
I’m happy to announce the rebuilding of CiviCRM translation resources. If you’ve been a visitor to our Transifex page previously, you know that CiviCRM always ran two concurrent sets of translation resources – one for the stable version and one for the upcoming version (since its first beta release). This was cumbersome – and is the past now.
The team is excited to announce the release of CiviCRM 3.3.6 - it is now available for download. You can also try it out on our demo site. This is a bugfix release resolving a few issues.
Update: We now have sponsorship committed for 63% of this project and have started a Make-it-Happen Campaign!
CiviEvent is the most popular CiviCRM Component. We get a steady stream of feature requests along with quite a few patches. We were approached recently by an organization that wanted to add Reminder Emails for CiviEvent.
We had a quick online and offline conversation with them and realized that there was a fair amount of cool integration so an event administrator could schedule and send messages to event participants. Briefly the set of features would include:
Ability to schedule a mailing 'n' days before / after the event start date / end date OR on a specific date. This will allow an event admin to schedule a reminder email 7 days before the event and a thank you email 1 day after the event. Ability to decide who the recipient list is based on a combination or participant role (attendee, sponsor, volunteer) and participant status (Pending, Registered, Wait Listed, Cancelled). Ability to type the text/html message and subject or use a civicrm message template. Ability to include event information in the message as "civicrm mail tokens". Sending the event as a vevent/ical format used by exchange/gmail, so the recipient can register from within the mailStable is getting close! This week, we bring you totally new thrill in CiviCRM Releases series (season 3.4/4.0) - the BETA1!
An remember - if you didn't already, make sure you read "Step up and help out" section of this blog post!
Versions released today are:
As announced earlier, the Location API has become obsolete in API version 3, which is currently shipped with the 4.0/3.4 alpha versions. It has been replaced by Address, Email, Phone and Website API in v3.
However, in the v2 Location API there was already a param 'version' which was used to determine if the older functionality of the Location API (CiviCRM version 2.2 and older) was used or the newer functionality (CiviCRM 3 and onwards). So the code looked like this:
Paging all multilingual CiviCRM users: We’re considering turning some of the multilingual fields back to be monolingual (i.e., have the same values in all languages, even on a multilingual installation), and your feedback on this is crucial.
Join the next meeting of the Dallas / Fort Worth CiviCRM Meetup group on April 6, 2011 at 7:00 PM.
You have the need for CRM solution, know where to host it, but not quite sure about the next step? Come and see how to install CiviCRM in 45 minutes from download to running.
RSVP through our Meetup page.
Sorceforge recently conducted an unscientific twtpoll that yielded interested results. The top four factors in the success of an open source project were:
Did you already try CivicRM 3.4 and/or 4.0? If not, we're releasing next alpha version, third one, especially for you. :-) Before downloading, make sure you read "Step up and help out" section of this blog post and let us know what you think (and what problems did you encounter).
Versions released today are:
