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

Deleted channels appear in storage request form #1269

Closed
intelliant01 opened this issue Mar 7, 2019 · 2 comments
Closed

Deleted channels appear in storage request form #1269

intelliant01 opened this issue Mar 7, 2019 · 2 comments

Comments

@intelliant01
Copy link

Summary

Have deleted a few of the channels from My Channels but they still appear in the storage request form in the probables for making Public

Category

BUG

Usage Details

Please give details about how you were using Studio.

  • Browser: Any
  • Channel: A few deleted channels (See below)

Traceback or relevant snippet from browser console

A few deleted channels -

<option value="9729640dc9d25b1da18d07343416f9bd">Sample JSON channel</option>
<option value="6859c5e9896d4a7ab6b534d130de0a83">Kiddie Stories</option>
<option value="c401c87e3cf652128fd3efaa5b3774f2">Sample Ricecooker Channel</option>

How to reproduce

  1. Curate a channel and publish it
  2. Delete the channel
  3. Check in user profile Settings - Storage - Request more space form - Who can use your content? section's public probables multi-select box.
  4. The deleted channel is still visible

Screenshots

All but Gujarati Stories of the channels shown in this screenshot have been deleted -

image

Real-life consequences (anything community should be aware of, for instance how it affects end users)

Confusion, suspecting if the channels have indeed been deleted or not. May be space is also not being freed up.

A similar issue related to deleted channel still being accessible had been addressed in #501

@jayoshih
Copy link
Contributor

jayoshih commented Mar 8, 2019

Hello @intelliant01,

Thank you for submitting this issue! I have submitted a fix for this, which should be in the next release.

Thank you for your patience!

@jayoshih
Copy link
Contributor

Pushed the fix to production

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

No branches or pull requests

3 participants