- Cleanups and tests
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 15 2025
Jul 14 2025
Jul 11 2025
Jul 10 2025
Jul 8 2025
- Don't consider existing domains in the same account as non-existing
Jul 5 2025
- Save ACTIVE status before createing an LDAP record where it may be relevant, simplify some code
Jul 4 2025
The way we use folder_id() in kolab4 driver is different. Also I think we could probably get rid of object_prettyname(). Anyway, see my untested version in https://git.kolab.org/D5457
- Use saveQuietly()
- Remove redundant code
- Throw an exception if mailbox already exists (added a way to disable this)
Jul 3 2025
is_broken would be better because we already have is_deleted in some tables, but fine.
We should make this new code consistent with kolab_sync_storage_kolab4::folders_list(). You can find there how we handle special folders type. kolab_storage::folders_typedata() should not be used.
I don't see how you unset the "broken" state. You said that when you reset Outlook according to your manual it will use the same device identifier. How it will unlock itself then? A test would be nice.
Makes sense.
Jul 2 2025
This may not be a big win because non-owner users do have meet room entitlements in their wallets. Hopefully abusers never visited the Video chat page in dashboard, i.e. the entitlement wasn't created for them.
Jul 1 2025
- Fix test regression
Probably 5 instead of 10 would be enough.
Jun 30 2025
Jun 27 2025
In D5406#70137, @mollekopf wrote:In D5406#70107, @machniak wrote:We already have $config['activesync_force_subscriptions'] in the kolab_activesync plugin. It would make sense to de-duplicate.
How do we deduplicate accross plugin boundaries?
We already have $config['activesync_force_subscriptions'] in the kolab_activesync plugin. It would make sense to de-duplicate.
Jun 26 2025
- Reset password only after full authentication
- Wording
- Revert possibility to check password policy using email address
Jun 25 2025
- Move checks into the SQL query
Jun 20 2025
Jun 19 2025
Jun 18 2025
In D5388#69819, @mollekopf wrote:A more generic solution might be that the client can simply list the thing's it wants. which would be 'id' in this case (I suppose having the access_token implicit makes sense?).