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…
Hello,
The current logo of MediaWiki was adapted slightly more than fifteen years
ago and hasn’t changed since. This logo despite having the nice concept of
sunflower, is old. The sunflower represents the diversity, the constant
growth and also the wildness.
Among its biggest issues I can point out that it’s a bitmap picture so it’s
unusable in large sizes (like large posters) and it’s too realistic making
it unusable in small sizes.
Most, virtually all, software products use a simpler and more abstract
form. For example, docker, kubernetes, Ubuntu, VueJs, React, Apache Kafka,
and many more. It’s a good time for MediaWiki to follow suit.
My request is for changing the logo of MediaWiki and I have no plans or
interest in changing logo of any other project.
Please show your support, oppose or your comments in the discussion page.
You can also add more suggestions.
The discussion page:
https://www.mediawiki.org/wiki/Project:Proposal_for_changing_logo_of_mediaw…
Best
--
Amir (he/him)
Hello,
I have tried to restore one of my wiki sites for testing, because I've always learnt that a non-tested backup is a useless backup.
I have exported my database named pascal_wikidb using phpmyadmin on my host site and obtained an sql file.
Then I have tried to import this sql file on another database (on the same host site) named pascal_dbtest. I have had hard time doing it because the import function of phpmyadmin doesn't work well with lynx, but that is another story. Using Firefox, I managed to do it still with an error message (I don't remember this message and I cannot reproduce easily this operation); so I wasn't sure my restoration was complete.
I then imported pascal_dbtest and it sounded complete when looking at the sql file, except that there are only 5 "ALTER TABLE" in it, instaed of a few dozens in the file exported from pascal_wikidb. Anyway it's hard to compare at a manual glance.
So I changed the LocalSettings.php of my wiki site to have it pointing on pascal_dbtest instead of pascal_wikidb :
$wgDBname = "pascal_dbtest";
$wgDBuser = "pascal_testwiki";
$wgDBpassword = "Undiscloed_password"
I opened my wiki with the normal URL, I managed to log in, but I couldn't modify any page, when I try I get :
"Alert: HTTP/1.1 500 Internal Server Error"
then (this is a translation back to english, sorry)
«
A database request error occured. It could have been caused by something wrong in the software.
[1cd8b80a4379c26549677281] 2020-07-13 17:30:10: Fatal erreur of type "DBQueryError"
»
Is there any procedure to follow to restore a wiki installation from a database backup?
Or is it likely to be caused by a corruption in my database backup?
I precise that I almost eliminated the hypothesis of an error in the user's permissions on this database.
Thanks in advance for any answer
Regards
Pascal GRÉGIS
Hi,
I use the mediawiki API to download all pages of an arabic wiki
(mediawiki version 1.29.2). For download I used the PHP example code
provided on https://www.mediawiki.org/wiki/API:Parsing_wikitext .
To get an information about the images in the wikitext too, I use
prop='wikitext|images'
However, it seems that not all images embedded in the wikitext appear in
$result['parse']['images']
It seems that images which are embedded like [[صورة:H100.gif]] are
missing in the image list for a page.
Is that an intended behaviour or a mistake?
Best Sigbert
--
https://hu.berlin/skhttps://hu.berlin/mmstat3
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2020.07. This bundle is compatible with MediaWiki 1.33 or above
and requires PHP 7.2 or above.
Next MLEB is expected to be released in 3 months. If there are very
important bug fixes, we will do an intermediate release. Please give
us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar…
* sha256sum: 7334f6c0f4e00a451d976c81024c955061cffc3466d8a03fd223733992d0a2d5
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CleanChanges and LocalisationUpdate ==
* Localisation and maintenance updates.
== cldr ==
* Update to cldr 37.
== Translate ==
* Fixes to moving and deletion of translatable pages.
([[phab:T168591|Phab:T168591]])
* Improved escape sequence handling for the Android XML file format.
([[phab:T192062|Phab:T192062]])
* Display a help message when editing a translatable page source.
([[phab:T192052|Phab:T192052]])
* Translations are now published instead of saved, for consistency
with rest of MediaWiki. ([[phab:T131132|Phab:T131132]])
* Updated Google Translate integration ([[phab:T33695|Phab:T33695]])
* Patrolling of edits to translation pages is allowed.
([[phab:T151172|Phab:T151172]])
* Message index should now be more robust and issues like "the message
does not correspond to any message group" when translating should no
longer occur. ([[phab:T221119|Phab:T221119]])
* Ensure plural keyword other is always present in exports for yaml
and json. ([[gerrit:c/mediawiki/extensions/Translate/+/603470|Gerrit
Patch]])
* Interface changes to message validator code. If you have custom
validators, you need to migrate them to a new interface.
([[gerrit:c/mediawiki/extensions/Translate/+/604400|Gerrit Patch]])
* Translatable pages can now prevent wrapping of outdated (and in
future untranslated) units by using <translate nowrap> syntax.<!--
unescape for email -->([[phab:T256625|Phab:T256625]])
* Slight changes to Special:PageTranslation interface.
([[gerrit:c/mediawiki/extensions/Translate/+/610073|Gerrit Patch]])
== UniversalLanguageSelector ==
* SkinTemplateOutputPageBeforeExec is deprecated, use SkinAfterPortlet
instead. ([[phab:T253178|phab:T253178]])
=== Input Methods ===
* Added Baoulé tilde keyboard.
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
Hi everybody!
As you might have noticed, the Revision class is being hard deprecated in MediaWiki core 1.35 release. The class has been replaced with RevisionRecord as a part of MCR work and has been soft-deprecated in 1.31 release. You can find out more about deprecation process in [1]
In practice, this means that extensions using Revision will keep working with MediaWiki 1.35, but would start emitting a deprecation warning, causing your tests to fail if $wgDevelopmentWarnings configuration enabled (it is in WMF CI). After 1.35 is released, Revision class and fallbacks using it will start being removed from core, breaking extensions that are still using it.
In order to help you start the update process and prepare, DannyS has written a comprehensive migration guide available under [2]. If you have any questions, Platform Engineering Team(Core Platform Team) will be answering them and providing assistance. To reach us, please use any of the following methods of communication:
#wikimedia-cpt IRC channel. The best time to find CPT is during the office hours, the next time slot it July 23 16:00-17:00 UTC - that’s when you’re guaranteed to find assistance, but if this timing is not good for you, please feel free to drop your questions at any convenient time.
Phabricator with #core-platform-team tag
Here on this email thread
Best regards.
Petr Pchelko
Senior Software Engineer, Core Platform Team
1. https://www.mediawiki.org/wiki/Stable_interface_policy#Deprecation_process <https://www.mediawiki.org/wiki/Stable_interface_policy#Deprecation_process>
2. https://www.mediawiki.org/wiki/Manual:Revision.php/Migration <https://www.mediawiki.org/wiki/Manual:Revision.php/Migration>
Hello,
Today the Wikimedia Foundation would like to introduce a new community
blog. It's called "Diff" (diff.wikimedia.org) and is a blog by – and
for – the Wikimedia volunteer community to connect and share
learnings, stories, and ideas from across our movement. We'd like to
encourage you to learn more about Diff and how it can help you in
sharing and learning from your fellow Wikimedians.
Everyone is invited to contribute!
https://diff.wikimedia.org/2020/07/14/welcome-to-diff-a-community-blog-for-…
The name “Diff” is in reference to the wiki interface that displays
the difference between one version and another of a Wikipedia page. It
also reflects the “difference” our communities and movement make in
the world every day.
For some background, Diff builds on lessons and experiences from the
Wikimedia Blog, the Wikimedia Foundation News, and Wikimedia Space;
previous posts from these channels are archived on Diff. The channel
is primarily intended for community-authored posts, in which
volunteers can share their stories, learnings, and ideas with each
other.
Diff offers a simple and accessible editorial process, moderated by
Foundation communications staff and open to volunteers, to encourage
participation from all — especially emerging and under-represented
communities. Additionally, content on Diff can be written and
translated into languages to reach a wide audience. Diff also has a
code of conduct and comments can be flagged and moderated.
Still curious to learn more?
https://diff.wikimedia.org/2020/07/14/welcome-to-diff-a-community-blog-for-…
Yours,
Chris Koerner (he/him)
Community Relations Specialist
Wikimedia Foundation
Hello.
(Apologies for cross-posting, and that you are likely not reading this
message in your native language: translations of the full announcement may
be available on Meta [1], and will be posted to all the wikis in the next
few days. Please consider helping with translations in the meantime.
Thanks!)
The Wikimedia Foundation Board of Trustees has approved a new sister
project, temporarily titled "Abstract Wikipedia" [2].
Its goal is to generate baseline encyclopedic content in a multilingual
fashion, allowing more contributors and more readers to share more
knowledge in more languages. You can learn more on Meta [1] and can also
join the new dedicated mailing list [3].
Talk to you soon!
[1]
https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia/June_…
[2] https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia
[3] https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
--
Erica Litrenta
Manager, Community Relations Specialists
https://meta.wikimedia.org/wiki/User:Elitre_(WMF)
On March 30, we announced that we were temporarily pushing back the release
of MediaWiki 1.35 due to uncertainty resulting from the COVID-19 pandemic.
We are now ready to begin the process of moving forward with the release.
The first step is cutting the release branch, REL1_35, which will occur on
Monday, July 13.
We will then be in "pencils down" mode: developers will stop targeting
MediaWiki 1.35 for new features. Instead, any new features would continue
to be applied to master and would target MediaWiki 1.36 or later. The only
work that would continue towards MediaWIki 1.35 would be blockers -
critical bug fixes or features close to completion that need to make it
into the release. This would happen by merging those patches into master
and then backporting them to the REL1_35 branch.
We anticipate that MediaWiki 1.35 will be released at the beginning of
August.
We appreciate your patience in these difficult times. Wishing you safety
and health,
Cindy