Transition Technology: Ticket #508: Step by step process to convert web point of contact to widget owner

jim — Sun, 10 Mar 2013 19:26:43 GMT

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:

Same
Same
Same -- EXCEPT the button is 'Get the widget' (because users don't care about permissions).
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...
User submits above form, gets their role to 'widget owner', page reloads and they're on the Get Widget page.
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 — Sun, 10 Mar 2013 19:48:21 GMT

great

jim — Sun, 10 Mar 2013 21:51:01 GMT

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...

owner, priority, status changed

jim — Sun, 10 Mar 2013 23:09:07 GMT

owner changed from jim to ed
priority changed from critical to major
status changed from new to assigned

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.

cc set

jim — Sun, 10 Mar 2013 23:09:28 GMT

cc ed, jim added

Ensuring we're in the loop...

ed — Mon, 11 Mar 2013 08:16:48 GMT

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

status changed; resolution set

jim — Tue, 12 Mar 2013 10:09:59 GMT

status changed from assigned to closed
resolution set to fixed

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

status changed; resolution deleted

ed — Tue, 12 Mar 2013 10:18:32 GMT

status changed from closed to reopened
resolution fixed deleted

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.

status changed; resolution set

jim — Tue, 12 Mar 2013 12:36:44 GMT

status changed from reopened to closed
resolution set to fixed

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 — Wed, 13 Mar 2013 10:28:21 GMT

Great - Ed to test.

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

ed — Wed, 13 Mar 2013 10:50:08 GMT

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

jim — Wed, 13 Mar 2013 21:15:02 GMT

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.