MediaWiki-l March 2018

mediawiki-l@lists.wikimedia.org

45 participants
34 discussions

Lis tes messages avant qu'ils ne soient effacés!

by Badoo

Lis ton message de Nganguem Victor avant qu'il ne soit effacé! Pour lire ton message, suis simplement ce lien: http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6 D'autres personnes sont aussi présentes: Oded (Tel Aviv, Israël) Priya (Udaipur, Inde) RajaYogi BK (Udaipur, Inde) Karuna (Udaipur, Inde) Chika Reginald Onyia (Pnompen', Cambodge) ...Qui d'autre? http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6 Les liens ne fonctionnent pas dans ce message? Copie les dans la barre d'adresse de ton navigateur. Tu as reçu cet email suite à un message envoyé par Nganguem Victor de notre système. S'il s'agit d'une erreur, ignore simplement cet email. La requête sera alors effacée du système. Amuse-toi bien ! L'équipe Badoo Courrier automatique de Badoo suite à l'envoi d'un message à ton attention sur Badoo. Les réponses ne sont ni stockées, ni traitées. Si tu ne veux plus recevoir de message de Badoo, fais-le nous savoir: http://eu1.badoo.com/impersonation.phtml?lang_id=6&mail_code=65&email=media…

3 months, 3 weeks

EU’s GDPR and MediaWiki

by Tom

Hey Everyone Is there any roadmap for MediaWiki that addresses the EU’s GDPR (General Data Protection Regulation) being enforced as of 28 May 2018? Mainly addressing user registration on websites and holding what the EU deems personally identifiable information of EU residents such as usernames, real names, email addresses, etc. A method to prove consent such as a checkbox for Terms of Service and the date consent was given. From the read of GDPR, it effects any company or organization (even those outside the EU) who store data on someone living in the EU. Tom

5 years, 11 months

How do Wiki Farms work?

by John Lewis

How do Wiki Farms work? I want to build and sell a product that is a private MediaWiki site that can ingest logs and display them in templates and still have room for people to add notes about the device or service being logged using the Cargo and probably the ExternalData extensions. The problem is that I haven't seen the back end of a Wiki Farm yet so I don't know how one typically works. I know what I need. I need to build a site with the necessarily minimal plugins for functionality, a way to upgrade the mediawiki instances, a way to potentially upgrade php, a database with 1-2 schema per site, and probably all of the templates packed into one plugin for ease of management. My first plan would be to make Ansible do everything on the back end and have a php button kick it off. There are probably a bunch of weaknesses in the strategy, but they were so small that Redhat bought Ansible Inc. so they can use Ansible as part of the new base for Satellite. https://www.redhat.com/cms/managed-files/09.2%20CloudForms% 2C-satellite-and-ansible-by-Red-Hat-Doing-More-Together.pdf This manual https://www.mediawiki.org/wiki/Manual:Wiki_family has a few different methods. Extensions are either in beta or not maintained. The Ultimate minimalist solution are symlinks and an array. Writing a program to writes another program perfectly every time is not something I know how to do just yet. Using git to upgrade all of the web code sounds like a good idea right now though. I think copying the WikiMedia method would make a little more sense because I have an account there and I see that it works and haven't heard any complaints recently. The whole thing is template based and is primed to be done by ansible which is also template based. I could try Drupal-style sites, but I never had good luck with Drupal. I am still going to bit by the fact that they will have to be private wikis that don't share most users except for the the farm administrators is going to add another issue potentially. I will also need to eventually get another factor of authentication in because people demand it, but there is probably something in PHP already. https ://www.mediawiki.org/wiki/Help:Two-factor_authentication already works apparently. I do need to figure out some failover so I don't have to babysit the thing too much and so I can upgrade the Operating System. I want to attempt this project, but I don't know if I know enough about Wiki Farms yet to start. Guess I can try it and fail a few times and I can tell you what I didn't know, but is there anything obvious other than marketing.

6 years

Code of conduct committee call for new members

by Amir Ladsgroup

Hello all, It's coming close to time for annual appointments of community members to serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee is a team of five trusted individuals plus five auxiliary members with diverse affiliations responsible for general enforcement of the Code of conduct for Wikimedia technical spaces. Committee members are in charge of processing complaints, discussing with the parties affected, agreeing on resolutions, and following up on their enforcement. For more on their duties and roles, see https://www.mediawiki.org/wiki/Code_of_Conduct/Committee <http://meta.wikimedia.org/wiki/Ombudsman_commission> This is a call for community members interested in volunteering for appointment to this committee. Volunteers serving in this role should be experienced Wikimedians or have had experience serving in a similar position before. The current committee is doing the selection and will research and discuss candidates. Six weeks before the beginning of the next Committee term, meaning 8th of April 2018, they will publish their candidate slate (a list of candidates) on-wiki. The community can provide feedback on these candidates, via private email to the group choosing the next Committee. The feedback period will be two weeks. The current Committee will then either finalize the slate, or update the candidate slate in response to concerns raised. If the candidate slate changes, there will be another two week feedback period covering the newly proposed members. After the selections are finalized, there will be a training period, after which the new Committee is appointed. The current Committee continues to serve until the feedback, selection, and training process is complete. If you are interested in serving on this committee or like to nominate a candidate, please write an email to techconductcandidates AT wikimedia.org with details of your experience on the projects, your thoughts on the code of conduct and the committee and what you hope to bring to the role and whether you have a preference in being auxiliary or constant member of the committee. The committee consists of five members plus five auxiliary members and they will serve for six months; all applications are appreciated and will be carefully considered. The deadline for applications is end of day on 5th of April, 2018. Please feel free to pass this invitation along to any users who you think may be qualified and interested. Best, Amir on behalf of the CoC committee

6 years

Re: [MediaWiki-l] Mediawiki Job queue not running

by Andrew Geary

I appreciate the support Brian and Greg. I am still receiving the same error message. PHP Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 196608 bytes) in /var/www/html/mediawiki/autoload.php on line 518 Brian - you clearly set the memory limit above the referenced number, so I'm not sure the issue. Any additional help would be appreciated. Thank you. Andrew * Listen to SEGs podcast, Seismic Soundoff * Andrew Geary | publications outreach editor +1.918.497.4615 | ageary(a)seg.org Society of Exploration Geophysicists (SEG) 8801 South Yale Ave, Ste. 500, Tulsa, OK 74137 USA -----Original Message----- From: Andrew Geary Sent: Monday, March 26, 2018 10:43 AM To: 'mediawiki-l(a)lists.wikimedia.org' <mediawiki-l(a)lists.wikimedia.org> Subject: Mediawiki Job queue not running I administer a public wiki - https://wiki.seg.org - and I am having issues with a jobs backlog. It's currently at 19,058 and counting. I have tried using runJobs.php, but I get this error message: PHP Fatal error: Allowed memory size of 157286400 bytes exhausted (tried to allocate 3846541 bytes) in /var/www/html/mediawiki/includes/objectcache/SqlBagOStuff.php on line 656 I have noticed I do not have the variable: $wgJobRunRate listed in my LocalSettings.php. Should I add this variable to my LocalSettings.php file? How can I address this error message? I believe the jobs backlog is contributing to a Translate extension error I am having, mentioned here - https://phabricator.wikimedia.org/T159947. I am running MediaWiki 1.26.2. The jobs back log started in November 2017. No changes have been made to my version of Mediawiki in that timeframe. Thank you. Best, Andrew Andrew Geary | publications outreach editor +1.918.497.4615 | ageary(a)seg.org Society of Exploration Geophysicists (SEG) 8801 South Yale Ave, Ste. 500, Tulsa, OK 74137 USA

