You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
agwells
changed the title
More graceful handling of non-configured cloud services
Usability: More graceful handling of non-configured cloud services
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.
The text was updated successfully, but these errors were encountered: