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

[bug -- or feature?] After creation of a same shortcut in "o" namespace but shortcut type II: "Access denied" #163

Closed
Wikinaut opened this issue Jan 27, 2016 · 1 comment

Comments

@Wikinaut
Copy link

I added "somafm" to "o" namespace (works), after it was auto-accepted apparently.

Then I cloned "somafm" (shortcut type I) to "somafm channel" (shortcut type II) and expected this also becoming auto-accepted. This was not the case, and the second form currently throws "Access denied" when I try to use it.

(You already described this effect elsewhere, but now I was able to reproduce it - documented above).

@Wikinaut Wikinaut changed the title After creation of a second shortcut: "Access denied" After creation of a same shortcut in "o" namespace but shortcut type II: "Access denied" Jan 27, 2016
@Wikinaut Wikinaut changed the title After creation of a same shortcut in "o" namespace but shortcut type II: "Access denied" [bug -- or feature?] After creation of a same shortcut in "o" namespace but shortcut type II: "Access denied" Jan 27, 2016
@georgjaehnig
Copy link
Owner

In successor www.trovu.net, editing happens now outside the UI in YAML files. So this became obsolete, closing.

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

2 participants