Re: setting the Syncml uri for calendar/tasks/notes to another than the default one

[email protected]
Newsgroups gmane.comp.horde.sync
Message-ID <[email protected]>
> Zitat von [email protected]:
> 
> > Hello
> >
> > I can not determine the right url for horde  if I wan to sync  
> > another than the default calendar or task, memos vith SyncML.  I was  
> > able to set the sync with the default one by setting url = calendar  
> > on the client side (Syncevolution on my N900), the same for tasks  
> > and memo. But if I have for example a work calendar on my phone and  
> > set the source for calendar to this one and let the uri = calendar,  
> > the SyncML writes the work data to the default calendar one on my  
> > horde groupware. I can not find any documentation related to this  
> > issue, could someone help me please ?
> 
> This doesn't have anything to do with synchronization URI. Up to  
> Kronolith 3.0.4 you can only synchronize with the default calendar.
> 
> Jan.
> 
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
> 
> -- 
> sync mailing list - Join the hunt: http://horde.org/bounties/#sync
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: [email protected]
> 
> 
> 

Hello

To be honest this did not make this topic any clear. I have horde groupware 4.0.1 with Kronolith 3.0.5. I found in settings the option to select which calendar should be synced with horde. But if I choose the work calendar on the client, the work data are being written in the default calendar. Could you be so kind and provide a short explanation how to sync the work calendar on the client with the workl calendar in horde ? I use Syncevolution on my Linux and on my Mobile phone.

Thanks Karel 
-- 
sync mailing list - Join the hunt: http://horde.org/bounties/#sync
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.