Hey, we're currently considering an RFC regarding of what to do with
mbstring support in MediaWiki: https://phabricator.wikimedia.org/T129435
In a nutshell: mbstring is a PHP extension that adds support for Unicode
string operations. MediaWiki requires it to function, however not every PHP
install in existence has it. MediaWiki in those situations either creates
slow PHP-only replacements or just crashes. In the RFC, 2 possibilities are
discussed:
* MediaWiki requires mbstring and doesn't work without it.
* MediaWiki uses a polyfill library to consistently override all mbstring
functions if they're absent, at the cost of string operations being 10-100
times slower (basically, what it currently does but more consistently and
code is maintained by a third party).
We would like more input on this issue from third-party MediaWiki operators:
* Do you currently have mbstring installed?
* If not, how hard would it be for you to install it?
* Do you think it's worth it to force users to have mbstring in order to
guarantee good performance?
Please comment on the Phabricator task.
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hei folks,
looking at https://wiki.debian.org/MediaWiki the mediawiki-package for
Debian seems to be in not-so-good shape.
Debian is shipping 1.19 - Upstream Security support has ended, Debian
security seems to end soon.
We're running mediawiki on Debian for a small community project and I'm
thinking about our deploment.
We've been using mediawiki's tarballs for a few months now, but looking
at the patch-version our installation is outdated quite often. Thinking
about reason, I came up with this:
- Updating the tarball is unpleasant and cumbersome comparing to apt-get
upgrade
- The tooling for whining on an outdated installation is rather
non-existent. It's easy to overlook the issue.
- Updating an installation requires knowledge on how to deploy mediawiki
and its internals. It cannot be done by somebody familiar with Debian, only.
Using a debian package is very helpful - patching / upgrading is very
easy. Since apt is integrated into icinga, these issue do not get
overlooked that easy.
What do you thing about the situation?
Thinking about release intervals, Debian is way slower compared to
mediawiki - thus Debian's packages for mediawiki become outdated with
very high probability. Is there a chance to see debian packages built by
mediawiki some day soon?
Greetz,
yanosz
I have set up the Translate extension on my wiki. Everything works well except that the machine translation is very inconsistent. On some articles it will show the Apertium translation, but the majority of articles the box stays empty (only showing the "Add documentation" button). Does anyone know why this might be and how I could fix it so the machine translation appears for each unit?
Thank you,
Andrew
MediaWiki: 1.23.2
PHP: 5.5.9-1ubuntu4.14 (apache2handler)
MySQL: 5.5.47-0ubuntu0.14.04.1
Andrew Geary
ageary(a)seg.org
I'm running MW 1.25 and PHP 5.5.33 with mysql 5.5.
I'm having a problem with one of my locally hosted wikis. I got an email from a user that our site was down, and discovered that the backend mysql database had been overwhelmed with processes giving
LCStoreDB::finishWrite
as part of their info when I use show processlist; from the mysql prompt. There were also some very long-running processes like this
COMMIT /* LoadBalancer::commitMasterChanges 66.249.64.57 */
I closed access to the wiki by putting a die(); message at the top of LocalSettings.php. The number of mysql processes dropped, but the db was still not responsive. I then made what was probably a mistake by trying to kill processes in mysql. From reading up on why the killed processes are still there, it seems that killing a commit causes a rollback, which can be very slow... 3-4 hours later, it's still not cleared up. Now I see a bunch of processes that look like
INSERT /* MessageBlobStore::insertMessageBlob 66.249.75.103 */ IGNORE INTO `msg_resource` (mr_lang,m
From what I've read, it sounds like I have to just wait for the rollback to complete. But while I'm waiting... is there anything I should be doing with my configuration to avoid this happening in the future?
Thanks,
Jim Hu
=====================================
Jim Hu
Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
Hi,
MediaWiki 1.26.2
PHP 5.4.41 (apache2handler)
MySQL 5.6.27-76.0
ICU 4.2.1
Server OS Linux (32-Bit)
I am having a lot of difficulty, setting up a blacklist aside from the default Meta-Wiki one (I.e. https://meta.wikimedia.org/wiki/Spam_blacklist).
Following the examples here: https://www.mediawiki.org/wiki/Extension:SpamBlacklist#Examples
in LocalSettings.php I included the following lines:
$wgSpamBlacklistFiles = array(
"[[m:Spam blacklist]]",
"https://en.wikipedia.org/wiki/MediaWiki:Spam-blacklist"
);
But when I test this, by entering the links that are blacklisted in the English Wikipedia blacklist, they don’t get blocked. To make sure I was using the correct links, I tested them in the English Wikipedia sandbox where they were successfully blocked.
Additionally, according to the documentation, when “$wgSpamBlacklistFiles” is used, the blacklists are solely the ones defined in this array, so I deleted the link to the Meta-Wiki blacklist and tried inputting some junk link (I.e. "https://en.wikipedia.org/wiki/abc") in the array. From what I understand, no link should have blocked in such a scenario. But again the links defined in the Meta-Wiki blacklist were blocked. It appears that the “$wgSpamBlacklistFiles” is having absolutely no effect whatsoever.
No matter what I do, the Meta-Wiki blacklist continues to work, but none of the other blacklists I try to include, work.
I have even tried creating a similar blacklist page on my own Wiki to no avail. I also remembered to clear the cache before each try.
What am I missing?
Thanks in advance.
Regards,
I am trying to suppress the post save notice and cannot find the
documentation on it, I could have sworn that I had notes on this already
but I cannot locate them.
Thanks
This is the error:
Exception encountered, of type "Exception"
[8aa63dcf] [no req] Exception from line 54 of /var/www/html/extensions/FlaggedRevs/frontend/FlaggablePageView.php: FlaggablePageView has no context article!
Backtrace:
#0 /var/www/html/extensions/FlaggedRevs/frontend/FlaggablePageView.php(253): FlaggablePageView->load()
#1 /var/www/html/extensions/FlaggedRevs/frontend/FlaggedRevsUI.hooks.php(193): FlaggablePageView->addStableLink(boolean, boolean)
#2 /var/www/html/includes/Hooks.php(195): FlaggedRevsUIHooks::onArticleViewHeader(Article, boolean, boolean)
#3 /var/www/html/includes/page/Article.php(585): Hooks::run(string, array)
#4 /var/www/html/maintenance/rebuildFileCache.php(133): Article->view()
#5 /var/www/html/maintenance/doMaintenance.php(103): RebuildFileCache->execute()
#6 /var/www/html/maintenance/rebuildFileCache.php(158): require_once(string)
#7 {main}
Can any one explain?
Thanks
john
I want to create a login popup window in my wiki, so that the user does not
go to a different page to login. Instead, a window should appear on the top
of website for login sign up purposes.
Creating a window asking for username and password is easy, but I am having
difficulties with authenticating the data. I am not sure how to do it. I
think it can be easily done by including the mediawiki.api.login.js file
which is present in the /resources/src/mediawiki.api folder into the skin,
but how to implement the function within the script?
Thanks in advance for the help.
-Palash
Hi all,
I have a batch that every night uploads a pdf file (with same name) on
my mediawiki.
Is there a way to tell mediawiki (through a localSettings variable or an
extension) to keep only last n revisions of that file and automatically
delete the older ones (in order not to get my disk full).
thanks
Gabriele