6 years

[Cargo] Page column missing link?

by Milov Patel

Recently installed Cargo on 1.2.7 -- however the "Page" column is blank for our data table. Is there any reason that could be causing this?

6 years

New MediaWiki extension: TinyMCE

by Yaron Koren

Hi everyone, We're very pleased to announce the release of a new WYSIWYG extension for MediaWiki, "TinyMCE": https://www.mediawiki.org/wiki/Extension:TinyMCE As you can probably guess from the name, this extension lets you use TinyMCE, a popular (and open source) web-based WYSIWYG editor, to edit wiki pages and textarea fields within the PageForms extension. We have created this extension based on one called "VisualEditor", which is part of the BlueSpice package: https://www.mediawiki.org/wiki/Extension:VisualEditor_(BlueSpice) It is not related to the much-better-known extension also called VisualEditor, other than that they're both WYSIWYG editors. The BlueSpice VisualEditor extension was developed by a team at the company Hallo Welt!. Duncan then worked to turn this into a true standalone extension, while I helped with some of the more MediaWiki-related aspects of it. Why another WYSIWYG extension? This extension is not as good at editing wiki pages as VisualEditor (the better-known one). However, it has a number of advantages, most notably the fact that it's quite a bit easier to install, since it doesn't require any outside libraries or services - you just download the code, install it, and everything (hopefully) works. Another major advantage, for those who use the Page Forms extension, is that it's easily integrated into the textarea inputs of forms. Feel free to try this out on your wikis, and let us know on the talk page if you run into any issues. Yaron and Duncan

