Project

General

Profile

Actions

Feature proposal #5242

closed

Implement follow buttons

Added by krileon almost 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
20 April 2015
Due date:
% Done:

100%

Estimated time:

Description

Implement the ability to follow another asset. This should result in my activity outputs also including any asset that's being followed. The base for this stream api should be the tags class. There should only need to be 2 endpoints. 1 for displaying the button (which also includes the ajax) and 1 for saving the stream. When creating a follow stream the asset supplied is the asset to be followed.

For the button display endpoint it's probably best to reserve show/default for an actual view (e.g. if in the future there's a view to display all the assets the user is following) so use ->follow( 'button' ) instead.

Actions #1

Updated by krileon about 7 years ago

REMOVED

Actions #2

Updated by krileon about 7 years ago

REMOVED

Actions #3

Updated by krileon about 7 years ago

  • Subject changed from Implement like and follow fields to Implement follow buttons
  • Description updated (diff)
Actions #4

Updated by krileon about 7 years ago

  • Description updated (diff)
Actions #5

Updated by krileon about 7 years ago

  • % Done changed from 0 to 30
Actions #6

Updated by krileon about 7 years ago

  • % Done changed from 30 to 50
Actions #7

Updated by krileon about 7 years ago

  • % Done changed from 50 to 70
Actions #8

Updated by krileon about 7 years ago

  • % Done changed from 70 to 90

Just needs its jQuery. Button display, follow, and unfollow endpoints all functional.

Actions #9

Updated by krileon about 7 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 90 to 100
Actions #10

Updated by krileon about 7 years ago

  • Status changed from Resolved to Assigned
  • % Done changed from 100 to 90

Implement a content bot and module usage as well.

Actions #11

Updated by krileon about 7 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 90 to 100
Actions #12

Updated by krileon about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF