Step by step process to convert web point of contact to widget owner

[ed]

We want this to work for the beta testers and every web point of contact going forward. Then we can assume it will work for anyone who is a web point of contact. In fact, once we have done this, the nag block described below will be there forever (until Ed removes it if they project doesn't work out).

RULE: Widget owners need to be the web points of contact for Transition Initiative Profiles on TN.org.

STEPS:

1. user receive an email with a link to login
2. user login and go to their user account page
3. user sees a block and clicks on the button in a nag block at the top of the right hand column like the 'add your project/initiative' block in other places: 'Want to add the projects widget to your website? <br> Click this button to set your permissions <button>' - !NB Ed needs to be able to edit this!
4. user goes to page with (1) pre-ticked widget owners mail chimp subscription and text 'please keep me up to date with changes to widget code and other related updates (no spam, we promise). Widget code will change so please don't opt out of this - we will need to update you' and (2) button for user to click to confirm that they want to be a widget owner which sets their role to 'widget owner' with the text 'Click this button to confirm that you want to be a widget owner. Agreeing to this means that you agree with the <link to T&Cs> Transition Network website terms and conditions</link to T&Cs>.'.
5. user goes to their user account page in the projects moderation tab - where they will see the 'not got a project widget yet? click to get one here…' link

[jim]

This is already under way... BUT not released right now -- soon.

I've;

• Created a function that allows us to check if any user is a Web PoC for an ini or hub ini.
• Created a block using the above function for display that Ed can edit
• Rebuilt the 'get the widget' page to allow a nicer workflow per 4) in description

Re 5: This is an extra step that's not needed -- we can have it in addition though.

The current workflow is easier than the description and goes like this:

1. Same
2. Same
3. Same -- EXCEPT the button is 'Get the widget' (because users don't care about permissions).
4. user goes to page "get the widget" page BUT no 'get' options present -- instead the form agree to the T&Cs with pre-ticked widget owners mail chimp subscription...
5. User submits above form, gets their role to 'widget owner', page reloads and they're on the Get Widget page.
6. Everything carries on...

Thus we avoid a horrible side-step back to the moderation page to hope a user spots the right text and clicks the link -- instead they just get 'get widget' -> 'agree/sign up' -> 'get the code'.

Working on last bits now and will upload tonight, then we'll be on to the last bits of the testing/access/perms tweaks per 41 & 48 on the spreadsheet.

[ed]

great

[jim]

OK this is now up... Still making a few tweaks and looking at the perms issues.

FYI: Users who go to the 'Get Widget' page WITHOUT being a Web POC get the following message:

---

Get the Projects Widget!

---

Sorry, you must be the Web Point of Contact for your initiative to continue

Unfortunately, you cannot use the widget until you have been set up as the "Web Point of Contact" for your local initiative.

Please find your initiative in the Initiatives Directory and either edit it (if you have that ability), or contact the person who is marked as the "Primary point of contact".

Remember to come back here when you're done, and please contact us if you have any questions or problems.

---

ED: Any changes? Once they are a web poc, they don't see this. But then they'd never get to the page without knowings its address because the block from 3) won't show.

Development now mostly done!!! WOOO! Now, on to the perms bits, then some bug fixes...

[jim]

This is now done, and all working !!!EXCEPT!!! the bloody Mail Chimp integration... Works on mine but not on Prod. New ticket open to track that here: #512

Reassigning to Ed for comment/text changes pending his close.

[jim]

Ensuring we're in the loop...

[ed]

Text for project moderation page for users without widget owner role approved. Please enjoy the mailchimp works.

[jim]

OK, so this is done barring the #512 Mailchimp issue (which I'm doing today), so closing this bad boy.

[ed]

Nice try.

Q: nag button shows up on 'get' page - making it smaller and less useful. Can you not show on get page?

Close when mailchimp issue is done.

[jim]

Added some checks to not show 'get' block on admin pages or pse/widget pages...

And MC is hammered over at #512..

This is so fixed it hurts!

[ed]

Great - Ed to test.

Can I edit/admin this PSE 'get' block?

[ed]

ignore last comment - found it - saw the .php - assume it's a 'do NOT touch' kind of thing

[jim]

The content and title of the block can be edited safely, just stay away from the visibility settings at the foot where you saw the PHP. Note also the HTML in there that makes the button -- easier to see with the WYSIWYG off.