Skip to content

Support setting default blog visibility on instance - #148

Merged
thebaer merged 5 commits into
developfrom
default-visibility
Aug 7, 2019
Merged

Support setting default blog visibility on instance#148
thebaer merged 5 commits into
developfrom
default-visibility

Conversation

@thebaer

@thebaer thebaer commented Aug 1, 2019

Copy link
Copy Markdown
Member

This adds a new default_visibility config value that lets an instance admin set the visibility of newly created collections: Unlisted (current default), Public, or Private.

This can also be set via the Admin UI.

Resolves T675.

thebaer added 2 commits July 31, 2019 22:18
This adds a new `default_visibility` config value that lets an instance
admin set the visibility of newly created collections.

Ref T675
@thebaer thebaer added this to the 0.11 milestone Aug 1, 2019
@thebaer thebaer changed the title Default visibility Support setting default blog visibility on instance Aug 1, 2019
@thebaer

thebaer commented Aug 6, 2019

Copy link
Copy Markdown
Member Author

Need to verify that creating a collection via API still works, then we can merge.

thebaer added 3 commits August 7, 2019 16:19
instead of updating it later. This is more correct behavior, prevents an
additional query, and ensures that potential collection-creation when
claiming posts also respects the default (which it didn't before).

Ref T675
(in returned JSON data)

Ref T675
@thebaer

thebaer commented Aug 7, 2019

Copy link
Copy Markdown
Member Author

Verified collection creation via API works, refactored some things, and added documentation. Merging now.

@thebaer
thebaer merged commit adfcc82 into develop Aug 7, 2019
@thebaer
thebaer deleted the default-visibility branch September 23, 2019 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant