Welcome and thank you for serving/having served in such an important role !
DJ
On Thu, Jun 20, 2019 at 11:39 AM Amir Sarabadani
wrote:
> Hello everyone,
> The deadline for the public feedback was yesterday. Some objections have
> raised but committee decided not to change the structure of
There can be various causes, but your file path makes me suspect that it
might have something to do with the fact that your 'local' files are on a
shared/network file segment. Maybe your client isn't allowed to lock files
on this share.
But see
No, it is just not possible to disable API access any longer through the
switches wgEnableAPI and wgEnableWriteAPI. It's simply always on now.
DJ
On Thu, Nov 1, 2018 at 2:04 PM Rowe (US), Dolores A <
dolores.a.r...@boeing.com> wrote:
> Dear Group,
>
> When I look at this web page:
>
Maybe you missed that table.foo (and similarly string.foo) is the prototype
for any someTable, which thus automatically has someTable.foo(). And that
someTable:foo(args) is just syntactic sugar for someTable.foo( someTable,
args ) ?
It's one of those weird Lua quirks
DJ
On Mon, Jul 16, 2018 at
> From what I’ve heard, the rules about personal data are less strict when
the data is stored and processed in order to fulfil a contract.
Less strict is not a good description. GDPR has many restrictions on how
you collect and handle personal data. It however also has many reasons why
you are
No, but there are some related tickets on this topic however:
https://phabricator.wikimedia.org/T89552
https://phabricator.wikimedia.org/T187872
https://phabricator.wikimedia.org/T187873
DJ
On Thu, Apr 5, 2018 at 3:28 PM, Dan Mar <220...@gmail.com> wrote:
> Dear all!
> Is there an extension to
This might be a typo in your message, but it's jQuery, not jquery.
Also you can shorten that page ready code, see:
http://learn.jquery.com/using-jquery-core/document-ready/
By default, jQuery and it's alias $ are always available in MediaWiki.
However, we often tend to import globals and then
@mat54
The definition of personal information in this law, is wider than you
assume most likely. It also includes IP addresses, nicknames, login
ids, real names, fingerprints of your browser, etc etc. basically
anything that can potentially lead back to the user.
The collection of the data in
"all" is a lot, and not likely to be what you want. All includes skinning,
libraries, content scripts, site scripts, user scripts etc. javascript,
css, userinterface message etc... All have different elements to them that
might not fit your use case, so identifying that is important.
Furthermore,
He brion,
Maybe there could some day be a program, where an external company could
propose items to place on the roadmap, with the promise that they will
deliver a developer to collaborate on that item if the platform chooses to
prioritize it. Like a Community tech wishlist in exchange for mutual
Double check if your upgrade went ok. Often people only update core, forgetting
either to update extensions or skins, or something went wrong during the
upgrade and they just skipped over the error message.
DJ
> On 19 Jan 2017, at 11:15, Bri wrote:
>
> I recently
This means exactly what it says. There is a script in the file, that a
webbrowser might execute, which is a security risk.
Judging from http://sozi.baierouge.fr/pages/10-about.html, the script in the
file is probably just used to do animations, but MediaWiki cannot know that.
You can flip the
1: You should always try to use matching versions of core and extension
software.
2: English Wikipedia always uses the 'latest and greatest', so if you copy
from them, so should you.
3: English Wikipedia community has the tendency to build some VERY
complicated stuff, that uses dozens of
The answer is not as simple as that.
First let's try to explain the structure a bit. All existing skins are a
combination of a PHP template and a set of CSS. When we say Vector, we mean
the PHP UI template vector, and the CSS that goes with that template. This
template itself only handles
Here is a complete example:
https://test2.wikipedia.org/wiki/User:TheDJ/common.js
Note that for anything post+token related, it's a lot easier to use
api.postWithEditToken() or api.postWithToken(). It does automatic token
re-requesting if it expired.
DJ
On Tue, Nov 11, 2014 at 12:00 PM, John
I think what you want is already live on Wikipedia right now. Try
going to the redirect https://en.wikipedia.org/wiki/TV
This new behavior is part of MediaWiki 1.24 release. Does it better
match your expectations ?
DJ
On Fri, Sep 5, 2014 at 11:33 AM, Scheid, Bernhard
bernhard.sch...@oeaw.ac.at
One of the reasons is that it is rather inefficient. Not more than
VisualEditor, but still. There definitely would be people who would
want to disable it. It's also imperfect. It makes mistakes in highly
complex pages.
Something similar was in in the works for WikiEditor some 4 years ago,
but it
On 8 sep. 2013, at 14:10, m...@x2592.com wrote:
Hi Dmitrii,
I tried this just now, but the MathML still does not get displayed. Actually,
I want the MathML to be processed by MathJax, and am trying to solve why it
is not...
Thanks for the advice. ;-)
You can't, everything you enter
You wouldn't have Adblock installed per chance ?
DJ
On Mon, Jun 3, 2013 at 6:40 AM, Arcane 21 arc...@live.com wrote:
I just discovered an extremely strange error when parsing the following:
==Advertisements==
All one will get when trying to create that section heading will be a
blank
On 2 jun. 2013, at 06:06, David Cuenca dacu...@gmail.com wrote:
Hi Billinghurst,
While on the Amsterdam Hackathon I asked several people about why the
project was split, but I didn't get a clear answer. I can imagine that it
was because back in the day there were no easy ways of localizing
On 14 okt. 2012, at 17:45, Moritz Schubotz phy...@physikerwelt.de wrote:
Summary: I'm looking for people to discuss about the parsing of math.
The last person who really did some work on the extension was Brion Vibber.
Almost all of the (limited) work that has gone into the extension over the
21 matches
Mail list logo