Extension talk:GuidedTour/Archive2/Flow export

There is one archived talk page.

This is a beautiful extension. Can you generate a list of guided tours in use on any of the current wikis? I came here after seeing the GettingStarted guided tour, but it's not clear from this page that GS is implemented using this extension. I also don't see a special page that lists all tours on a wiki; is there one? Thanks! Sj (talk) 17:05, 7 July 2013 (UTC) Reply

Even better would be a dashboard somewhere combining such lists of guided tours from all wikis, or we'll soon lose track of them (in the hope that usage will increase). Nemo 08:29, 8 July 2013 (UTC) Reply

There's not (yet) a special page or dashboard of this kind. I've tried to keep the wiki page here updated with the list of tours. For now, other than the wiki page here, you can also the list of tours packaged in the extension, by using our repository browser.

I'd be interested in hearing what Matt thinks, but IMO there probably aren't enough tours to justify building an automated dashboard with them. Also, since admins can enable any tour locally, such a dashboard might have to search through the entire MediaWiki namespace on all wikis to look for tours. Steven Walling (WMF) • talk 22:19, 9 July 2013 (UTC) Reply

Maybe this is a task to be done on Tools Labs? Helder 02:00, 11 July 2013 (UTC)

Not a bad idea. Steven Walling (WMF) • talk 21:15, 11 July 2013 (UTC) Reply

Tracked in Phabricator
Task T53419

I think it's a good idea. There are already eight on-wiki tours on English Wikipedia (plus a handful of extension-defined ones); most of the on-wiki ones are Wikipedia Adventure levels. It will take some work, but I can already see different possible approaches that should allow sufficient performance.

In the meantime, you can use this PrefixIndex search as a work-around to see the on-wiki ones. Only the ones ending in .js are actually tours. The others are messages for extension-defined tours. Superm401 - Talk 02:08, 16 July 2013 (UTC) Reply

I see you've left a note for the TWA developers, and they are planning on coordinating with the extension maintainers. I wonder if there are other community js projects that would benefit from the same introduction to the GT code? In the case of TWA in particular: there seem to be issues of implementation that many Tour creators will share: How often to page-refresh, where to show messages of different kinds, how to overlay messages on a background page with/without graying out the page.

The existence of this template for tours is something we can publicize more openly on the village pumps and cafes of big wikis, once there is at least one implementation there. For instance as part of any announcement of a new microsurvey. And the talk pages of the most popular guided tours should include a link to a tutorial on making your own tour :) Sj (talk) 17:08, 7 July 2013 (UTC) Reply

Yes, E3 (including me) has talked occasionally with User:Ocaasi (developer of Wikipedia Adventure). We've also kept people posted publicly, including on the EE mailing list, Wikipedia Village Pump (e.g. here), Wikinews, and Wikivoyage (original discussion, GuidedTour Tour Agency under discussion).

