Re: [Wikitech-l] Bingle/Bugello broken post-Bugzilla upgrade
On 14 February 2014 02:50, Arthur Richards aricha...@wikimedia.org wrote: The only other thing I can think of is my original theory of an issue with the out of date Python Requests library. Anybody else have ideas? python-requests bundles it's own cacert list (although the ubuntu .deb version might use the central certificate store - not sure about that), which might be outdated. Some older cacert lists have issues with RapidSSL certificates (this is an issue with the list bundled with httplib2, for example). Merlijn ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bingle/Bugello broken post-Bugzilla upgrade
python-requests bundles it's own cacert list (although the ubuntu .deb version might use the central certificate store - not sure about that), which might be outdated. Some older cacert lists have issues with RapidSSL certificates (this is an issue with the list bundled with httplib2, for example). We use pywikibot's httplib2 which solves the issue Merlijn mentions here. For requests though, the last commit message on their cacert.pem file makes me like your original thought that requests should be updated: https://github.com/kennethreitz/requests/blob/master/requests/cacert.pem ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Parsing templates into associative arrays or objects
Hello,
sorry for the maybe naïve question. Within an extension, is there a
specific method (via Parser class, for instance) or a more or less
direct way that could turn a template in a wikitext string into an
object or associative array.
Let's say:
{{Example|Name=John|Last=Smith}}
into:
{
Example: {
Name: John,
Last: Smith
}
}
Thanks,
--
Toni Hermoso Pulido
http://www.cau.cat
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
If I install the Visual Editor mediawiki extension on the Wiki that I manage here at my work and also setup Parsoid, will new pages be saved with Wikitext still? The documentation for the extension's installation mentions that after you install Visual Editor you won't be able to edit Wikitext pages, but you will be able to create new pages. It also mentions that with Parsoid you will be able to edit Wikitext pages again. This leaves unclear whether or not having Parsoid installed makes Visual Editor save new pages as Wikitext as well, or just previously existing pages. I'm thinking about letting folks try Visual Editor here, but I need to be able to work with Wikitext still as there are definitely some unusual things I do in Wikitext from time to time. Thank you, Derric Atzrott Computer Specialist Alizee Pathology ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
On 02/14/2014 11:32 AM, Derric Atzrott wrote: If I install the Visual Editor mediawiki extension on the Wiki that I manage here at my work and also setup Parsoid, will new pages be saved with Wikitext still? Yes. All content is currently stored as wikitext, so you are naturally able to use the wikitext editor to create pages or edit existing pages. In the longer term we are working on the ability to store HTML instead for new wikis, in which case it might become possible to run without Parsoid if you don't need a wikitext editor front-end. This is not going to happen over night and will just be an option, so no reason to worry. The documentation for the extension's installation mentions Do you have a link to this documentation? Thanks, Gabriel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
If I install the Visual Editor mediawiki extension on the Wiki that I manage here at my work and also setup Parsoid, will new pages be saved with Wikitext still? Yes. All content is currently stored as wikitext, so you are naturally able to use the wikitext editor to create pages or edit existing pages. In the longer term we are working on the ability to store HTML instead for new wikis, in which case it might become possible to run without Parsoid if you don't need a wikitext editor front-end. This is not going to happen over night and will just be an option, so no reason to worry. So right now, assuming I don't have Parsoid, Visual Editor creates pages in Wikitext, it just can't edit previously existing pages? I would assume that this also means that without Parsoid if I edit a page in the regular Wikitext editor, I won't be able to use Visual Editor with it anymore. The documentation for the extension's installation mentions Do you have a link to this documentation? I was reading this page: https://www.mediawiki.org/wiki/Extension:VisualEditor Thank you, Derric Atzrott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
On 02/14/2014 12:47 PM, Derric Atzrott wrote: If I install the Visual Editor mediawiki extension on the Wiki that I manage here at my work and also setup Parsoid, will new pages be saved with Wikitext still? Yes. All content is currently stored as wikitext, so you are naturally able to use the wikitext editor to create pages or edit existing pages. In the longer term we are working on the ability to store HTML instead for new wikis, in which case it might become possible to run without Parsoid if you don't need a wikitext editor front-end. This is not going to happen over night and will just be an option, so no reason to worry. So right now, assuming I don't have Parsoid, Visual Editor creates pages in Wikitext, it just can't edit previously existing pages? I would assume that this also means that without Parsoid if I edit a page in the regular Wikitext editor, I won't be able to use Visual Editor with it anymore. VisualEditor is an HTML editor and doesn't know about wikitext. All conversions between wikitext and HTML are done by Parsoid. You need Parsoid if you want to use VisualEditor on current wikis. Gabriel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Parsing templates into associative arrays or objects
On 02/14/2014 04:00 AM, Toni Hermoso Pulido wrote: Within an extension, is there a specific method (via Parser class, for instance) or a more or less direct way that could turn a template in a wikitext string into an object or associative array. If you need both the parameters (including nested templates) and the rendered output, then one option is to use Parsoid for this by calling the web service: http://parsoid-lb.eqiad.wikimedia.org/ https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Transclusion_content Gabriel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
On 02/14/2014 10:39 PM, Gabriel Wicke wrote: VisualEditor is an HTML editor and doesn't know about wikitext. That single sentence explains so much. If you would have told me two years ago, I could have said wrong path, this will fail. (Of course, many would have protested and refused to listen to sound advice, but now we know the outcome.) What do you predict we will be using five years from now, in 2019? Plain old wikitext, VisualEditor, or some other path? -- Lars Aronsson (l...@aronsson.se) Aronsson Datateknik - http://aronsson.se ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Deployment and roadmap highlights - week of February 17th
Hello and welcome to the latest edition of the weekly Deployments and Roadmps update. For the full (and most up to date) schedule of planned deployments, see: https://wikitech.wikimedia.org/wiki/Deployments For next week, the highlights include: == Monday == NO DEPLOYS - US Holiday (Presidents' Day) == Tuesday == MediaWiki deploy window, currently following the 1.23 schedule * group1 to 1.23wmf14: All non-Wikipedia sites (Wiktionary, Wikisource, * Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites) ** https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap#Schedule_for_the_deployments ** https://www.mediawiki.org/wiki/MediaWiki_1.23/wmf14 == Thursday == MediaWiki deploy window, currently following the 1.23 schedule) * group2 to 1.23wmf14 (all Wikipedias) * group0 to 1.23wmf15 (test/test2/testwikidata/mediawiki) ** https://www.mediawiki.org/wiki/MediaWiki_1.23/wmf15 * Wikidata Repository code updated on testwikidata * Pending tests on testwikidata, Wikidata Repository code updated on * wikidata.org == Long term == You can see what is known to be upcoming here: https://wikitech.wikimedia.org/wiki/Deployments#Next_month As always, questions welcome, Greg -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | signature.asc Description: Digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Visual Editor and Parsoid New Pages in Wikitext?
On 14 February 2014 15:40, Lars Aronsson l...@aronsson.se wrote: On 02/14/2014 10:39 PM, Gabriel Wicke wrote: VisualEditor is an HTML editor and doesn't know about wikitext. That single sentence explains so much. If you would have told me two years ago, I could have said wrong path, this will fail. (Of course, many would have protested and refused to listen to sound advice, but now we know the outcome.) Thanks for your timely input. :-) We pointed out some of the (dozens of) reasons why a client-side implementation of the parser wasn't a workable solution when we made the choice to take this route; sorry you didn't notice that at the time. What do you predict we will be using five years from now, in 2019? Plain old wikitext, VisualEditor, or some other path? For new out-of-the-box MediaWiki installs? Almost certainly HTML. For existing legacy MediaWiki sites with sane quantities of extensions? Probably HTML for most. For WMF's currently-hosted sites? Probably wikitext, but it's possible that we'll have switched. J. -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
