Gist visibility update?

yaegashi's Avatar

yaegashi

30 Aug, 2016 06:01 PM

When I edit an existing public gist entry, it always turns into a private gist without any indications. And there seems no way to change the visibility of gists from private to public. Is this an intended behavior?

Confirmed with my own RhodeCode CE 4.3.1 installation and https://code.rhodecode.com.

How to reproduce:

  1. Sign in to https://code.rhodecode.com/.
  2. Open https://code.rhodecode.com/_admin/gists/new.
  3. Fill anything in the body and push "Create Public Gist" button.
  4. Push "Edit" button.
  5. Push "Update Gist" button.

Expected result:

  • The gist entry should remain public.

Actual result:

  • The gist entry turns into "Private Gist".
  1. Support Staff 1 Posted by Marcin Kuzminsk... on 26 Sep, 2016 10:42 AM

    Marcin Kuzminski's Avatar

    Hi !

    Thanks for reporting this, we will fix this ASAP, and produce a bugfix release in next 1-2 days.

  2. Support Staff 2 Posted by Marcin Kuzminsk... on 26 Sep, 2016 10:45 AM

    Marcin Kuzminski's Avatar

    Ticket was backported to issue tracker: https://issues.rhodecode.com/issues/4243 on 2016-09-26T10:47:50Z

  3. Support Staff 3 Posted by Marcin Kuzminsk... on 27 Sep, 2016 05:15 PM

    Marcin Kuzminski's Avatar

    This has been fixed in release 4.4.1

  4. Marcin Kuzminski closed this discussion on 27 Sep, 2016 05:15 PM.

  5. yaegashi re-opened this discussion on 30 Sep, 2016 03:07 AM

  6. 4 Posted by yaegashi on 30 Sep, 2016 03:07 AM

    yaegashi's Avatar

    Hi, thanks for the fix! I've confirmed the issue got handled in 4.4.1.

    I also wanted to confirm some details of RhodeCode Gists... are my assumptions in the following correct and intended?

    • Users cannot change the visibility (public / private) of existing gists
    • Users cannot specify arbitrary gist id on public gists (only sequencial numbers are allowed)
    • Users cannot change that arbitrary gist id of existing gists

    Actually any of them are not a big problem and OK to me, but it would be nice to have it explained in the documentation.

  7. yaegashi closed this discussion on 30 Sep, 2016 03:08 AM.

  8. Marcin Kuzminski re-opened this discussion on 30 Sep, 2016 09:38 AM

  9. Support Staff 5 Posted by Marcin Kuzminsk... on 30 Sep, 2016 09:38 AM

    Marcin Kuzminski's Avatar

    Hi, yes all your assumptions are correct. We'll try to indicate this in docs, however you're welcom to contribute to our documentation as well :)

    Cheers

  10. 6 Posted by yaegashi on 04 Oct, 2016 06:45 AM

    yaegashi's Avatar

    Thanks again for the clarification. Now this question could be closed satisfactorily.

    Hope my English becomes good enough to contribute to docs some day, but for now I'd rather make the effort on Japanese translations to support our local use of RhodeCode in the team. I've joined transifex.com and been working for these days, looking forward to seeing new translations reviewed and merged into the mainline.

  11. Support Staff 7 Posted by Marcin Kuzminsk... on 19 Dec, 2016 11:17 AM

    Marcin Kuzminski's Avatar

    In order to keep our support system clean and improve our response time to the open tickets, I will now close this support ticket. Of course, if you still have questions regarding this issue you may reopen this ticket at your convenience.

  12. Marcin Kuzminski closed this discussion on 19 Dec, 2016 11:17 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac