Movatterモバイル変換

[0]ホーム
URL:

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview
List overview
Download

Wikitech-lApril 2012

wikitech-l@lists.wikimedia.org
  • 152 participants
  • 192 discussions
Start a nNew thread
Database dumps
by Byrial Jensen 17 Apr '25

17 Apr '25
Until some weeks agohttp://dumps.wikimedia.org/backup-index.html usedto show 4 dumps in progress at the same time. That meant that newdatabase dumps normally was available within about 3 weeks for alldatabases except for enwiki and maybe dewiki where the dump process dueto size took longer time.However the 4 dumps processes at one time become 3 some weeks ago. Andafter massive failures at June 4, only one dump has been in progress atthe same time. So at the current speed it will take several months tocome thru all dumps.Is it possible to speed up the process again using several dumpprocesses at the same time?Thank you,Byrial
3 2
0 0
User-Agent:
by Domas Mituzas 17 Apr '25

17 Apr '25
Hi!from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites.Domas
19 61
0 0
EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25
What's the status of the project to create a grammar for Wikitext in EBNF?There are two pages:http://meta.wikimedia.org/wiki/Wikitext_Metasyntaxhttp://www.mediawiki.org/wiki/Markup_specNothing seems to have happened since January this year. Also the comments onthe latter page seem to indicate a lack of clear goal: is this just a funproject, is it to improve the existing parser, or is it to facilititate anew parser? It's obviously a lot of work, so it needs to be of clearbenefit.Brion requested the grammar IIRC (and there's a comment to that effect athttp://bugzilla.wikimedia.org/show_bug.cgi?id=7), so I'm wondering what became of it.Is there still a goal of replacing the parser? Or is there some alternativeplan?Steve
26 217
0 0
Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24
Hello,I have been a WP editor since 2006. I hope you can help me. For some reasonI no longer have Section Heading titles showing in the Articles. This istrue of all Headings including the one that carries the Article subject'sname. When there is a Table of Contents, it appears fine and, when I clickon a particular Section, it goes to that Section, but all that is there is astraight line separating the Sections. There is also no button to edit aSection. If I edit the page and remove the "== ==" markers from the SectionTitles, the Title then shows up, but not as a Section Heading. Also, I don'thave any Date separators on my Want List. This started 2 days ago. Anythoughts?Thanks,Marc Riddell[[User:Michael David]]
10 11
0 0
MediaWiki 1.19.0beta2
by Sam Reed 09 May '14

09 May '14
I'm happy to announce the availability of the second beta release of thenew MediaWiki 1.19 release series.Please try it out and let us know what you think. Don't run it on anywikis that you really care about, unless you are both very brave andvery confident in your MediaWiki administration skills.MediaWiki 1.19 is a large release that contains many new features andbug fixes. This is a summary of the major changes of interest to users.You can consult the RELEASE-NOTES-1.19 file for the full list of changesin this version.Five security issues were discovered.It was discovered that the api had a cross-site request forgery (CSRF)vulnerability in the block/unblock modules. It was possible for a useraccount with the block privileges to block or unblock another user withoutproviding a token.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=34212It was discovered that the resource loader can leak certain kinds of privatedata across domain origin boundaries, by providing the data as an executableJavaScript file. In MediaWiki 1.18 and later, this includes the leaking ofCSRFprotection tokens. This allows compromise of the wiki's user accounts, saybychanging the user's email address and then requesting a password reset.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=34907Jan Schejbal ofHatforce.com discovered a cross-site request forgery (CSRF)vulnerability in Special:Upload. Modern browsers (since at least as early asDecember 2010) are able to post file uploads without user interaction,violating previous security assumptions within MediaWiki. Depending on the wiki's configuration, this vulnerability could lead tofurthercompromise, especially on private wikis where the set of allowed file typesisbroader than on public wikis. Note that CSRF allows compromise of a wikifroman external website even if the wiki is behind a firewall.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35317George Argyros and Aggelos Kiayias reported that the method used to generatepassword reset tokens is not sufficiently secure. Instead we use variousmoresecure random number generators, depending on what is available on theplatform. Windows users are strongly advised to install either the opensslextension or the mcrypt extension for PHP so that MediaWiki can takeadvantageof the cryptographic random number facility provided by Windows.Any extension developers using mt_rand() to generate random numbers incontextswhere security is required are encouraged to instead make use of theMWCryptRand class introduced with this release.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35078A long-standing bug in the wikitext parser (bug 22555) was discovered tohavesecurity implications. In the presence of the popular CharInsert extension,itleads to cross-site scripting (XSS). XSS may be possible with otherextensionsor perhaps even the MediaWiki core alone, although this is not confirmed atthis time. A denial-of-service attack (infinite loop) is also possibleregardless of configuration.For more details, seehttps://bugzilla.wikimedia.org/show_bug.cgi?id=35315********************************************************************* What's new?*********************************************************************MediaWiki 1.19 brings the usual host of various bugfixes and new features.Comprehensive list of what's new is in the release notes.* Bumped MySQL version requirement to 5.0.2.* Disable the partial HTML and MathML rendering options for Math, and render as PNG by default. * MathML mode was so incomplete most people thought it simply didn't work.* New skins/common/*.css files usable by skins instead of having to copypiles of generic styles from MonoBook or Vector's css.* The default user signature now contains a talk link in addition to theuser link.* Searching blocked usernames in block log is now clearer.* Better timezone recognition in user preferences.* Extensions can now participate in the extraction of titles from URL paths.* The command-line installer supports various RDBMSes better.* The interwiki links table can now be accessed also when the interwikicache is used (used in the API and the Interwiki extension).Internationalization- --------------------* More gender support (for instance in user lists).* Add languages: Canadian English.* Language converter improved, e.g. it now works depending on the page content language.* Time and number-formatting magic words also now depend on the page content language.* Bidirectional support further improved after 1.18.Release notes- -------------Full release notes:https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob_plain;f=RELEASE-NOTES-1.19;hb=1.19.0beta2https://www.mediawiki.org/wiki/Release_notes/1.19Co-inciding with these security releases, the MediaWiki source coderepository hasmoved from SVN (athttps://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3)to Git (https://gerrit.wikimedia.org/gitweb/mediawiki/core.git). So therelevantcommits for these releases will not be appearing in our SVN repository. Ifyou useSVN checkouts of MediaWiki for version control, you need to migrate these toGit.If you up are using tarballs, there should be no change in the process foryou.Please note that any WMF-deployed extensions have also been migrated to Gitalso, along with some other non WMF-maintained ones.Please bear with us, some of the Git related links for this release may notwork instantly,but should later on.To do a simple Git clone, the command is:git clonehttps://gerrit.wikimedia.org/r/p/mediawiki/core.gitMore information is available athttps://www.mediawiki.org/wiki/GitFor more help, please visit the #mediawiki IRC channel onfreenode.netirc://irc.freenode.net/mediawiki or email The MediaWiki-l mailing listat mediawiki-l(a)lists.wikimedia.org.**********************************************************************Download:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gzPatch to previous version (1.19.0beta1), without interface text:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gzInterface text changes:http://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patch.gzGPG signatures:http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gz.sighttp://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patch.gz.sigPublic keys:https://secure.wikimedia.org/keys.html
5 5
0 0

02 Jul '12
Hello!I thought I'd reach out to the wider wikitech community to discuss aproblem we are having in the MobileFrontend extension and see ifanyone can come up with a good solution.The MobileFrontend extension is increasingly getting [1] bugs [2]raised [3] which are due to inline css styles present in certain wikiarticles that are written with the desktop site in mind. (Slightly offtopic there is also certain content that just doesn't work on mobile[4])To get an idea of some of the bugs that are present please see this bug [5].Currently we are resorting to various !important hacks in a separatecss file [6] but this is not sustainable and does not cover everythingand ideally I would prefer that this file was not needed at all.Solutions I have thought about so far involve the following. I am yetto conclude on which is the best way to do this so would reallyappreciate discussion...1) scrubbing all inline styles#########################* in php - my worry is this would be a quite expensive operation?* in javascript (but this doesn't help people with javascript disabled)* would mean any nice mobile safe styling disappears :(2) scrubbing certain inline styles#########################* I could imagine us scrubbing any inline styles which have not beenmarked as mobile safe (e.g. anything with a class 'mobilesafe' keepsits inline style) - this at least allows editors to use pretty stylesand encourages checking their styles on mobile3) disallowing inline styles in wikitext output##################################* this is controversial as it would restrict us to defining css rulesin MediaWiki:Common.css which only admins can edit** one could imagine pages/templates being able to maintain their ownstylesheets for desktop and mobile to allow customisations** ResourceLoader could serve the desktop or mobile stylesheetdepending on the context4) educating editors better about ensuring their styles work on mobile#############################################I'm not sure how effective/sustainable this would be and how we'd goabout doing this... but would be keen to hear your thoughts around it.[1]https://bugzilla.wikimedia.org/show_bug.cgi?id=30887[2]https://bugzilla.wikimedia.org/show_bug.cgi?id=36030[3]https://bugzilla.wikimedia.org/show_bug.cgi?id=36076[4]https://bugzilla.wikimedia.org/show_bug.cgi?id=20030[5]https://bugzilla.wikimedia.org/show_bug.cgi?id=35704[6]https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/MobileFrontend…
24 58
0 0
MediaWiki to Latex Converter
by Hugo Vincent 18 Jun '12

18 Jun '12
Hi everyone,I recently set up a MediaWiki (http://server.bluewatersys.com/w90n740/) and I need to extra the content from it and convert it into LaTeX syntax for printed documentation. I have googled for a suitable OSS solution but nothing was apparent.I would prefer a script written in Python, but any recommendations would be very welcome.Do you know of anything suitable?Kind Regards,Hugo Vincent,Bluewater Systems.
6 13
0 0

15 Jun '12
Hello!Various cultural institutions in Denmark are planning a cultural heritagehackathon in the autumn. They are still in the google-doc-phase:https://docs.google.com/spreadsheet/ccc?key=0Asi52gKHCCyOdG9naG55Y2xtVnlaLU…Perhaps someone is interested in chipping in with knowledge about theMediaWiki API?Regards,Ole--http://palnatoke.org * @palnatoke * +4522934588
4 9
0 0
Guidelines for db schema changes
by Rob Lanphier 14 Jun '12

14 Jun '12
Hi everyone,As we do more frequent deploys, it's going to become critical that weget database schema changes correct, and that we do so in a way thatgives us time to prepare for said changes and roll back to oldversions of the software should a deploy go poorly. This applies bothto MediaWiki core and to WMF-deployed extensions.I'd like to propose that we make the following standard practice:1. All schema changes must go through a period of being optional.For example, instead of changing the format of a column, create a newcolumn, make all writes happen to the old and new column (if itexists) and deprecate use of the old column. Check if the new columnexists before blindly assuming that it does. Only eliminate supportfor the old column after it's clear the schema migration has happenedand there's no chance that we'll need to roll back to the old versionof the software.2. There might be cases where rule #1 will be prohibitive from aperformance perspective. However, schema changes like that should berare to begin with, and should have prominent discussion on this list. In the case where it's impossible to follow rule #1, it is stillcritical to write scripts to roll back to the pre-change state.3. For anything that involves a schema change to the production dbs,make sure Asher Feldman (afeldman(a)wikimedia.org) is on the reviewerlist. He's already keeping an eye on this stuff the best he can, butit's going to be easy for him to miss changes in extensions shouldthey happen.I don't have a strong opinion about whether we need to follow rule #1above through an iteration of our six month tarball release cycle, butwe at least need to follow it through the two week deployment cycle.Assuming this seems sensible to everyone, I can update this page with this:http://www.mediawiki.org/wiki/Development_policy(/me desperately tries to avoid yak shaving and updating the policyabove for Git)Rob
6 9
0 0
Database dump of Bugzilla
by John Du Hart 21 May '12

21 May '12
I'm currently investigating alternative bug tracker and project managementsoftware for MediaWiki. To do that I'll be installing some differentsoftware on the Labs and importing existing bugs for evaluation by thedevelopment team and users. The following software is planned for test: - JIRA <http://www.atlassian.com/software/jira/overview> + Greenhopper + Bonfire - YouTrack <http://www.jetbrains.com/youtrack/> - The Bug Genie <http://www.thebuggenie.com/index.php> - Redmine <http://www.redmine.org/> - ChiliProject <https://www.chiliproject.org/>If you have any suggestions for this list I'd be glad to hear it.Of course, this goes back to the original request. To do this I need a dumpof the current Bugzilla install. Is it possible for me to get this andunder what conditions? Thank you.-- John
18 43
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp