On my the header of the first sidebar section (usually "Navigation") will
appear and then disappear.
Sometimes (depending on several things), it will also cause the entire
sidebar to suddenly reposition itself when the page loads.
Visually, it's janky and weird and distracting.
However, other sites have a stable, non-annoying sidebar that doesn't
And here's two examples of a site afflicted with the Sidebar Fidgets
FYI: My site, and the two jittery examples above, run Semantic Mediawiki.
I've never seen this jitter issue on a pure, non-semantic mediawiki
install, but since the issue doesn't seem related to anything "semantic",
I'm asking on this list.
I've tried about 10 different approaches, including removing from Common.js
all code that seems related to toolbar collapse/expand.
So... what are the two example sites above doing to disable a) collapsible
sidebar sections and b) preventing the first collapsible section header
P.S. The only thing my searching could unearth (besides the same unanswered
question) was this...
...which is ineffective at preventing the first sidebar navigation section
P.P.S. I've confirmed that my MediaWiki:Sidebar page is formatted correctly.
P.P.P.S. Here's another description the problem:
I finished faculty of mathematics and informatics and looking for a part time job from home, do you maybe have something for me on your site.
I can writte english, german and Balkan-region languages and i have experience as a forum support.
I am willing to take almost anything if you are willing to pay me.
there are now suggestions for booking accommodation in Vienna for the SMWCon 2014 in October.
----- Ursprüngliche Mail -----
> Dear users, developers and all people interested in semantic wikis, wikis and
> open knowledge, especially in Semantic MediaWiki!
> We are happy to announce SMWCon Fall 2014 - the 10th Semantic MediaWiki
> * Dates: October 1st to October 3rd 2014 (Wednesday to Friday)
> * Create Camp / Hackday on Saturday, October 4th
> * Location: Municipal and Provincial Archives of Vienna, Gasometer D,
> Guglgasse 14, 1110 Vienna, Austria
> * Conference wikipage: https://semantic-mediawiki.org/wiki/SMWCon_Fall_2014
> * Participants: Everybody interested in semantic wikis, wikis and open
> knowledge, especially in Semantic MediaWiki, e.g., users, developers,
> consultants, business or government representatives, researchers.
> * Registration is now open at: http://de.amiando.com/SMWCon2014.html
> (if you register, please don't book hotels yet, there will be recommendations
> next week on the connference webpage)
> * The hashtag on Semantic MediaWiki on Twitter Twitter is #SMWCon.
> SMWCon Fall 2014 will be organized by KDZ - Centre for Public Administration
> Research , supported by the Open Semantic Data Association  and the
> Municipal and Provincial Archives of Vienna  in cooperation with
> Wikimedia Austria  and Open Knowledge Foundation Austria .
> Following the success of recent SMWCons, we will have one tutorial day and
> two conference days. As a novelty, the SMWCon in Vienna will have a Create
> Camp / Hackathon on Saturday at the KDZ premises.
> Thank you to our sponsors https://gesinn.it/ (gold) and
> https://energypedia.info (silver)!
> Please contact us if you are interested in sponsoring the conference.
> Contributing to the conference: If you want to present your work in the
> conference please go to the conference wikipage and add your talk there. To
> create an attractive program for the conference, we will later ask you to
> give further information about your proposals.
> ==Among others, we encourage contributions on the following topics==
> ===Applications of semantic wikis===
> * Business Applications - what technology did you use, what were the boundary
> conditions and how did you solve your challenges?
> * Science Applications - what are potential or proven uses for SMW? How did
> SMW improve or change the way you work?
> * What is left and right of SMW?
> * Lessons learned (best/worst practices) from using semantic wikis or their
> * Semantic wikis in e-science, e-learning, e-health, e-government
> * Semantic wikis and Open Data
> * Semantic MediaWiki, Wikipedia, Wikidata, DBpedia
> ===Development of semantic wikis===
> * Development roadmap - what are the plans for SMW, what is in the pipeline?
> * Recent developments - what are you developing in the moment? Where are the
> * Semantic wikis as knowledge base backends / data integration platforms
> * Comparisons of semantic wiki concepts and technologies
> * Community building, feature wishlists, roadmapping of Semantic MediaWiki
> * Improving user experience in a semantic wiki
> * Speeding up semantic wikis
> * Integrations and interoperability of semantic wikis with other applications
> and mashups
> * Access control and security aspects in semantic wikis
> * Multilingual semantic wikis
> == Tutorials ==
> We are also looking for people giving tutorials on the first day (tutorial
> If you have questions you can contact me (Bernhard Krabina, General and Local
> Chair), or Franz Borrmann (Program Chair) per e-mail (Cc).
> Hope to see you in Vienna!
> Best regards,
> Bernhard Krabina
>  http://www.kdz.or.at
>  https://opensemanticdata.org/
>  https://www.wien.gv.at/english/history/archives/index.html
>  https://www.wikimedia.at/
>  http://www.okfn.at
> Mag. Bernhard Krabina
> KDZ - Zentrum für Verwaltungsforschung
> Centre for Public Administration Research
> Guglgasse 13, 1110 Wien
> Telefon: +43 1 8923492-27, Fax: +43 1 8923492-20
> Mobil: +43 676 849579-27, Twitter: @krabina
> mailto:email@example.com - http://www.kdz.or.at
> - Offener Haushalt - Transparente Gemeindefinanzen:
> - Plattform Verwaltungskooperation:
> - Open Government Vorgehensmodell
> KDZ News: WissensmitarbeiterIn Public Management/Governance gesucht!
In the past few weeks, we've been seeing the "Loss of session data" error message in our wiki frequently when users try to save their edited articles (and the save fails). Our best guess is that memcached, which stores session info, is losing session information unexpectedly. This began shortly after upgrading from MediaWiki 1.21 to 1.22 (I don't know if this is related, but the timing is suspicious). When users log out and log back in, the error goes away... for a time.
What is the recommended way to debug this kind of problem? What would YOU do if this issue cropped up on your wiki?
We've been inserting error_log() statements into MediaWiki core code, dumping the values of $_SERVER, $_COOKIE, and $_SESSION, and haven't found anything helpful yet.
Our wiki (version 1.22.5) is served by four webservers behind a load balancer on a private intranet. There's a master and one slave database. memcached has plenty of RAM and therefore should not be dropping data.
Thanks for any helpful debugging tips!
Good afternoon everyone,
I finished upgrading our mediawiki wiki.redmountainmakers.org to 1.22.6 last weekend.
Due to some family issues, ended up accessing my ISP to run maintenance scripts from the command line over an airport network enroute to another city.
This may have been the source of the hacking problem, as due to some problems establishing a secure connection, I transmitted a password in the clear to my ISP.
Checked back in on the wiki last week to find around 1300 new spammy users.
Have locked down the wiki, blocking new account creation, enabled a captcha, and have restricted administrator's priviledges to create new accounts.
But the new accounts keep on coming.
Spam blacklist is enabled.
Sysops have been blocked from creating accounts, as have all ordinary users.
I've changed the critical passwords.
Recommendations as to other settings I should be checking?
-- Shirley Hicks
this is a discussion happening on wikitech-l at the moment. I think this is also of interest to all the mediawiki users out there ;) Please share your thoughts!
Von: wikitech-l-bounces(a)lists.wikimedia.org [mailto:firstname.lastname@example.org] Im Auftrag von Gabriel Wicke
Gesendet: Mittwoch, 11. Juni 2014 20:48
An: Wikimedia developers
Betreff: [Wikitech-l] How to make MediaWiki easier to install: use cases
In the current discussion about git submodules vs. composer there are several different underlying assumptions about the user's situation. I think it would help the discussion to clarify which use cases we are dealing with.
Here is an attempt:
1) Shared hosting without shell. The user uploads code with (s)ftp, and can't install anything globally.
2) Shared hosting with non-root shell and git installed. The user can use git directly on the server, but can't install anything globally without root. They can manually download composer to their home directory.
3) Root on a (virtual) server. The user can install packages, and do any of the above.
The git submodules vs. composer discussion seems to focus on case 2). Case
1) could be addressed by providing a 'bundle' tar file with all dependencies that can be uploaded via (s)ftp. In case 2) composer or git can be used on the server to fetch dependencies separately.
When using git, it might be worth considering Parsoid's method of making the core repository a submodule of a 'core-deploy' repository which has all dependencies, rather than making the dependencies a submodule of core. This avoids issues with git complaining about dirty submodules in the common case of updating core often.
In case 3) the user has a full packaging system at their disposal, which means that it is theoretically possible to set up a fully-featured MediaWiki system with a few commands. So far we don't have any special support for this case (we expect users to follow the manual tarball setup), which made sense in the past as folks running their own server were fairly rare.
Many of our users are starting to take advantage of cheap virtual machines though, which are now widely available at a price point comparable to shared hosting. For this reason I think that we should put more effort into supporting case 3), for example by providing good Debian packaging which lets you do "apt-get install mediawiki-full" and get a MediaWiki install with caching, VisualEditor and so on. There are also other benefits here beyond the initial install, like automatic security updates with unattended-upgrades.
So far we don't have a good idea of how common the different use cases are, and how this distribution is changing. I think that we should try to get this information so that we can have a more informed debate.
Wikitech-l mailing list
I'm trying to find away to get rid of, or add a template, to the licensing option on File uploads labeled "None Selected." Via Mediawiki:Licenses one can add any number of licensing options, and have those licensing options call forth a template to be included on the file page. But the "None Selected" option seems to be hard coded and it doesn't seem to be possible to add a template to it via the Mediawiki:Licenses interface. I'm using semantic mediawiki functions & the variable CURRENTUSER (from an extension) to automatically annotate the uploads, via the licensing templates, but the "None Selected" option is leaving a gap in those annotations.
Sent from my iPad