Last modified: 2013-02-04 21:45:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45142, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43142 - Add a 'make_a_tour' tour that "Launch a Tour on using Tours" points to
Add a 'make_a_tour' tour that "Launch a Tour on using Tours" points to
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
GuidedTour (Other open bugs)
master
All All
: High normal (vote)
: ---
Assigned To: Matthew Flaschen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-14 22:41 UTC by Matthew Flaschen
Modified: 2013-02-04 21:45 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Matthew Flaschen 2012-12-14 22:41:07 UTC
At the end of the test.js tour, there is a "Launch a Tour on using Tours" button, but it fails silently.
Comment 1 Steven Walling 2012-12-14 22:43:16 UTC
I believe this is because it's simply not defined on the test wiki, piramido.wmflabs.org?
Comment 2 Matthew Flaschen 2012-12-14 22:45:32 UTC
It's also not in master.  I'm going to file a separate bug about the need to copy the starter tours manually to MediaWiki.
Comment 3 Luke Welling 2012-12-17 15:32:48 UTC
There are a few separate issues here.

Every time guided tour fails, it does it silently for the user, but logs for various anticipated failure types (including this one).  That seems reasonable to me, but it could fling alerts about if louder javascript error handling is the norm.

The failure is because there is not a second tour defined for it to link to.  I'd rather not solve it by deleting the linking button as that sample tour is essentially the documentation on how to write tours, so the features it shows off are the ones people will likely copy to their own real tours.

A better fix for this bug would be to write a second tour for it to link to.

IMHO the code is fine in this instance, the problem is a content shortage.
Comment 4 Luke Welling 2012-12-17 15:40:02 UTC
There is a second tour here about the gadget version: 
https://github.com/tychay/mwgadget.GuidedTour/blob/master/tours/guidedtour.js

But it is short and does not really apply to the extension version, so may not be a useful starting point.
Comment 5 Steven Walling 2012-12-17 18:47:15 UTC
We should either edit the test tour to remove mention of the second test tour, or simply add it as well. I'm fine with either. The exact content of the examples doesn't really matter, as long as it accurately reflects the technical capabilities of the extension.
Comment 6 Matthew Flaschen 2012-12-17 22:25:37 UTC
Luke is right.  The 'silently' is not the issue.  It is using the best-practice mw.log, which means I should have run it in debug mode to see the issues.

I'll make a 'makeatour' tour for this.
Comment 7 Steven Walling 2013-02-04 21:12:15 UTC
Seems like we've decided to abandon this idea? 

http://lists.wikimedia.org/pipermail/ee/2013-February/000133.html
Comment 8 Matthew Flaschen 2013-02-04 21:45:00 UTC
Yes, at least for now.  As a note, the gadget guidedtour (https://github.com/tychay/mwgadget.GuidedTour/blob/master/tours/guidedtour.js) was really a guide to using tours, not to developing them.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links