Keel - LDH Middleware issueshttps://source.puri.sm/liberty/host/middleware/-/issues2020-03-09T22:04:23Zhttps://source.puri.sm/liberty/host/middleware/-/issues/96Enable Beta functionality in middleware2020-03-09T22:04:23ZDavid SeawardEnable Beta functionality in middleware**User story:** I am a product manager. I want to see new features in production system, so I can perform final integration and UX tests.
**Proposed solution:** We already have a "Beta" group defined in LDAP. Can we formalize this as a ...**User story:** I am a product manager. I want to see new features in production system, so I can perform final integration and UX tests.
**Proposed solution:** We already have a "Beta" group defined in LDAP. Can we formalize this as a "Beta" service in the middleware?
This will allow us to add Beta features to the middleware templates. Let's say we're adding feature `foo` to template `bar`, we tag it such that only Beta users can see it. Once we've confirmed that we're happy, we untag it in the template, deploy a new version, and everyone can see it.
The "Beta service" should be hidden to non-Beta users :)Boring badgerDavid SeawardDavid Seaward2020-03-12https://source.puri.sm/liberty/host/middleware/-/issues/92Update django-ldapdb to the latest version once our changes get accepted2023-05-24T11:46:00ZBirin SanchezUpdate django-ldapdb to the latest version once our changes get acceptedWe found out that the way `django-ldapdb` handled LDAP entries updates were sub-optimal when using LDAP groups with thousands of members. To solve that we created a PR with a solution:
https://github.com/django-ldapdb/django-ldapdb/pull...We found out that the way `django-ldapdb` handled LDAP entries updates were sub-optimal when using LDAP groups with thousands of members. To solve that we created a PR with a solution:
https://github.com/django-ldapdb/django-ldapdb/pull/198
If this PR get accepted it will probably make it to latest `django-ldapdb` version, therefore we will need to update the packages dependencies of the project to start using it.Birin SanchezBirin Sanchezhttps://source.puri.sm/liberty/host/middleware/-/issues/88Migration path for pre-existing WooCommerce accounts2020-05-06T16:26:54ZDavid SeawardMigration path for pre-existing WooCommerce accounts**User story:** I am a returning customer. When I subscribe, I want to use my existing shop account, so that I can see all my orders in one place.
**Suggested solution:** Custom registration page for existing WooCommerce users prompting...**User story:** I am a returning customer. When I subscribe, I want to use my existing shop account, so that I can see all my orders in one place.
**Suggested solution:** Custom registration page for existing WooCommerce users prompting for:
* Existing address
* Existing passphrase
* Librem One address
* CAPTCHA
```
Given there is an existing account
And the Librem One address is available
When the user enters the correct credentials
Then create a gratis Librem One account
And set the recovery email to the old address
And update the WooCommerce account details
```
...the user can now migrate to a gratis account, and upgrade to a paid account if they want to.
**Notes:**
We currently disallow recovery emails that match an existing WooCommerce account. Replace this error message with something like:
> This recovery email is in use at the shop. [Please migrate your account.]()
Additionally, we should offer a migration link from within WooCommerce. (New ticket once this one is complete.)Boring badgerDavid SeawardDavid Seaward2020-03-09