Project

General

Profile

Actions

Feature #20214

closed

Feature #19592: Groups Page Re-Design

Move group "Manage > Social Media Accounts" settings to group "Manage > Details" page

Added by Raymond Hoh 3 months ago. Updated about 1 month ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
Groups (misc)
Target version:
Start date:
2024-04-19
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

As per the group redesign mockups, the group "Manage > Social Media Accounts" page is going to merge into the group "Manage > Details" page.

The settings from the "Manage > Social Media Accounts" page belong to the `bp-groups-social-media` plugin created by Dan awhile ago. The mockups call for a simpler interface compared to the current Social Media Accounts admin UI.

Boone, I'm tentatively assigning this to you, but feel free to assign it back to me if you have other things to work on.


Files

Groups - Manage - Details.png (672 KB) Groups - Manage - Details.png Raymond Hoh, 2024-04-19 01:43 PM
Actions #1

Updated by Boone Gorges 3 months ago

  • Status changed from New to Testing Required

Thanks for the ping on this, Ray. A first implementation is in https://github.com/cuny-academic-commons/cac/commit/e44fa1b7376fc2eacde43d37c09d222050109cd7 and is ready for testing on cdev.

I decided to eliminate the bp-groups-social-media plugin altogether. (it's still in the codebase for reference until this ticket is resolved.) The new plugin supports the old data format, which allowed you to enter URLs or usernames, depending on the service. But there's some JS in the new editing interface that encourages the use of full URLs. So if you enter 'boone' into the Twitter field, on blur it'll validate and swap out with https://twitter.com/boone.

Actions #2

Updated by Colin McDonald about 1 month ago

At the risk of getting too into the weeds on URL validation, which I'm sure is complex, I noticed a couple of things while testing these settings for the new Group design:

- Is the X (Twitter) field set to recognize twitter.com links but not x.com links? I can't get the latter to register.

- If entering a full link, rather than the username only as Boone mentions above, does it only register if you add the https prefix? Should it recognize if I write x.com/boone, for example? Or is that even possible?

Actions #3

Updated by Boone Gorges about 1 month ago

My initial implementation wasn't set up to recognize x.com or URLs without the https:// protocol. I've made a change in https://github.com/cuny-academic-commons/cac/commit/2b67696d50da31c7efa535e7799e7da78a702f5a that should accommodate both.

Actions #4

Updated by Colin McDonald about 1 month ago

Thanks, Boone! Both are working for me now.

Actions #5

Updated by Boone Gorges about 1 month ago

  • Status changed from Testing Required to Resolved
Actions

Also available in: Atom PDF