We have moved to Github. Please open tickets there.

Opened 2 years ago

Closed 2 years ago

#2722 closed Enhancement (fixed)

Re-implement Group support for Blogs

Reported by: jtilson Owned by: jtilson@…
Priority: normal Milestone: Elgg 1.8.0
Component: Blog Version: Github Master
Severity: minor Keywords:
Cc: brett@… Difficulty: easy

Description

This was stripped out in the current SVN version of the blogs plugin. Just need to add it back in.

Change History (5)

comment:1 Changed 2 years ago by cash

  • Difficulty set to easy
  • Milestone changed from Needs Review to Elgg 1.8

I agree that this needs to be done. I've been discussing a better way to handle routing with Brett and Evan. That influences the routing portion of the page handler. Basically, should the url be like it is in 1.7: pg/blog/owner/group:<guid> (which is an invalid url) or can we do something like pg/blog/group/owner/<guid>

comment:2 Changed 2 years ago by jtilson

It looks like in the trunk code there's a forwarder function that converts the old style, pg/blog/group:xx into pg/blog/owner/xx

Do we really need to add 'group' into the url? Whether its a group vs. a user doesn't make alot of different in displaying list of items, does it? Most of the group enabled plugins I've coded just handled the difference when needing to display a different header or different set of breadcrumbs, but I'm hardly the authority on page handlers!

I do think though, that there is a need for some consistent way of handling this stuff.

comment:3 Changed 2 years ago by cash

  1. We want to create a consistent scheme for urls across the core plugins.
  1. We need to decide how we want to handle group urls for the core plugins. Current candidates:
    • pg/blog/group/owner/<guid>
    • pg/blog/owner/group:<guid>
    • pg/blog/owner/<guid> (requires user's blogs to use guid rather than username)

The key issue is that users tend to be identified by username in URLs and groups by GUIDs. We either need to add 'group' somewhere in the URL to identify it as such or change over to using GUIDs. Users do not like seeing pg/blog/owner/5758475854

comment:4 Changed 2 years ago by jtilson

Gotcha Cash.. I was thinking a little 2D there. I definitely agree that users don't want to see their guids slapped across every URL. With that argument, and the fact that group:guid makes for an invalid URL the, only option is to use pg/blog/group/owner/guid out of those candidates.

That would definitely shake up the current page handler. It's expecting an action (or friends), then username.

comment:5 Changed 2 years ago by cash

  • Resolution set to fixed
  • Status changed from new to closed

redid the page handler for blogs and added group blogs back in

Note: See TracTickets for help on using tickets.