I'm using the dav resource to connect to my google account. Also this google account is connected to my android phone. When adding an event via the phone this event is correctly shown in Korganizer after synchronizing. However this event always belongs to the "Categories": * "http" * "//schemas.google.com/g/2005#event" which is ugly and I obviously don't want this. Note that I didn't add such categories and if I delete the categories they are recreated when adding a new event via my phone. Also note that manually unticking the categories for each event works and is remembered. When adding the event via the google webinterface no such things happen but when comparing two events (one created by webinerface, one created by phone) in the google web interface I cannot see any difference; there doesn't seem to be the concept of "categories" at all. Reproducible: Always Steps to Reproduce: 1. create google-acc. and add akonadi dav-resource to connect to that 2. connect an android phone to this google account 3. create an event on the android phone Actual Results: korganizer shows that this event belongs to two specific categories (explained above). Expected Results: I want the event to be in no category at all (if not specified at creation).
Thanks for the report. Could you attach the same (anonymized) .vcf, one exported from kaddressbook and the other from google. Unfortunately I don't have an android phone.
Created attachment 79390 [details] .ics from google, .vcs from korganizer phew.. that was not an easy task as it turned out. What I have now is an "ics" file from google and and "vcs" file from korganizer. I hope this suffices (it seems one cannot get a vcs from google directly). If you look at it you'll notice this line in _both_: "CATEGORIES:http://schemas.google.com/g/2005#event" 1) obviously it's one category, not two. 2) okay, it's in both, so this category is google's fault. Nevertheless it would be nice if kde could simply ignore this kind of category and automatically get rid of this category in its events. I mean.. it doesn't seem to serve any purpose at all, does it?
It's a weird behavior from Google, not something that should be manipulated by the resource unfortunately.