I was talking about default behavior of sql addressbook (which you do not use), just to show possible (counter) solution.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 9 2016
The first issue was fixed in ab433d7428d6 (not packaged yet). The other is pykolab localization issue and is already part of T1358.
The default sql addressbook in Roundcube has functionality that makes sure new group (or renamed group) name is always unique instead of throwing an error. E.g. If you have group "My Group" and you try to create another with the same name, Roundcube will just create group with name "My Group 2".
Aug 8 2016
Aug 5 2016
There are other plugins too and there's an upstream ticket for this feature: https://github.com/roundcube/roundcubemail/issues/4971.
While I'm investigating the missing groups issue.... I couldn't reproduce the first described issue. I think this may depend on ldap configuration (and vlv configuration). Please, provide your ldap_public config and progide ldap_debug log.
Aug 4 2016
Fixed in Transifex and updated in git for release-1.1 branch.
Fixed in git and Transifex.
So, we have two issues here:
Fixed in git and Transifex.
Jul 29 2016
Jul 28 2016
Oh, as I understand the fix would be simpler. See kolab_filter variable in https://git.kolab.org/diffusion/P/browse/master/pykolab/auth/ldap/__init__.py;1c4d7bb4154143752af6e2542cdbfaf2f7372cb5$702. It is not used in this method, but should.
Probably the number of slots in an hour here should depend on Preferences > Calendar > Time slots per hour.
I don't get it. Resource is not a location. Even assuming some resources can have location specified (where in LDAP?) this could be somewhat confusing. What if the location was filled as you describe and then you edit the event changing the resource, should we then modify the location?
Jul 27 2016
Fixed Bug#1, Bug#2, Bug#3 described in my previous comment.
Ok, there's a couple of issues here described, but first... Let's agree that (while we do not support counter proposals) when an attendee changes a task's status the iTip REPLY is send to the organizer. When the REPLY is "merged" only an attendee status should be updated, NOT the completion status. Think about a task with two attendees (assignees).
It was fixed in rPbfb9070f4fb2e8f, pykolab-0.7.27.
These notices come from composer. Update composer.
Could you provide complete message sample? You can remove message/attachment bodies or other sensitive information, but keep the structure.
As I understand when you send a document from LibreOffice it will attach the document to the email message, right?
Jul 26 2016
Enabling syncing of all (selected) folders is one thing and disabling "flat mode" is another. I think this ticket is about the former.
Jul 25 2016
Jul 22 2016
Looks good to me. Only one objection, sometimes you use try/except for log.info() call, I'm not sure why you would do that. And you do not do this consistently.
Confirmed. I see this message is used sometimes when moving/resizing/deleting an event. However, I'm not really convinced about usefulness of such a message. I don't see a code that would "copy" the event to personal calendar, so it does not make sense at all.
Plugins localization updated in ab433d7428d649
Jul 21 2016
Jul 20 2016
Sounds like a duplicate of T1301. Could you confirm it fixes the issue?
Jul 19 2016
I'm unable to reproduce.
In mail compose searches are handled a little bit different than the searches in Addressbook if we consider groups. Here only cn attribute is used, in Addressbook we use more attributes.
migmak-232, migmak-575.2, migmak-569 are fixed on Transifex. After we fix other issues here, we'd need to update localizations in git.
According to http://www.useragentman.com/IETransformsTranslator/ for IE < 9 we need additional css hacks.
Fixed in 4361a9582050 [master] and fbf89913a30 [release-1.1].
This involves a lot of different components and not all are just "missing translation". Would be better to create a separate ticket for every issue.