A quick braindump:
Profile are a great way of simplifying the interface and provide more focussed forms, but some of the goodies of the normal edit form are gone. For instance, the employer isn't anymore an autocomplete field. luckily, with the REST interface and a jquery autocomplete plugin, that's a few lines to add to make it work:
add on the templates/CRM/Profile/Form/Edit.tpl
{if $session->get('userID') > 0} {literal} jQuery(document).ready(function($) {The past week was quite interesting and generated a fair amount of traffic and news about CiviCRM. It compelled me to summarize and link to the various blog posts :)
I think that here in the UK, we're missing out on something. Ideally I would like to have a central place to communicate and support each other with civicrm. Hopefully this will help organise meet ups and other events in the same timezone.
I have set up a provisional group at http://tech.groups.yahoo.com/group/civicrmuk/ if you could join up and start the ball rolling.
I'm putting this together to help the next version of civicrm. We needed a waiting list for events once they are full. Our needs will perhaps differ from a generic version but you have to start somewhere.
We started by detecting the state of the event with eventFull(). If it's full and the user is not already a participant OR in the waitinglist table, we give them a simple link which will add them to the waitinglist table.
The documentation for CiviCRM 2.2 is up and so are the new docs for CiviMail Installation, including a sub-page on CiviMail Processor.
Along with the introduction of CiviMail Processor as the new supported return email hander, we’ve made three changes that are relevant for third-party CiviMail developers in CiviCRM 2.2.
Unified email formats
Thanks to the invitation from Joomla! and their kind sharing of the precious student slots, CiviCRM was able to participate in last year’s Google Summer of Code, with the GSoC project adding multilingual support to CiviCRM.
