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…
I have a wiki with a high volume of edits that need to be made (via API),
about 2-3 per second. The wiki can't keep up with them; there ends up being
a backlog of edits that need to be made as, e.g., attempts are being made
by 10 different bots to make 10 edits simultaneously (all to different
pages) and it takes a long time for them to save so that the bots can move
on to their next edits.
What's the best way to boost performance in the ways needed to reduce the
time needed to save edits, or to be able to save more edits per second by
concurrently running bots? Thanks, -- Starstruck
Hi Everyone,
Over the last few months, the Wikimedia Developer Advocacy team has been
working to improve technical documentation for the MediaWiki Action API
<https://www.mediawiki.org/wiki/API:Main_page>.
So far, we have:
- Started efforts to revise, simplify, and reorganize the MediaWiki
Action API pages on MediaWiki using a new documentation template for
sub-pages: https://www.mediawiki.org/wiki/API:Documentation_template
- Updated the API navigation-template:
https://www.mediawiki.org/wiki/Template:API
As we continue to make improvements to the technical documentation, we
could use your help to better guide our efforts!
Would you please take a few moments to complete the following survey and
share your opinions and experiences with us?
https://goo.gl/forms/Y5PGILb6b3awC3OJ2
*Notes about the Mediawiki Action API Survey:*
*Survey Period: *December 6, 2018 - January 6, 2019
*Privacy Policy:* This survey will be conducted via a third-party service,
which may subject it to additional terms. For more information on privacy
and data-handling, see the survey privacy statement
https://foundation.wikimedia.org/wiki/MediaWiki_Action_API_Survey_Privacy_S…
.
Thanks for your participation!
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
I’m sorry, but it appears that your issue is not directly related to MediaWiki. At the MediaWiki mailing list, we can only help you with issues related to MediaWiki. You’d probably be better off reaching out to someone else.
— Amanda
On Sunday, December 30, 2018, 12:45 PM, Jess Urbe <urbejessie(a)gmail.com> wrote:
I got a block bits came from wikkimedia but when we deploy in my wallet its bump error so I got to foxed it.that is a donation for the poor people
On Mon, Dec 31, 2018, 1:40 AM Amanda Quad <amandaquad(a)yahoo.com wrote:
Hi Jess,
I’m sorry, but we can’t help you fix your problem if you don’t tell us what your problem is! This message was blank except for the subject, so unfortunately we cannot help you further unless you provide us with more information.
— Amanda
On Saturday, December 29, 2018, 7:06 AM, Jess Urbe <urbejessie(a)gmail.com> wrote:
Sorry sir I thought that somebody has trying to hack my account,but its
just a test from my wallet developer n partners,thank you so much.this is a
big help to the people of tenement
Hi everyone,
I'm using MW version 1.29.2 on a shared hosting server (PHP 7.2.13 and MySQL 5.5.60). I've inadvertently exceeded the ISP's 1GB size limit of the database, with the result that I can't make any further changes. The wiki is still up and running, but I can't edit or delete content, no users can log in, and none of the PHP scripts will run from the maintenance shell extension. Because it's a shared hosting server, I don't have direct shell access to run PHP scripts.
My ISP has suggested that I reduce the size of the database using MySQL, so I can get it back under the threshold limit, and 'unfreeze' everything. In theory I should be able to delete unwanted old versions of pages in the usual way to free up space.
Using MySQL I've emptied the archive table (only 256 kb), but I need to be able to clear another 10 Mb or so without corrupting the database. What else can I delete safely to avoid crashing the wiki?
Thanks for any suggestions,
Brett
Hi Everyone,
A while back we applied hardening per
http://www.cyberciti.biz/tips/php-security-best-practices-tutorial.html
. Our php.ini includes the following:
;; #15 Limit PHP Access To File System
;; Allows recursive descent
open_basedir="/var/www/html/:/var/lib/php/"
When (1) the cache is stale, and (2) we run Special:Version, then part
of our security configuration is provided:
https://cryptopp.com/special-version.png
Is there any way to close that hole?
I'm OK with allowing Git to run, but I don't know how to do it short
of opening up /usr/bin to the web server.
Thanks in advance.
I'm trying to perform another 1.30 -> 1.31 upgrade. MariaDB version 5.5.60.
I've tried to run upgrade.php with our standard user (mwuser) and db
administrator (root). upgrade.php has always worked in the past using
our standard user (mwuser).
I've run "mysql_upgrade --user=root ..." again just in case because of
the hint below. Everything is OK.
What is the error and how do I fix it?
###################################
# php maintenance/update.php
MediaWiki 1.31.1 Updater
Your composer.lock file is up to date with current dependencies!
Going to run database updates for my_wiki-wikicryptopp_
Depending on the size of your database this may take a while!
Abort with control-c in the next five seconds (skip this countdown with --quick)
... 0
Turning off Content Handler DB fields for this part of upgrade.
Adding ipb_id field to table ipblocks ...[33b892a93ece4b42600cbd2b] [no req] W
ikimedia\Rdbms\DBQueryError from line 1457 of /var/www/html/w/includes/libs/rdbm
s/database/Database.php: A database query error has occurred. Did you forget to
run your application's database schema updater after upgrading?
Query: ALTER TABLE `mediawiki`.`wikicryptopp_ipblocks`
ADD ipb_auto tinyint NOT NULL default '0',
ADD ipb_id int NOT NULL auto_increment,
ADD PRIMARY KEY (ipb_id)
Function: Wikimedia\Rdbms\Database::sourceFile( /var/www/html/w/maintenance/arch
ives/patch-ipblocks.sql )
Error: 1142 ALTER command denied to user 'mwuser'@'localhost' for table 'wikicry
ptopp_ipblocks' (localhost)
Backtrace:
#0 /var/www/html/w/includes/libs/rdbms/database/Database.php(1427): Wikimedia\Rd
bms\Database->makeQueryException(string, integer, string, string)
#1 /var/www/html/w/includes/libs/rdbms/database/Database.php(1200): Wikimedia\Rd
bms\Database->reportQueryError(string, integer, string, string, boolean)
#2 /var/www/html/w/includes/libs/rdbms/database/Database.php(4194): Wikimedia\Rd
bms\Database->query(string, string)
#3 /var/www/html/w/includes/libs/rdbms/database/Database.php(4129): Wikimedia\Rd
bms\Database->sourceStream(unknown type, NULL, NULL, string, NULL)
#4 /var/www/html/w/includes/installer/DatabaseUpdater.php(683): Wikimedia\Rdbms\
Database->sourceFile(string)
#5 /var/www/html/w/includes/installer/DatabaseUpdater.php(751): DatabaseUpdater-
>applyPatch(string, boolean, string)
#6 /var/www/html/w/includes/installer/DatabaseUpdater.php(482): DatabaseUpdater-
>addField(string, string, string)
#7 /var/www/html/w/includes/installer/DatabaseUpdater.php(446): DatabaseUpdater-
>runUpdates(array, boolean)
#8 /var/www/html/w/maintenance/update.php(200): DatabaseUpdater->doUpdates(array
)
#9 /var/www/html/w/maintenance/doMaintenance.php(94): UpdateMediaWiki->execute()
#10 /var/www/html/w/maintenance/update.php(245): require_once(string)
#11 {main}
We use CentOS 7. Red Hat supplies antique software. It offers Media
wiki 1.21, if I recall correctly. It is what it is. We had to take on
maintenance of Mediawiki because we wanted to offer newer features
users. Skins and extensions sometimes need something newer than what
the platform provides.
We've managed to update Apache, Python and PHP using SCL
(https://wiki.centos.org/AdditionalResources/Repositories/SCL).
However, we cannot get the MySQL update to work. We are stuck at MySQL
5.5.60. MySQL 5.5.60 was released April 2018.
We can't upgrade to to MW 1.31 due to CentOS's MySQL. We tried to
install MW 1.31 but maintenance/update.sh died when trying to update
the database. We had to go to backup and restore the installation.
It is not just CentOS. Other OSes, like Ubuntu 14 LTS, are boxing
users. For example Ubuntu 14 provides MySQL 5.5.62
(https://packages.ubuntu.com/search?keywords=mysql-server). MySQL
5.5.62 was released October 2018.
Earlier I said "We've managed to update Apache, Python and PHP...".
SCL does not offer Composer. Composer is an entirely new set of
hardships. SCL probably does not offer Composer because dev tools have
no business being on a production server. While you may think
'composer update' is easy, it took us a day and a half to work around
all the problems and exceptions.
Please consider lowering the MySQL requirements. Most helpful would be
to lower and freeze all requirements for the next 3 or 5 years. A
requirements freeze would allow us (and other users) to upgrade
Mediawiki without the hassles and aggravations.
Thanks in advance.
