Manage Request Subscribers #39

New Issue

2020-08-09T12:40:08Z

MrLyallCSIT commented

2020-08-09 12:40:08 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.
Add a manage request subscribers button to the view, update and upload pages.

Describe the solution you'd like
Button to create a similar view to below but instead of view, it gives the option to delete and edit.

Ability to add subscribers too using a form method. similar to the one in new shown below.

Subscribers list should also store name (e.g. stored in array format: Alex,alex@example.com],[Luke,luke@example.com as some users may want those with a non-definitive email as a subscriber (e.g. funkymonkeyjd@example.com could be James Dean)

**Is your feature request related to a problem? Please describe.** Add a manage request subscribers button to the view, update and upload pages. **Describe the solution you'd like** Button to create a similar view to below but instead of view, it gives the option to delete and edit. ![image](https://user-images.githubusercontent.com/9097891/89732275-780df280-da45-11ea-92bf-dba4bb35d33e.png) Ability to add subscribers too using a form method. similar to the one in new shown below. ![image](https://user-images.githubusercontent.com/9097891/89732283-8a882c00-da45-11ea-998d-d86bfdb9a7c4.png) Subscribers list should also store name (e.g. stored in array format: [[Alex,alex@example.com],[Luke,luke@example.com]] as some users may want those with a non-definitive email as a subscriber (e.g. funkymonkeyjd@example.com could be James Dean)

luketainton commented

2020-08-09 12:44:46 +00:00

(Migrated from github.com)

By "non-definitive email", do you mean users that don't exist in the app? Because for now there's no email function so this would be pointless until we implement that.

I think as a starter we should focus on managing subscribers based only on existing users, and go from there. Only because if an existing user's email changes, and we use their UUID to store their subscriptions, the email will change automatically.

By "non-definitive email", do you mean users that don't exist in the app? Because for now there's no email function so this would be pointless until we implement that. I think as a starter we should focus on managing subscribers based only on existing users, and go from there. Only because if an existing user's email changes, and we use their UUID to store their subscriptions, the email will change automatically.

MrLyallCSIT commented

2020-08-09 19:13:33 +00:00

(Migrated from github.com)

By "non-definitive email", do you mean users that don't exist in the app? Because for now there's no email function so this would be pointless until we implement that.

I think as a starter we should focus on managing subscribers based only on existing users, and go from there. Only because if an existing user's email changes, and we use their UUID to store their subscriptions, the email will change automatically.

non-definitive email in reference to emails that do not obviously declare the users name. such as fortnielol@example.com etc.

> By "non-definitive email", do you mean users that don't exist in the app? Because for now there's no email function so this would be pointless until we implement that. > > I think as a starter we should focus on managing subscribers based only on existing users, and go from there. Only because if an existing user's email changes, and we use their UUID to store their subscriptions, the email will change automatically. non-definitive email in reference to emails that do not obviously declare the users name. such as fortnielol@example.com etc.

github-actions[bot] commented

2020-08-10 13:37:33 +00:00

(Migrated from github.com)

Branch feature/39 created!

Branch [feature/39](https://github.com/luketainton/FHeD/tree/feature/39) created!

MrLyallCSIT commented

2020-08-10 14:38:23 +00:00

(Migrated from github.com)

What needs to be done @luketainton

we need a function for $subscribers in managesub which pulls all the subscribers from the DB
the edit and delete button on lines 140 and 141 need to go to the right places
line 124 in managesub needs a + button on the end that directs to addsub.php
addsub.php needs to be created from a duplicate of editsub.php
addsub and editsub need the correct insert and update commands adding to them

What needs to be done @luketainton - [ ] we need a function for $subscribers in managesub which pulls all the subscribers from the DB - [ ] the edit and delete button on lines 140 and 141 need to go to the right places - [ ] line 124 in managesub needs a + button on the end that directs to addsub.php - [ ] addsub.php needs to be created from a duplicate of editsub.php - [ ] addsub and editsub need the correct insert and update commands adding to them

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: archives/FHeD#39