Skip to content
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

occ app:enable should exit with proper error message if enterprise key is invalid #36351

Closed
xoxys opened this issue Oct 30, 2019 · 3 comments · Fixed by #36399
Closed

occ app:enable should exit with proper error message if enterprise key is invalid #36351

xoxys opened this issue Oct 30, 2019 · 3 comments · Fixed by #36399

Comments

@xoxys
Copy link
Contributor

xoxys commented Oct 30, 2019

Steps to reproduce

  1. Disable an enterprise app
  2. Set an invalid Enterprise Key
  3. Try to enable an enterprise app

Expected behaviour

The occ app:enable example-ee-app command should exit with a proper error message and notify the user that the app will not be enabled due to an invalid license key.

Actual behaviour

The occ app:enable example-ee-app command exited with a success message while the app is still disabled. Only if you look into the owncloud.log you will see an error message about the invalid license key.

Server configuration

Operating system: Ubuntu 18.04

Web server: Apache

Database: MySQL

PHP version: 7.2

ownCloud version: 10.3

@pako81
Copy link

pako81 commented Nov 11, 2019

Proposed fix in #36399

@stale
Copy link

stale bot commented Sep 19, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/STALE label Sep 19, 2021
@stale
Copy link

stale bot commented Sep 20, 2021

This issue has been automatically closed.

@stale stale bot closed this as completed Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants