Tue, Jul 9
https://en.wikiversity.org/wiki/MediaWiki:Random-url now updated.
May 11 2019
Apr 13 2019
Mar 22 2019
Feb 10 2019
It appears that everything has been resolved. Thanks!
Jan 12 2019
Mar 12 2018
I think that's a valid assumption. I'm trying to think of a use case where a wiki would want RandomRoot for their main namespace but Random for one of the other namespaces. I'm not coming up with anything.
Mar 5 2018
The best way to understand why might be the explanation at en.wikipedia: https://en.wikipedia.org/wiki/Help:Special_page .
Only namespace 0 (NS_MAIN?) is a content namespace.
Mar 4 2018
The mobile configuration should match the desktop configuration. The Random desktop link is already configured as:
Feb 18 2018
Jan 15 2018
Jan 4 2017
I'm not sure I have any value I can add to the project at present, but if something comes up, please let me know.
Dec 2 2016
Thanks for your assistance on this. I've removed the problematic code from https://en.wikiversity.org/wiki/MediaWiki:Common.js . It did not appear to be necessary anymore.
Dec 1 2016
Oct 26 2016
Aug 20 2016
It's been broken since June. Not necessary to work on it over the weekend unless you want to. It is somewhat functional in its current state but not desirable.
May 13 2016
The wire frames above look good. Currently missing from the web version is the percentage of plagiarism detected and the word count for the edit. These would definitely be helpful on smaller wikis where there are fewer users to do plagiarism checks.
Apr 24 2016
Thanks! Would you be willing to include a short summary of how the issue was resolved? I'm trying to learn more about Linux configuration, and it would certainly be helpful for me. It might also help others later who find this on a search and wonder how to resolve similar issues.
Apr 23 2016
Jan 3 2016
Yes, that resolves this issue. I took the code and put it into a different template:
Dec 16 2015
Would adding the old data with a different tag work? The historical / "bad" data could be loaded with a "historical" or "deprecated" tag. And if you're willing, load through June 30, 2016. That's a 13/14 month overlap, allowing full comparison of old and new measurements. After June 2016, only new data would be available.
I'll just add my own quick perspective on this. The previous method for accessing log files by having to download all data for all projects by hour was research-prohibitive. The Pageview API is a significant improvement for quickly getting individual pages or top 1000 results.
Dec 10 2015
Dec 1 2015
I'm not sure where to share this code with the community, so I'll add it here for reference. I created a Python script to generate monthly stats for en.wikiversity, and also functions to pull and tally individual page stats from a list of pages. The code is at:
Nov 26 2015
Thanks for the suggestion. But there's more to it than just HTML formatting. The numbers are used as div IDs to hide and show each answer individually. The div could likely be converted to a span, but that doesn't resolve the issue of numbering them uniquely on the page so they can be triggered individually.
Nov 23 2015
I don't know where this would fit in terms of priority, but something I was just looking for is what might be called "Referrer URL" in a web sever log file. I'm not looking for any external information that would be a privacy concern. What I would like to see is which internal page links are highly used to access other pages, and which ones aren't. In other words, when looking at "What links here", I'd like to be able to find out which of those links are promoting the page, and which ones aren't.
Nov 14 2015
Nov 8 2015
Clarifying: It was already in the proposal at https://en.wikiversity.org/wiki/Wikiversity:User_access_levels that Custodians would be able to remove Curators. I just forgot to include it here.
Sorry, I missed that detail. The intention was that Custodians would be able to both add and remove Curators. I will update our documentation accordingly.
Nov 5 2015
After thorough discussion and voting on Wikiversity user access levels, available at https://en.wikiversity.org/wiki/Wikiversity_talk:User_access_levels, the community supports the creation of a new Curators group with rights listed at https://en.wikiversity.org/wiki/Wikiversity:User_access_levels. The discussion was listed with a site-wide notice, https://en.wikiversity.org/w/index.php?title=MediaWiki:Sitenotice&diff=prev&oldid=1455933, and open for two weeks. The Curators group will not have access to deleted content, addressing concerns noted above.
Oct 1 2015
See https://en.wikiversity.org/wiki/IT_Fundamentals/Hardware#Review_Questions . The review questions are numbered both internally (hidden tag) and visually for the user. It would be nice to have a variable that could be used for both numbers and incremented through code rather than typed manually.
Sep 26 2015
We have a number of pages where we have sequential numbers on content, but the numbers need to sent to templates to be rendered rather than numbering the content using #. Some pages may have as many as 40 or 50 of these items, and they are currently maintained manually. I was hoping to use variables to automate the counting. I tried Lua, but each #invoke is a clean state.
Thanks for the fast response. Are there any alternatives that might provide similar functionality?