8000 Add a Save button below the License Ownership information fields · Issue #130 · xwikisas/application-licensing · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add a Save button below the License Ownership information fields #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AndreeaChi opened this issue Oct 13, 2022 · 3 comments
Open

Add a Save button below the License Ownership information fields #130

AndreeaChi opened this issue Oct 13, 2022 · 3 comments

Comments

@AndreeaChi
Copy link
AndreeaChi commented Oct 13, 2022

Hi! It would be more user friendly to have a Save button under the License Ownership fields in the Licenses administration.

Currently, the only option to save those details is to click on the Buy, Get trial or Extend license buttons, next to an installed Pro application shown in the Licenses table (or to edit the Licenses page in object mode to add those details).

image

@mflorea
Copy link
Contributor
mflorea commented Oct 20, 2022

Yes, but why would you fill those fields if not to be able to buy a license or get a trial one? What workflow do you have in mind? Filling license ownership information and then leaving the page doesn't make much sense no? The Save button you propose might make things clearer but it also adds an additional click.

@oanalavinia
Copy link
Contributor

I think I have a usecase. Now once you have a trial license added any new extension install will add automatically a trial license for your app, so after the first get trial you won't see the button again. This can make it harder for users to change the license ownership fields before an extension install if they don't have any Extend trial

@mflorea
Copy link
Contributor
mflorea commented Oct 20, 2022

OK, so the use case is changing / updating the license ownership information. I agree it's a valid use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
0