Hey,
Maybe I'm missing something here, but why does Wikipedia still use the
Oversight extension if it has since be superseded by core functionality.
I'm sure there's a simple explanation, I just can't find it. :)
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com
> What I want is :
>
> 1. when I register in my service , it could create an acount in mediawiki
> 2. when I login in my service , it could login in mediawiki
> 3. when I logout in my service ,it could logout in mediawiki
What you want would be better served by implementing an AuthPlugin:
https://www.mediawiki.org/wiki/AuthPlugin
It should be 4 spaces... I found where the default is set, here's a
quick untested patch with no configurability.
You can also change your personal preferences under Differences ->
Preferences
diff --git
a/gerrit-reviewdb/src/main/java/com/google/gerrit/reviewdb/client/AccountDiffPreference.java
b/gerrit-reviewdb/src/main/java/com/google/gerrit/reviewdb/client/AccountDiffPreference.java
index 3b04725..5c689aa 100644
---
a/gerrit-reviewdb/src/main/java/com/google/gerrit/reviewdb/client/AccountDiffPreference.java
+++
b/gerrit-reviewdb/src/main/java/com/google/gerrit/reviewdb/client/AccountDiffPreference.java
@@ -58,7 +58,7 @@ public class AccountDiffPreference {
public static AccountDiffPreference createDefault(Account.Id
accountId) {
AccountDiffPreference p = new AccountDiffPreference(accountId);
p.setIgnoreWhitespace(Whitespace.IGNORE_NONE);
- p.setTabSize(8);
+ p.setTabSize(4);
p.setLineLength(100);
p.setSyntaxHighlighting(true);
p.setShowWhitespaceErrors(true);
Hi,
I have build mediawiki .
And I have another webservice write by myself.
What I want is :
1. when I register in my service , it could create an acount in mediawiki
2. when I login in my service , it could login in mediawiki
3. when I logout in my service ,it could logout in mediawiki
I have found API:Login and API:Logout .
But I cannot find something like API:CreateAccount.
So can someone tell me how to create account by API?
Thanks.
hello,
I have configured (and patched) richeditor in my mediawiki 1.19.1:
require_once("$IP/extensions/WYSIWYG/WYSIWYG.php");
$wgGroupPermissions['*']['wysiwyg'] = TRUE;
$wgDefaultUserOptions['riched_use_toggle'] = 1;
$wgDefaultUserOptions['riched_start_disabled'] = 1;
$wgDefaultUserOptions['riched_use_popup'] = 0;
$wgDefaultUserOptions['riched_toggle_remember_state'] = 1;
$wgDefaultUserOptions['cke_show'] = 'richeditor';
It works in url like "action=edit&mode=wysiwyg" but it doesn't in the
preview page (action=submit). In this page I have the default
mediawiki editor.
I know this module is under development, can you help me?
ADM
On 08/06/2012 08:03 PM, Tomás Vírseda wrote:
> Anyway I think it is useful and I'd like to share this project in
> Internet. Which is the best strategy?
> I know that I can export all my pages into a file. But is there
> any idea/extensions about this issue?
I'm interested in anything you find out here. I've talked to some
people about a way to ship some standard templates or gadgets with the
MediaWiki tarball and it sounds like the same method could be used to
solve both our problems.
[CCing wikitech-l since someone there may know what needs to be done.]
--
http://hexmode.com/
Human evil is not a problem. It is a mystery. It cannot be solved.
-- When Atheism Becomes a Religion, Chris Hedges
Hi!
According to some pages on mediawiki.org[1][2], it seems that wiki is
going to be
a central repository for gadgets which will be shared with WMF projects
(and other projects using MediaWiki).
I would like to know if there is any chance of changing the licence requirements
for the new "Gadget:" namespace of this central wiki, so that they can be
licensed under a true free ''software'' licence such as GPL (without needing to
license also under CC-BY-SA, which is not compatible).
The main advantage is that this would allow us to import GPL-licensed scripts
for use on WMF wikis. Gadget developers could e.g.:
* Copy parts of MediaWiki code, and modify it on-wiki (to try to fix bugs,
or to customize the default behavior)
* Adapt other external scripts for use on Wikimedia Wikis.
See also[3].
What do you think?
Best regards,
Helder
[1] https://www.mediawiki.org/wiki/ResourceLoader/Version_2_Design_Specificatio…
[2] https://www.mediawiki.org/wiki/Thread:Talk:ResourceLoader/V2_testing/Questi…
[3] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(policy)#Proper_licens…
You are invited to the Localisation team development demo on Tuesday 8
August 2012 at 15:00 UTC (other time zones: 08:00 PDT, 17:00 CEST,
20:30 IST). This meeting will take 40 minutes at most. In this meeting
the Localisation team will present its deliverables from sprint 21[1].
As there were no demos for the previous two sprints because of
Wikimania and holidays, work from those sprints will also be covered.
After about 20 minutes of presentation, the remainder of the meeting
is for discussion.
We hope you can attend, and please invite any other colleagues or
friends you think are interested!
This meeting will be held using WebEx. Please ensure that you log in a
few minutes before the meeting starts, so that you have time to
install any required plug-ins or software. Connection details and a
quick link to add this meeting to your calendar can be found below the
signature.
[1] https://mingle.corp.wikimedia.org/projects/internationalization/cards/1070
--
Siebrand Mazeland
Product Manager Localisation
Wikimedia Foundation
M: +31 6 50 69 1239
Skype: siebrand
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://wikimedia.webex.com/wikimedia/j.php?ED=182389302&UID=1293732427&RT=…
2. If requested, enter your name and email address.
3. No password is required
4. Click "Join".
To view in other time zones, please click the link:
https://wikimedia.webex.com/wikimedia/j.php?ED=182389302&UID=1293732427&ORT…
To add this meeting to your calendar program (for example Microsoft
Outlook), click this link:
https://wikimedia.webex.com/wikimedia/j.php?ED=182389302&UID=1293732427&ICS…
> Mhm. I like the idea of function supersession. Basically, I just don't
> think we should call a function deprecated unless it actually is indeed
> deprecated, i.e., no longer used anywhere in the core. Theoretically, a
> function that is deprecated in the core should not show any warnings
> whatsoever when testing without extensions.
+1. Things should be deprecated, or not deprecated.
If something is deprecated, it should not be used whatsoever in core
or extensions (that are in the Wikimedia repo). It should be the
person adding the wfDeprecated()'s responsibility to ensure that there
are no uses in core or extensions.
I am not a fan of hidden "Deprecated in some future version" thingies.
If there is something wrong enough with the code to deprecate it, it
should be deprecated immediatly. I do think its ok to occasionally
have "It's ok to use this function in old code, but new code should
use other function x", but such code should at most have an
@deprecated on it. It shouldn't generate warnings until such a time as
it is no longer used anywhere in core.
If something deprecated is still used in core, it is perhaps a sign
that whatever is replacing the deprecated function isn't a sufficient
replacement.
--
-Bawolff