Project

General

Profile

Actions

Feature #8835

open

Extend cuny.is shortlinks to sites

Added by Luke Waltzer about 5 years ago. Updated 7 months ago.

Status:
New
Priority name:
Normal
Assignee:
Category name:
Blogs (BuddyPress)
Target version:
Start date:
2017-10-20
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

opening ticket to begin discussion of extending automatic cuny.is shortlinks to sites...


Related issues

Related to CUNY Academic Commons - Feature #8836: Redesign site launch processAssignedBoone Gorges2017-10-20

Actions
Related to CUNY Academic Commons - Feature #6241: cuny.is short URLs for groupsResolvedBoone Gorges2016-10-13

Actions
Actions #1

Updated by Boone Gorges about 5 years ago

  • Category name set to Blogs (BuddyPress)
  • Target version set to 1.14

Let's see if we can shoehorn this into a broader discussion of site creation.

Actions #2

Updated by Boone Gorges about 5 years ago

Actions #3

Updated by Boone Gorges about 4 years ago

  • Target version changed from 1.14 to 1.15
Actions #4

Updated by Boone Gorges over 3 years ago

Actions #5

Updated by Boone Gorges over 3 years ago

  • Target version changed from 1.15 to 1.16

Let's look at this for the fall. There are a few high-level questions that'll need addressing before we can implement. (See previously #6241.)

- What's the format for site shortlinks? In the case of groups, we use 'group-{groupname}' - eg, 'group-cunypie' for commons.gc.cuny.edu/groups/cunypie. Do we do something similar for sites? 'site-cunypie' etc.
- Related, how do we deal with the relationship between group-connected sites and their connected groups? If we prefix the default values, there should be no conflicts. But what if you create the shortlink 'cunypie' for your group, but later set up a connected site and want to shift the shortlink to the group? The uniqueness checks currently in place would forbid this.

Actions #6

Updated by Boone Gorges about 3 years ago

  • Assignee set to Boone Gorges
  • Target version changed from 1.16 to 1.17.0
Actions #7

Updated by Boone Gorges over 2 years ago

  • Target version changed from 1.17.0 to 1.18.0
Actions #8

Updated by Matt Gold over 2 years ago

Hi Colin -- I want to put this on your radar for a possible Fall release dev item

Actions #9

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.18.0 to 1.19.0
Actions #10

Updated by Boone Gorges about 1 year ago

  • Target version changed from 1.19.0 to 2.0.0
Actions #11

Updated by Boone Gorges 7 months ago

  • Target version changed from 2.0.0 to Future release
Actions

Also available in: Atom PDF