6 years, 1 month

Question about older extensions ?

by Rowe, Dolores A

Although MediaWiki 1.26.x family is older, we are still using it right now. I would like to use an extension that is no longer available on the distributor because of the version 1.26.x. Is there any way to get the older extension ?

6 years, 1 month

Re: [MediaWiki-l] Mediawiki Job queue not running

by Andrew Geary

Thank you for the responses Greg. I ran the code and received a slightly different message: PHP Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 196608 bytes) in /var/www/html/mediawiki/autoload.php on line 518 It calls a different file for the error. It did not run any job. Thanks for the troubleshooting. Andrew * Listen to SEGs podcast, Seismic Soundoff * Andrew Geary | publications outreach editor +1.918.497.4615 | ageary(a)seg.org Society of Exploration Geophysicists (SEG) 8801 South Yale Ave, Ste. 500, Tulsa, OK 74137 USA -----Original Message----- From: Andrew Geary Sent: Monday, March 26, 2018 10:43 AM To: 'mediawiki-l(a)lists.wikimedia.org' <mediawiki-l(a)lists.wikimedia.org> Subject: Mediawiki Job queue not running I administer a public wiki - https://wiki.seg.org - and I am having issues with a jobs backlog. It's currently at 19,058 and counting. I have tried using runJobs.php, but I get this error message: PHP Fatal error: Allowed memory size of 157286400 bytes exhausted (tried to allocate 3846541 bytes) in /var/www/html/mediawiki/includes/objectcache/SqlBagOStuff.php on line 656 I have noticed I do not have the variable: $wgJobRunRate listed in my LocalSettings.php. Should I add this variable to my LocalSettings.php file? How can I address this error message? I believe the jobs backlog is contributing to a Translate extension error I am having, mentioned here - https://phabricator.wikimedia.org/T159947. I am running MediaWiki 1.26.2. The jobs back log started in November 2017. No changes have been made to my version of Mediawiki in that timeframe. Thank you. Best, Andrew Andrew Geary | publications outreach editor +1.918.497.4615 | ageary(a)seg.org Society of Exploration Geophysicists (SEG) 8801 South Yale Ave, Ste. 500, Tulsa, OK 74137 USA

6 years, 1 month

vector.css for Flow

by Evans, Richard K. (GRC-H000)

Hello, I'm trying to implement an alternative (dark) color theme for vector and I'm having trouble with styling the discussion elements produced by the Flow extension. Basically, I am using this alternative css for Vector (modified from a Halo gaming website I think): https://www.mediawiki.org/wiki/User:Revansx/vector.css And you can see the issue (if you have applied the vector.css code to your own user page like it did) on any talk page. (The text is white due to the dark theme, and the Flow edit box is also white.. making white-on-white) Using the Elements view of the Developers Tools, I can see countless subtle places where I could start applying changes, but I thought I would ask here if anyone knows definitively which two element id's to assign a new color to in order to make the skin work. I would also be interested in other Vector.CSS styles that maintain the vector layout but provide different color themes. Thanks! -Rich

6 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l March 2018