I just wanted to give you all some update on how we are getting on with the development of CiviSync. The application interface is ready. There will be three buttons on Outlook Toolbar to Sync Contacts, Sync Email and Settings. I hope they are self explanatory. We have also worked on a number of setting options to make it as extensive as possible and at the same time user friendly as well.
When we started working on the synchronisation, we realised that CiviSync can not work out of the box because of two main reasons:
- A Site Key is not generated in an installation by default which is required for logging in to CiviCRM using REST API.
- The user logging in should already have an API Key in the database
The site key can not be created from the user interface and hence the user can not use CiviSync until the admin/someone goes in the civicrm.settings.php and creates a site key.
The API Key is more awkward where the user will have to go to the database and create a new API key for the other users who are allowed to use the REST API and hence CiviSync.
So after a lot of discussion internally in Target Integration; we decided that we will create a new component for Joomla and module for CiviCRM which will overcome the issues and make it easier for super administrators to create a new site key and create and remove API Keys for the users.
Hope to bring CiviSync to you by the 3rd week of February..
Comments
Hi Polestar
sounds like good progress and I'm excited to hear you're getting there. You mention a component for Joomla! but not Drupal. Is that because it won't be needed with the current Drupal version of Civi or just that you're not developing this for Drupal?
Regards
Davem
Ah Davem!!
Well picked up. Yes there will be a Drupal Module as well. My small brain forgot to give the instructions to the hands to write it in the blog. Seems like I need an upgrade.
the CiviCRM installer automatically creates a site key (32 character md5 hash) and instantiates that in the settings file
you should raise the api issue with the api team
lobo
most def, we need to talk!
I would suggest that instead of dev a separate module, you add the user key mgt in civi. We never did it because so far all the REST users are only using it for one external server user, so having to dig into mysql isn't a big deal. As you push it further, it would make sense to add this feature.
Ping us to discuss the details.
Otherwise, you might have seen that we are preparing a v3 for the api. Don't worry we will maintain v2 too on 3.4/4 but I would like to have your input on the new version, now is the time to verify if it improves for your as well.
X+
Hi Xavier,
Ping :)
I agree that future versions can have the feature of managing "API Keys" built in to CiviCRM but we want to support CiviCRM version 3.2 onwards so that existing installations can also use the features without the need of an upgrade and hence the module/component will be created.
We are keeping an eye on API v3 progress and will get some feedback over to you. I am available on gtalk using rohit at targetintegration.com or skype rohitthakral
Thanks
Rohit
That's Great Lobo. I will talk to the team and see what they think.
Can you do sync also for Thunderbird?
We haven't thought about it yet but that definitely is a possibility.
I'm wondering if you could check your code into svn somewhere so others could start helping you. I think this is an important contribution that is an important feature for many potential CiviCRM users.
Where is this new release of CiviSync? Can it be downloaded from anywhere for testing or deployment?