My problem:
I want to open an intranet wiki to the outside world, with Google
login to even view anything beyond the fact of its existence. (I
emailed the list about this before, and it's working great and
everyone is very pleased.)
We have an external IP, which accepts SSL on 443 and http:// on 80,
and passes both through to the back-end server as plaintext on port
80. So both https://example.wiki and http://example.wiki work, because
we have legacy http:// URLs in documentation *everywhere* that need to
keep working.
Trouble is: how do I get it, when it gets an http:// URL, to
auto-redirect to https:// ?
Remember that the server sees *only* http:// connections, it isn't
doing SSL at all - SSL is terminated at the external IP.
I had to make the GoogleLogin extension (0.3.1) accept both http://
and https:// versions of Special:GoogleLogin for login to work on
http:// pages.
(Can Apache even see if the incoming request was originally https:// ?)
Ideas welcome!
- d.
Hello,
I installed yesterday the latest available wikibase repository extension
on a fresh install of Mediawiki 1.28 (PHP 5.6.29). I followed the
instructions of https://www.mediawiki.org/wiki/Wikibase/Installation.
After the installation, I wondered how to create a new item since I
noticed I should add the /Special:NewItem suffix to the base URL.
However, is ther any user documentation where I could previously find
this information ? As informations to create properties ?
What is more, is the software behind the /Wikidata Query Service/
available for use on my own wiki ?
Thanks,
--
Jean-Baptiste Pressac
Traitement et analyse de bases de données
Production et diffusion de corpus numériques
Centre de Recherche Bretonne et Celtique
Unité mixte de service (UMS) 3554
20 rue Duquesne
CS 93837
29238 Brest cedex 3
tel : +33 (0)2 98 01 68 95
fax : +33 (0)2 98 01 63 93
Hello,
Almost two weeks ago, the Technical Collaboration team invited proposals
for the first edition of the Developer Wishlist survey!
We collected around 77 proposals that were marked as suitable for the
developer wishlist and met the defined scope and criteria
<https://www.mediawiki.org/wiki/Developer_Wishlist#Scope>. These proposals
fall into the following nine categories: Frontend, Backend, Code
Contribution (Process, Guidelines), Extensions, Technical Debt, Developer
Environment, Documentation, Tools (Phabricator, Gerrit) and Community
Engagement.
Voting phase starts now and will run until *February 14th, 23:59 UTC*. Click
here on a category and show support for the proposals you care for most
<https://www.mediawiki.org/wiki/Developer_Wishlist>. Use the 'Vote' and
'Endorse' buttons next to a proposal to do so.
*What happens next?*Proposals that will gather most votes will be included
in the final results which will be published on *Wednesday, February 15th*.
These proposals will also be considered in the Wikimedia Foundation’s
annual plan FY 2017-18.
Cheers,
Srishti
--
Srishti Sethi
Developer Advocate
Technical Collaboration team
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
I recently upgraded to 1.28.
Before the update I could pass a category into a template:
<includeonly>{|
|align="center"|Also see [[{{#if: {{{term|}}}|{{{term}}}|{{{1}}}| }}]]
|}</includeonly>
But now it fails if I pass "Category:Foo" or ":Category:Foo".
In the first case (with term=) it tries to assign the category to the
page the template is on.
In the second case it fails at the colon.
I have tried using : and making a template:colon that returns :
-- both failed.
I feel that I am missing something simple, but can't figure it out.
-Bri
Is there a description how to upgrade from 1.23 to version 1.27/1.28
My profider is upgrading the php version tonight so I have to upgrade
mediawiki.
As I am mediawiki-dummy anny help is welcome.
Regards
Harry
Hi guys!
We just upgrade our wiki to MW 1.28 and the session totally failed.
The symptom is session id changed every time user refresh/visit new page.
Therefore, users can't login nor save edits.
(*"There seems to be a problem with your login session; this action has
been canceled as a precaution against session hijacking. Go back to the
previous page, reload that page and then try again" / **Sorry! We could not
process your edit due to a loss of session data. Please try again. If it
still doesn't work, try logging out and logging back in.*)
We tried $wgSessionCacheType = CACHE_DB; / CACHE_ACCEL; and 'redis';
as well as set the $wgCookieDomain+$wgCookiePrefix but does not solve this
error at all.
https://phabricator.wikimedia.org/T156882 bug reported here but not any
known fix for that.
Anyone have idea on how to fix this bug?
this bug can be reproduced if you login here
https://zh.moegirl.org/index.php?title=Special:%E7%94%A8%E6%88%B7%E7%99%BB%…
with User:
*sessionlosttester*
Password:
*123456*
Thank you!
We have an intranet wiki running 1.27 from tarball. I just installed
the previous version of GoogleLogin (0.3.1, because automatic account
creation works and it doesn't in 0.4). So you now need Google Login on
one of our whitelisted GApps domains to read it, let alone edit it.
What we want is to make this available on the public Internet (SSL of
course) so that workers in our international offices can use it, if
they're logged into their work Google account.
This is pretty much the "hard shell, tasty soft centre" security
model. Is this a desperately unsafe thing to do? Has anyone else done
this or something like it?
(We could put basic auth in front of it as well, but this is for the
sort of non-technical worker who this would desperately confuse. We
probably can't lock it to given IP ranges either.)
- d.
