Bug #5878
closed
Group Blog creation improvements
Added by Matt Gold over 8 years ago.
Updated over 8 years ago.
Category name:
Group Blogs
Description
if you create a blog and then try to attach it to a group during the group creation process, at the point when you are trying to connect the blog to the group, the following issues occur:
-- the list of sites is ordered in order of creation, with most recently created at the bottom; I'd suggest that it be ordered alpha by name or, if ordered in order of creation, with most recent at the top
-- the option to create a new blog was selected automagically, rather than choosing an existing blog. I'm not sure whether that is the right choice, but I'm also not sure how to assess that.
Files
Also -- even if you choose to select an already created site, the system acts as if your privacy levels haven't yet been set -- please see the attached screenshot
- Status changed from Assigned to Testing Required
- Target version set to 1.10
I made the following changes:
a. Blogs are now listed alphabetically in dropdown https://github.com/cuny-academic-commons/cac/commit/5e9edefb9238e08c46566fd77d8926cf1c682bd9
b. Site Privacy is now linked to the top section in the following ways:
- If you choose to create a new site, the suggested privacy level is whatever it previously was (private for private groups, etc)
- If you choose an existing site, the suggested privacy level is set to the actual privacy level of the existing site, the Site Privacy radio buttons are disabled, and the gloss changes to a message about how the privacy levels are controlled on the site.
https://github.com/cuny-academic-commons/cac/commit/3351e4ce53a56dc3fef2d9c0947d5b1692486c27
https://github.com/cuny-academic-commons/cac/commit/73e6d84428c3d4b2cb04bbf853db337636c02cf5
This can be tested on the new cdev (146.96.128.253 mapped to commons.gc.cuny.edu in your hosts file).
-- the option to create a new blog was selected automagically, rather than choosing an existing blog. I'm not sure whether that is the right choice, but I'm also not sure how to assess that.
IMO, the only good reason for changing this would be if we thought users were more likely to have created a site before deciding to link it to a group. My guess is that most users are not in this position; it's only our power users (eg you) who are likely to have one or more non-affiliated sites available for linking to groups. So I suggest leaving it.
Great. I don't have the bandwidth to test, but if you think this is working well, I think we can move forward.
- Status changed from Testing Required to Resolved
Also available in: Atom
PDF