Another maybe silly question. The extension works well with hyperlinks of articles from the main namespace. Is there a way to activate it for other namespaces?
Topic on Extension talk:Popups
Hey @Alzi24 could you tell me more about how this might benefit you? Currently there are no plans to increase the availability in other namespaces, but uses cases would help to build an argument. :)
On our wiki, most of the biggest content pages are also category pages.
So for instance, our page on the German toymaker '''Märklin'''
https://www.brightontoymuseum.co.uk/index/Category:Märklin
gives the background to the company, but also serves as a central category page for listing all the museum's relevant exhibits, and also all the images we've collected/edited/created.
We have comparatively few category pages that aren't also significant content pages. ~~~~
Would be useful for us since we use Talk pages and subpages to document context and conflicts that don't belong in the content namespace, but would be more useful if we could expose them through Popups. Expanding the content namespace to add Talk pages is likewise not a workaround.
In our local wiki, there'd be two use cases.
1. Templates: Viewing the help page with an overview of our templates, one could see the content of the template page within the popup. In our very special case the content of the template is not only the template itself, it's preceded by a short "noinclude" description of the template.
2. "Source" namespace: Besides the main namespace, we maintain a source namespace. All pages within the source namespace are simple redirects to the regarding source (which is, simplified, the description of a book). Articles of the main namespace now contain references to the sources not by directly linking to the book but instead by using the "Source:series-episode" (which is easier & usually shorter).
Don't know if any of these matters for any other wiki, so it is only a secondary proposal.
Example from Alzi24's wiki: https://perrypedia.proc.org/wiki/GREYHOUND (examples always help!)
I agree that it would be a very useful configuration option for the extension. 3rd-party wikis could utilize it immediately as a site-wide configuration. Wikimedia wikis could potentially utilize it as a power-editor setting, either individually configurable now, or in the future as part of the previously discussed advanced-popups (for editors) version idea.
Thanks both, those are helpful examples. I've created a phabricator task to have folks evaluate and discuss.
You can already configure this. Right now page previews will show for links to anything in your content namespace.
Configuring Manual:$wgContentNamespaces will show previews for other namespaces.
The downside of this, is that these namespaces are also tied to various other special pages.
In the mean time, you can experiment on a user level using the following in your user js: ``` mw.config.set('wgContentNamespaces', [0,2]); ```
Thanks, Jdlrobson, that fixes the toy museum's issue! IMO this is a really cool feature. ~~~~
Your first proposal seems to be too risky. I won't bother for some seldom used special pages, but I guess the articles count would be compromised. So I tried the user.js, which will work ... nearly fine with some constraints.
USER namespace: the popup is shown perfectly well.
TEMPLATE: the result depends of the complexity of the template, Popups are shown if it is a simple template, but not if there is some html code in, like div, span, ... (the reason might be we still use TextExtracts, not RESTbase)
Our own private "Source" namespace: unfortunately not. Maybe because it is always a redirect, back to a main namespace.
(In case of a main namespace redirect to another main namespace article, however, the popup shows the target article.)
Doesn't matter, not worth a headache.