As far as documentation, we have Extension:GuidedTour/Write an on-wiki tour. It's a start, but there's definitely room for improvement, and we need to put some time into that. We are planning to do some refactoring of the extension soon, which may involve some changes to how tours are written (we'll help people make the needed adjustments). So there is nothing stopping people from writing tours right now, but it may not be the ideal time for a big push. Superm401 - Talk 01:52, 16 July 2013 (UTC) Reply

I've installed both EventLogging and GuidedTour but haven't been successful in viewing the test tour on my install (though I can view on other sites running GuidedTour, so I'm capable of typing it correctly).

My Special:Version page shows:

 EventLogging (Version 0.6) --- I did try 0.5, with no success, and moved up because I saw other wikis using 0.6	
 GuidedTour (Version 1)

I've disabled all other plugins and I'm running MediaWiki 1.21.2

My question is: how do I troubleshoot this? anyone have any problems getting this to work? any reasons why it wouldn't work on the first try? any way to figure out easily if EventLogging (rather than GuidedTour) is the issue?

thanks for your help! A.Sea.Arr (talk) 16:49, 6 September 2013 (UTC) Reply

Sorry for the delayed reply.

How did you install the two extensions? I recommend you install both from git (if you didn't before). The clone URLs are https://gerrit.wikimedia.org/r/p/mediawiki/extensions/EventLogging.git and https://gerrit.wikimedia.org/r/p/mediawiki/extensions/GuidedTour.git .

If you have an old version of GuidedTour, it may be that you didn't update the submodule (not an issue if you have the latest git).

If it still doesn't work, you can join our public IRC channel, #wikimedia-growth ^connect so we can troubleshoot. Superm401 - Talk 23:36, 16 September 2013 (UTC) Reply

A.Sea.Arr

Did you ever get your install of GuidedTour to work? I'm having the same issue, I successfully installed EventLogging and GuidedTour but I cannot view any tours on my page. Additionally, I can view tours on the test pages provided on the extension page. I'm hoping you found a solution that might also work for me. I have revisited this issue multiple times, get frustrated and leave it for another day.

Thanks. Clifford.kasper (talk) 20:40, 15 May 2014 (UTC) Reply

What version of MediaWiki are you using (you can check at Special:Version)? Also, did you install EventLogging and GuidedTour from git, or another source (e.g. a tarball)? Superm401 - Talk 01:29, 16 May 2014 (UTC) Reply

I am using MW 1.21.2.

I used the Download Snapshot link and selected the download for MW 1.21. I also tried the one for MW 1.22 but that did not work either. Do you think using the git source might work? Thanks. Clifford.kasper (talk) 14:57, 4 June 2014 (UTC) Reply

What errors do you get with the 1.21 versions of EventLogging and GuidedTour?

If you don't know where the error log is, you can try displaying errors temporarily. Superm401 - Talk 23:05, 4 September 2014 (UTC) Reply

Hello, Just I came across Extension:GuidedTour. Can we use for ULS support.Speccially I would be haapy I if we can provide a button when clicked directly Marathi language input method अक्षरांतरण will get activated.So I can provide such a button on some of help pages on Marathi wikpedia and other mr wiki projects.

Thanks and regards Mahitgar (talk) 11:45, 19 September 2013 (UTC) Reply

Pau and Siebrand, what say ye? Steven Walling (WMF) • talk 21:29, 20 September 2013 (UTC) Reply

I think it's a nice idea. Does this require WMF involvement, or is it something that could be accomplished in a community driven and supported way? siebrand (talk) 22:38, 23 September 2013 (UTC) Reply

If there's a JS-savvy person from the community willing to write a tour, there's nothing stopping them, though we'd need to deploy the extension to hiwiki or whichever other project was interested. Once it's there, local admins can write and enable tours in the MediaWiki namespace just like gadgets, and you can deliver a tour by just adding it to the end of a link. Steven Walling (WMF) • talk 21:15, 24 September 2013 (UTC) Reply

I'm eagerly awaiting what will happen, then :). Let me know if something is needed from me or the Language Engineering team. siebrand (talk) 19:42, 26 September 2013 (UTC) Reply

It seems like they're actually requesting a simple button that can be put in help text that will instantly enable Marathi. That said, it should be possible to write a tour for this (which I think would be useful). I think it will require the advanced tour support we're planning in order to do a complete tour. Superm401 - Talk 12:00, 27 September 2013 (UTC) Reply

something like gt.nextStep() would be helpful. And i18n for multilingual wikis like Commons is essential. This should be possible without having to copy&paste the whole logic or using crappy approaches like I did at commons:MediaWiki:Guidedtour-tour-nominatefordeletion.js Rillke (talk) 12:59, 11 October 2013 (UTC) Reply

You can use action: 'next' as you are, if you don't need to do anything else on the same button. If you do, you can use mw.libs.guiders.next(); in an onclick, and action: 'okay'.

As for i18n, GuidedTour supports it for extension-developed tours (you're leveraging that support in your workaround). I don't currently plan to implement custom support for i18n tours on-wiki. We looked at it when the extension started, but didn't see a clean way to do it. I think the best approach is to finish Gadgets 2.0 (yes, I know it's been delayed), rather than every extension doing this its own way.

The workaround you're using is okay. However, just for completeness you can alternatively use a separate i18n mechanism and pass regular strings instead of messages. See Extension:GuidedTour/Write an on-wiki_tour#Test tour code walkthrough; note description can be used instead of descriptionmsg, etc (same for the other ones ending in msg).

Thanks for using GuidedTour; let me know how I can help further. Superm401 - Talk 22:13, 11 October 2013 (UTC) Reply

Tried that but the following was sent to the server despite using &uselang=de in the address bar:

action	parse
format	json
page	Help:Nominate for deletion/gt/msg/welcome/description

Without the user's language choice is submitted as well to the API, the message is returned in English. This is not really an option as Commons offers its contents to anonymous users in their chosen language by using the uselang parameter.

commons:Help:Nominate for deletion/gt/msg/welcome/description, Special:Permalink/106939382.

I guess you look for the response of the function passed to onShow and evaluate if it is a Promise, and if it is the tour waits for the operation to succeed? Could I use this for completely custom i18n logic or do you intend making changes to that code part?

Image annotator, for example has put all its translation into a template. This would be the easiest option for translators currently (and it would not require admin actions for each changed translation). I am also using this for the watchlist notice and this also gives me a nice overview over translation work that was already done. I'll care for escaping and everything like that.

Thank you for the comprehensive reply. Rillke (talk) 23:03, 12 October 2013 (UTC) Reply

If I understand right, you were experimenting with gt.getPageAsDescription. You raise a good point. It should preserve the user's language when calling the API, and it does not. I've noted bugzilla:55664 for this.

The way this API-based parsing/onShow works is not as clean as it should be. It is using synchronous requests. However, I plan to change that (bugzilla:44925). When I fix bug 55664, that will give you a way to do proper translation of on-wiki parsing.

I may not keep onShow intact, but I will consider if I can provide a way to make tour definitions fully asynchronous. Superm401 - Talk 23:52, 12 October 2013 (UTC) Reply

Oops, I should have read your full message before going to Gerrit, sorry; yes, I was experimenting with gt.getPageAsDescription -- should have mentioned that but thought it was what you suggested this with Extension:GuidedTour/Write an on-wiki_tour#Test tour code walkthrough?

I didn't expect you using synchronous AJAX 😕 -- the promise-approach would be nice, I think. onShow is still useful, even after fixing bugzilla:44925, for example for playing sound. Btw, do you have some best-practices for playing audio files inside guided tour?

Additionally, I do believe GT would be more popular if there would be a creation wizard for a tour, including selecting elements where guiders will be attached to, ...

Finally it is worth mentioning that right/left (position) are automatically flipped for RTL languages, if it isn't already. Otherwise this could lead to confusion for native speakers or RTL-languages. Rillke (talk) 09:28, 13 October 2013 (UTC) Reply

I haven't tested your patch yet, but it looks solid. Yes, I did suggest gt.getPageAsDescription as one of the possibilities (note how different steps demo different approaches; I've just explained that a little better).

I don't have an approach for playing sound. I would be very cautious about that, particularly if it starts automatically. You could easily end up annoying the user.

I agree that a creation wizard would be nice (bugzilla:44597), but it is not a priority currently.

I've documented the RTL-flipping. Let me know if anything is still unclear. Superm401 - Talk 01:26, 14 October 2013 (UTC) Reply

Hi installed both EventLogging and GuidedTour, and get this error message after activating GuidedTour. Help is much appreciated.

MediaWiki internal error.
Original exception: exception 'MWException' with message 'Detected bug in an extension! Hook GuidedTourHooks::onResourceLoaderRegisterModules failed to return a value; should return true to continue hook processing or false to abort.' in /home1/[my website path]/includes/Hooks.php:284
Stack trace:
#0 /home1/[my website path]/includes/GlobalFunctions.php(3883): Hooks::run('ResourceLoaderR...', Array)
#1 /home1/[my website path]/includes/resourceloader/ResourceLoader.php(206): wfRunHooks('ResourceLoaderR...', Array)
#2 /home1/[my website path]/includes/OutputPage.php(2565): ResourceLoader->__construct()
#3 /home1/[my website path]/includes/OutputPage.php(448): OutputPage->getResourceLoader()
#4 /home1/[my website path]/includes/OutputPage.php(473): OutputPage->filterModules(Array, 'bottom')
#5 /home1/[my website path]/includes/OutputPage.php(545): OutputPage->getModules(true, 'bottom', 'mModuleMessages')
#6 /home1/[my website path]/includes/OutputPage.php(2818): OutputPage->getModuleMessages(true, 'bottom')
#7 /home1/[my website path]/includes/OutputPage.php(2931): OutputPage->getScriptsForBottomQueue(false)
#8 /home1/[my website path]/includes/Skin.php(583): OutputPage->getBottomScripts()
#9 /home1/[my website path]/includes/SkinTemplate.php(390): Skin->bottomScripts()
#10 /home1/[my website path]/includes/OutputPage.php(2034): SkinTemplate->outputPage()
#11 /home1/[my website path]/includes/Wiki.php(572): OutputPage->output()
#12 /home1/[my website path]/includes/Wiki.php(458): MediaWiki->main()
#13 /home1/[my website path]/index.php(59): MediaWiki->run()
#14 {main}
Exception caught inside exception handler: exception 'MWException' with message 'Detected bug in an extension! Hook GuidedTourHooks::onResourceLoaderRegisterModules failed to return a value; should return true to continue hook processing or false to abort.' in /home1/[my website path]/includes/Hooks.php:284
Stack trace:
#0 /home1/[my website path]/includes/GlobalFunctions.php(3883): Hooks::run('ResourceLoaderR...', Array)
#1 /home1/[my website path]/includes/resourceloader/ResourceLoader.php(206): wfRunHooks('ResourceLoaderR...', Array)
#2 /home1/[my website path]/includes/OutputPage.php(2565): ResourceLoader->__construct()
#3 /home1/[my website path]/includes/OutputPage.php(448): OutputPage->getResourceLoader()
#4 /home1/[my website path]/includes/OutputPage.php(473): OutputPage->filterModules(Array, 'bottom')
#5 /home1/[my website path]/includes/OutputPage.php(545): OutputPage->getModules(true, 'bottom', 'mModuleMessages')
#6 /home1/[my website path]/includes/OutputPage.php(2818): OutputPage->getModuleMessages(true, 'bottom')
#7 /home1/[my website path]/includes/OutputPage.php(2931): OutputPage->getScriptsForBottomQueue(false)
#8 /home1/[my website path]/includes/Skin.php(583): OutputPage->getBottomScripts()
#9 /home1/[my website path]/includes/SkinTemplate.php(390): Skin->bottomScripts()
#10 /home1/[my website path]/includes/OutputPage.php(2034): SkinTemplate->outputPage()
#11 /home1/[my website path]/includes/Exception.php(227): OutputPage->output()
#12 /home1/[my website path]/includes/Exception.php(272): MWException->reportHTML()
#13 /home1/[my website path]/includes/Exception.php(643): MWException->report()
#14 /home1/[my website path]/includes/Exception.php(713): MWExceptionHandler::report(Object(MWException))
#15 /home1/[my website path]/includes/Wiki.php(461): MWExceptionHandler::handle(Object(MWException))
#16 /home1/[my website path]/index.php(59): MediaWiki->run()
#17 {main} Felipe95a (talk) 00:51, 15 November 2013 (UTC) Reply  

Thanks for the report. Core changed a few months ago so that a return true was no longer required here. However, I'm glad to add it so it isn't an obstacle to supporting older versions of MediaWiki core. This is fixed in latest master, so you can just pull to update. Superm401 - Talk 22:53, 18 November 2013 (UTC) Reply

Hi installed both EventLogging and GuidedTour, and get this error message after activating GuidedTour. Can you help me, please?

Detected bug in an extension! Hook CanonicalNamespaces closure failed to return a value; should return true to continue hook processing or false to abort.
Backtrace:
#0 /var/www/[myfolder]/includes/GlobalFunctions.php(3883): Hooks::run('CanonicalNamesp...', Array)
#1 /var/www/[myfolder]/includes/Namespace.php(226): wfRunHooks('CanonicalNamesp...', Array)
#2 /var/www/[myfolder]/includes/Namespace.php(257): MWNamespace::getCanonicalNamespaces()
#3 /var/www/[myfolder]/languages/Language.php(705): MWNamespace::getCanonicalIndex('template')
#4 /var/www/[myfolder]/includes/Title.php(3136): Language->getNsIndex('Template')
#5 /var/www/[myfolder]/includes/Title.php(152): Title->secureAndSplit()
#6 /var/www/[myfolder]/extensions/DynamicPageList/DPLSetup.php(1232): Title::newFromText('Template:Extens...')
#7 /var/www/[myfolder]/extensions/DynamicPageList/DPLSetup.php(1211): ExtDynamicPageList::commonSetup()
#8 [internal function]: ExtDynamicPageList::setupDPL()
#9 /var/www/[myfolder]/includes/Setup.php(551): call_user_func(Array)
#10 /var/www/[myfolder]/includes/WebStart.php(161): require_once('/var/www/...')
#11 /var/www/[myfolder]/index.php(55): require('/var/www/...')
#12 {main}

If I deactivate the DynamicPageList extension I get the following error

Detected bug in an extension! Hook CanonicalNamespaces closure failed to return a value; should return true to continue hook processing or false to abort.
Backtrace:
#0 /var/www/[myfolder]/includes/GlobalFunctions.php(3883): Hooks::run('CanonicalNamesp...', Array)
#1 /var/www/[myfolder]/includes/Namespace.php(226): wfRunHooks('CanonicalNamesp...', Array)
#2 /var/www/[myfolder]/languages/Language.php(493): MWNamespace::getCanonicalNamespaces()
#3 /var/www/[myfolder]/includes/search/SearchEngine.php(349): Language->getNamespaces()
#4 /var/www/[myfolder]/includes/User.php(1241): SearchEngine::searchableNamespaces()
#5 /var/www/[myfolder]/includes/User.php(4334): User::getDefaultOptions()
#6 /var/www/[myfolder]/includes/User.php(348): User->loadOptions()
#7 /var/www/[myfolder]/includes/User.php(328): User->saveToCache()
#8 /var/www/[myfolder]/includes/User.php(286): User->loadFromId()
#9 /var/www/[myfolder]/includes/User.php(2073): User->load()
#10 /var/www/[myfolder]/includes/User.php(981): User->getToken(false)
#11 /var/www/[myfolder]/includes/User.php(289): User->loadFromSession()
#12 /var/www/[myfolder]/includes/User.php(4328): User->load()
#13 /var/www/[myfolder]/includes/User.php(2227): User->loadOptions()
#14 /var/www/[myfolder]/includes/context/RequestContext.php(296): User->getOption('language')
#15 /var/www/[myfolder]/includes/Message.php(360): RequestContext->getLanguage()
#16 /var/www/[myfolder]/includes/context/RequestContext.php(377): Message->setContext(Object(RequestContext))
#17 [internal function]: RequestContext->msg('pagetitle')
#18 /var/www/[myfolder]/includes/context/ContextSource.php(165): call_user_func_array(Array, Array)
#19 /var/www/[myfolder]/includes/OutputPage.php(878): ContextSource->msg('pagetitle')
#20 /var/www/[myfolder]/includes/Article.php(554): OutputPage->setPageTitle('Main Page')
#21 /var/www/[myfolder]/includes/actions/ViewAction.php(44): Article->view()
#22 /var/www/[myfolder]/includes/Wiki.php(439): ViewAction->show()
#23 /var/www/[myfolder]/includes/Wiki.php(305): MediaWiki->performAction(Object(Article), Object(Title))
#24 /var/www/[myfolder]/includes/Wiki.php(565): MediaWiki->performRequest()
#25 /var/www/[myfolder]/includes/Wiki.php(458): MediaWiki->main()
#26 /var/www/[myfolder]/index.php(59): MediaWiki->run()
#27 {main}

I hope you can help me, I love this extension! Thank you. Gborgonovo (talk) 18:55, 6 March 2014 (UTC) Reply

I don't know if it can be useful, but I have some custom namespaces: 100, 101, 110, 111, 500, 501, 510, 511.

And subpages activated. Gborgonovo (talk) 19:00, 6 March 2014 (UTC) Reply

I have the same problem with GuidedTour extension disabled, so maybe it is a problem with EventLogging extension. See my question there. Thank you. Gborgonovo (talk) 20:06, 6 March 2014 (UTC) Reply

Thanks for trying GuidedTour. This issue is not with GuidedTour. Rather, there is an incompatibility between your version of core and the version of EventLogging. See my reply on the EventLogging talk page. Superm401 - Talk 23:14, 10 March 2014 (UTC) Reply

Hi, I like this extensiona lot, but it seems I really cannot see it at work. I'm running a fresh installation on MediaWiki 1.23.3, PHP 5.3.10, MySQL 5.5.38. Guided tour and EventLogging are at their very last version cloned from git. When I call the tour simply nothing happens, no message is shown, neither with debug options (error_reporting, dislay_errors) activated.

I don't where to go for further investigation. Thank you for your help. Gborgonovo (talk) 16:59, 11 September 2014 (UTC) Reply

What URL are you using? Did you try http://localhost/w/index.php?tour=test (or your wiki's equivalent URL)? Mattflaschen-WMF (talk) 00:28, 12 July 2015 (UTC) Reply

Thank you for your reply. I have not tried the extension a any more, but yes, the link was that. Gborgonovo (talk) 16:34, 22 July 2015 (UTC) Reply

Another thing you could check for is JavaScript errors in the browser console. Mattflaschen-WMF (talk) 20:52, 23 July 2015 (UTC) Reply

Really confused by " mw.guidedTour.setTourCookie( tourName )". Is this a piece of JS code? What exactly the tourName mean here?

For example, The guided tour name for FIRSTEDIT is MediaWiki:Guidedtour-tour-firsteditjs. However, the "name" in the example codes are myfirstedit. which one should I use? 73.45.154.154 (talk) 23:06, 24 July 2015 (UTC) Reply

Yes, it's JavaScript.

With the built-in firstedit tour, the name (tourName) is 'firstedit'. 'myfirstedit' is meant to be a starting point to help a JavaScript developer write a new tour.

If 'firstedit' meets your needs already, you can just use it. Mattflaschen-WMF (talk) 00:35, 1 August 2015 (UTC) Reply

Hi, it seems that the activation of the extension:GuidedTour (with the dependency) impacts the performance of our wiki installation extremely.

Some times it runs like a charm and sometimes it slows down the entire Wiki.

After some minutes not using the Wiki it takes around 1 minute to load any wiki page (not a guided tour) and afterwards everything is fast hence our suspicion that it has to do with a TTL (time to life) limitation.

Did you experience a similar behavior? BIG RizZ (talk) 14:24, 5 August 2015 (UTC) Reply

That's curious. I have not seen that behavior. Could be caching-related, but even with the GuidedTour library, it shouldn't be a minute. Mattflaschen-WMF (talk) 00:27, 6 February 2016 (UTC) Reply

what is the difference between the bullet points:

If a guider is not visible (i.e. above the fold) for a user, the browser will scroll the user to the location of the guider.--and--The page will scroll vertically to a guider's position, if it is out of view (i.e. above or below the fold). You can disable this for individual steps. Adroit (talk) 22:49, 5 February 2016 (UTC) Reply

Nothing. Good catch, fixed. Mattflaschen-WMF (talk) 00:26, 6 February 2016 (UTC) Reply

Hello,

I know GuidedTour by French Wikipedia's Tutoriels and I am building some for French Wiktionary. A question arised: are the tours accessible for IP? Noé (talk) 12:07, 13 February 2018 (UTC) Reply

Yes. Just log out and visit https://en.wikipedia.org/wiki/Earth?tour=test . Mattflaschen-WMF (talk) 23:55, 14 February 2018 (UTC) Reply

Great, thank you! 82.67.9.9 (talk) 07:38, 15 February 2018 (UTC) Reply

Ahah, you told me to log out, so I did. It works perfectly fine. Thanks! Noé (talk) 07:40, 15 February 2018 (UTC) Reply

Is it possible to write a guided tour on "User:xxx" page and use it with any possible ways for personal use?

Thanks. 小老虎3018 (talk) 09:24, 1 February 2019 (UTC) Reply

Will this work on other wikis with different skins other than the mediawiki vector skin? Jakel181 (talk) 18:02, 18 December 2019 (UTC) Reply

Hello,

I installed the extension without issues and I created my first tour. Everything works fine for me and other users with the right to read content in the MediaWiki namespace (where the tour is stored); but users with no such right (in my installation all the not logged in users) can't use the tour. Is that a normal behaviour?

When I try to start the tour without logging in, I get this error from my browser debbuger:

The error is: Uncaught SyntaxError: Unexpected token '<'

If I disable the Mediawiki namespace restriction, everything works. Do you have any suggestion to avoid this issue?

Thanks for any help! Loman87 (talk) 10:37, 16 April 2020 (UTC) Reply

In the documentation, two different names for a css file are given, in order to override the css for guidedtours. I tried both, and neither work. Does anyone know what the name of the file should be? The pages I created are MediaWiki:Guidededtour-custom.css and MediaWiki:GuidedTour/custom.css. AmieH (talk) 06:32, 7 May 2020 (UTC) Reply

@AmieH, according to the documentation it should be `MediaWiki:GuidedTour/custom.css`. Ivanhercaz (talk) 11:01, 30 October 2020 (UTC) Reply

GuidedTours stopped loading the MediaWiki:GuidedTour/custom.css page as CSS in late 2014 (see https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GuidedTour/+/165977 and https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GuidedTour/+/164585 for detail). I'll update the documentation momentarily. You should be able to add the same styles to MediaWiki:Common.css though. Phuedx (WMF) (talk) 16:44, 4 January 2022 (UTC) Reply

I am currently making a tour but where I the tour point to links and expect the user to click on them instead of the buttons. But some users will click on the X button if no buttons are available which closes the tour. Is it possible to hide the X button? I can't find the option in the Stepbuilder (except to ignore the ESC key). 000Tom0000 (talk) 10:27, 8 September 2020 (UTC) Reply

Like the title says, are we allowed to use this at our own wiki's? They seem very good and handy to me and instead of doing that all by myself, I thought it might come in handier if I used an already set up tour.

Thanks! IlseMul (talk) 12:33, 12 August 2021 (UTC) Reply

The relevant documentation claims that this function is deprecated. Why is that? It's a nice way to specify multiple step objects in an array at once without having to gt.step for each one Aaron Liu (talk) 19:58, 4 November 2023 (UTC) Reply

User:Mattflaschen might know, given that he deprecated it in commit fc9de92a6ae6f820bff34c1b56f60731d423f0be back in July 2014, though he might not be around anymore since he no longer works at the WMF. The commit message also mentions phab:T50507 and phab:T55143.

In any case, the method's been "deprecated" for over 9 years now, so I for one would be more than happy to +2 a patch un-deprecating it. Jack Phoenix _(Contact) 02:47, 5 November 2023 (UTC) Reply

Huh, thanks. If it gets undeprecated, support for the "back" action should also be added.

It appears Mattflaschen never edited beyond 2019年12月03日 on any wiki, should I just open a phab task for now? Aaron Liu (talk) 13:43, 5 November 2023 (UTC) Reply

WORKSFORME. :-)

It's not unusual for ex-staff to simply "vanish" from (WMF) wikis after their contract with the Foundation is up. That said, software is written by people and no person is perfect, so maybe what made sense 9 year ago perhaps isn't the best of ideas by today's standards. IMO that it hasn't been removed from the code in over 9 years and that there'd be a valid use case is already more than enough of a sufficient reason for removing that pointless @deprecated tag from it, but I don't maintain this codebase nor have the final say over such matters. Jack Phoenix _(Contact) 14:05, 5 November 2023 (UTC) Reply

Tracked in Phabricator
Task T350549

Aaron Liu (talk) 14:45, 5 November 2023 (UTC) Reply

My apologies ignore this post I apparently cannot read Guillaume Taillefer (talk) 14:47, 2 February 2024 (UTC) Reply

My Mediawiki version is 1.41. I installed GuideTour and myURL/index.php?tour=test does give a proper tour. But in the MediaWiki namespace I do not find any code.

Also I copied https://gerrit.wikimedia.org/g/mediawiki/extensions/GuidedTour/%2B/HEAD/modules/tours/test.js into my MediaWiki namespace with the name test1.js and also with test1 (without the .js extension) , and tried to execute the tour with: tour=test1.js or tour=test1 but without any respond.

How to start just a 'Hello world' tour on my wiki? Bernard543 (talk) 09:42, 20 May 2024 (UTC) Reply