How much server (disk space and memory) do I need to run my CiviCRM implementation....
The answer is, of course, it depends. But what are the critical factors?
-- Data base size (Number of contacts and number of custom data fields, relationships, groups, etc.)
-- Number of users (light usage vs. heavy usage)
-- What other applications will be running? (A CMS with a small data base or Jasper Reports with a lot of simultaneous users.)
I think it would be good to put forth some guidelines or rules of thumb.
For example for a database with 30,000 contacts, 200 custom data fields, a few dozen groups and relationships, integrated with a Drupal website with 200 pages with 5-10 heavy Civi users and a few hundred authenticated users….what you recommend and why? What if those 5-10 Civi users were also running Jasper reports?
If you have experience hardware sizing or, even better, if you are a hosting provider I’d love to hear what...Read more
Recently someone asked about setting up an autocomplete in a profile where the person completing the form would be offered the name of existing organisations in the database. We have implemented this with a couple of different variations and I did promise to provide some information on this so here goes. I’ll try to explain a whole lot of ‘customising civicrm’ concepts but this isn’t a step-by-step recipe you’ll have to add a fair bit of technical know-how/ extra reading to flesh this out for your own purposes. I have added a recipe-type summary at the end just to sum up. Areas I will touch on are:
UPDATE - THIS BLOG IS OVER A YEAR OLD. AT THE TIME IT WAS ANTICIPATED THE PATCH WOULD GO INTO CORE. THIS HAS NOT HAPPENED AND IS NOT ACTIVELY BEING LOOKED AT. THE BLOG IS STILL VALID IN MANY AREAS BUT PROCEED WITH CAUTION
- Customising a template
As we’re closer and closer to the release of CiviCRM 3.1, we began thinking what to schedule in CiviCRM 3.2. As one of the features we want to add is the ability to undelete certain CiviCRM entities, we want to discuss with the community the initial approach to undelete that we came up with – along with a sketch of logging functionality that we consider for a future release.
To make both of these features successful, we need something that’s both generic (i.e., works in the same way – or, at least, similarily – for all/most of the CiviCRM tables) and transparent from the perspective of the existing codebase. The experience with multilingual support done in that matter convinced us that it’s a sane approach; move as much as possible to the database layer, sprinkle with views and triggers if needed, add a bit of logic to CRM_Core_DAO and make the existing codebase blissfully unaware that there’s hidden functionality beneath (with the...Read more
The past two days a group of us gathered at the Mitchell Kapor Foundation offices in downtown San Francisco for the first CiviCRM Test Sprint. Some of the highlights of the event were:
- Introducing the concept of testing and our current framework for unit testing. CiviCRM uses PHPUnit for unit testing. We also use XDebug for code coverage. You can see the latest results of our testing here
- Improved the test coverage for our upcoming CiviCRM 3.1. Our goal before the final release of 3.1 is to have 80% coverage of the CiviCRM API and 50% coverage of the CRM classes. We are well on our way to meeting this goal.
- Improved the framework so we can make things easier and more efficient for future testers. Sasha worked on automating creation of CiviCRM objects via a generic method. We extended this to create all...
- Implement hook_civicrm_pageRun for the profile view page (CRM_Profile_Page_Dynamic). Only implement this hook for the specific profile id's you want relationship information. In this case we have two profiles, a Parent Profile (gid=3) and a Student Profile (gid=4)
- The pageRun hook also adds the module's template directory to the smarty include path, so we dont have to set it globally. This also allow multiple modules to append different template directories to the template...
Active Record, properly defined, is a design pattern where an object is represented as a record on a table in a relational database. As most know at this point this has been the ORM design pattern of choice in Ruby on Rails(RoR), although that is starting to change a bit. Because of the assumption of "one object - one record" there are a lot of...Read more
Current CiviCRM architecture pitfallsrasantiago has proposed a new CiviCRM architecture with details of the ORM layer. Torenware commented on the latter and mentioned some particular scalability issues. Our own experience with the Active Record design pattern proposed by rasantiago is that it works well for small projects but doesn't scale well. We believe that CiviCRM is now... Read more
For those who are not familiar with Active Records and ORM a little background will help. An object relational mapping (ORM) layer translates objects... Read more
After a lot of work and prototyping we think we may have found an architecture that will work and a path to that architecture. From this work we offer a... Read more
How do I set up a multiple-record custom data group?
- Go to Administer CiviCRM » Customize » Custom Data
- Click "New Group of Custom Fields"
- Select Contacts, Individuals, Households or Organizations for "Used For" record type. ...