Ticket #431 (closed enhancement: wontfix)
Webmaster can't edit/change/view widgets
| Reported by: | ed | Owned by: | ed |
|---|---|---|---|
| Priority: | major | Milestone: | PSE |
| Component: | Drupal modules & settings | Keywords: | |
| Cc: | Estimated Number of Hours: | 0.0 | |
| Add Hours to Ticket: | 0 | Billable?: | yes |
| Total Hours: | 0 |
Description (last modified by ed) (diff)
TI webmaster can create one/multiple widgets, but not then view/edit them.
TI web masters need to be able to see the widget they've got on their sites and change it if necessary.
ie - they go to a page with a list of their widgets
Change History
comment:2 Changed 4 years ago by ed
- Status changed from closed to reopened
- Resolution wontfix deleted
hmm OK. We are still tracking the widgets, though, as per this ticket yes? https://tech.transitionnetwork.org/trac/ticket/382
comment:3 Changed 4 years ago by jim
If Piwik has been set up, then we'll see activity on TN relating to PSE stuff -- i.e. all things related to viewing/editing via the widget at tn.org/pse/*.
BUT we can't track installations without extra work because the standard html/js model does not allow things inside iFrames to access outside, or vice versa.
Any code we add to the widget wrapper (the bit people paste into their web pages) will slow the widget down, and make people ansi about using it as we'll effectively be tracking ALL views of a page containing the widget -- this is not what we want.
So there's tracking, and there's tracking EVERYTHING. We will face security/trust issues to go outside 'our area', or extra development to get the widget to phone home.
Not though, that every widget display (view) has the user ID and node id of the initiative in the url, e.g. http://www.transitionnetwork.org/pse/view/sidebar/1/10006 so we can see what widgets for what initiatives are most popular.
Is this all ok? I think we have what we can safely have, any more will be tricky.
comment:4 Changed 4 years ago by jim
- Owner changed from jim to ed
- Status changed from reopened to assigned
And to be clear: by "we can't track installations" I mean, we can't see what page/site a widget was hosted on, only that it was requested for a given set of user/ini IDs.
comment:5 Changed 4 years ago by ed
- Status changed from assigned to closed
- Resolution set to wontfix
- Description modified (diff)
closing as this is in parallel to #382...
as long as we can see the following
- how many widgets are in action
- traffic generated by widdgets
- number of projects generated from widgets
Not trying to be negative, but this is outside the scope of the original spec isn't it? We never had a 'my widgets' page, and how can we since the code is cut/pasted into a site -- there's no extra admin/tracking here that lets a widget 'phone home'.
There is no facility or allowance for this, and will require significant alterations to logic to enable it... In fact I can't even think of a good way to do this.
Marking as 'not for Alpha' and letting Ed think and us chat as needs be.