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

Usability: More graceful handling of non-configured cloud services #9

Open
agwells opened this issue Jun 15, 2016 · 0 comments
Open

Comments

@agwells
Copy link
Contributor

agwells commented Jun 15, 2016

If you install this artefact and the blocktypes, and then go to the new "Content -> Cloud" page without configuring an API key for each of them, you see all the blocktypes but you also see an error message for each one of them that says something about the key not being found.

You can workaround this by disabling the blocktypes you're not going to use. But it would be more friendly if the page just silently hid the cloud services that aren't properly configured.

Likewise, it'd be good if each of the blocktypes could detect that it's lacking an API key, and hide itself from the blocktype list if so.

@agwells agwells changed the title More graceful handling of non-configured cloud services Usability: More graceful handling of non-configured cloud services Jun 15, 2016
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

2 participants