Project:Support desk/Flow/2017/07
| This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
| This page is an archive. |
| Please ask questions on the current support desk. |
Where can I hire someone to work on my wiki?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I'm in the U.S. Looking to hire someone to teach me how to tailor the wiki of my tiny personal site while we Skype. Is this a place to ask, or is there a better place to hire folks? Thanks. RedKnight7 (talk) 06:10, 1 July 2017 (UTC)
- You can take a look here: Professional development and consulting. AhmadF.Cheema (talk) 10:47, 1 July 2017 (UTC)
Anitmated gif don't work
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi there I created a few animated gifs using http://gifcreator.me/ some how they all work on a tablet, but not on a PC. When I change the px size at certain size they work again?
Thanks for any help in advance.
Cheers 178.17.171.221 (talk) 09:45, 1 July 2017 (UTC)
- You appear to have come at the wrong support forum. This support desk is related to the MediaWiki software which runs Wikis like Wikipedia. AhmadF.Cheema (talk) 10:45, 1 July 2017 (UTC)
- Thanks for your quick reply, but I don't not understand? I mean that the anitmated gif I created don't work(animate) on my Mediawiki page,when I look at the MediaWiki page using a PC, but the animation works when I look at my Mediawiki page using a tablet (iPad). Only when I set the size of the animated gif at a certain size using px they work, but then the size is so big that they won' fit on my Mediawiki page? 93.158.215.160 (talk) 11:09, 1 July 2017 (UTC)
- Does your unmentioned browser on your PC support displaying animated GIFs? Malyacko (talk) 22:31, 2 July 2017 (UTC)
- If you uploaded the gif to your wiki, it's possible that the thumb generated by MediaWiki doesn't respect the animation unless you embed it in its original size. Try using imagemagick for thumbnail generation. Ciencia Al Poder (talk) 17:54, 4 July 2017 (UTC)
[Solved] No emails from mediawiki
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I have noticed as of recently that I am not receiving emails from my mediawiki install (like confirmation emails and that kind of stuff).
I have checked that the emails are not going to spam, I do not see them there. I also tried changing the email the I am trying to use to a gmail account and I get emails on that account, in the spam folder though (the email I am trying to use is a company mail address created from MailCow; I don't know if that makes a difference or not).
I have opened up all smtp/imap ports on the server that I can think of.
Here is the information I have in my LocalSettings.php that look like the reference email settings.
$wgEnableEmail = true;
$wgEnableUserEmail = true; # UPO
$wgEmergencyContact = "kayla.manchette@devplateau.com";
$wgPasswordSender = "wiki@devplateau.com";
$wgEnotifUserTalk = true; # UPO
$wgEnotifWatchlist = true; # UPO
$wgEmailAuthentication = true;
Is there something I'm not realizing that I can add to make this work or is there something that I am forgetting to do so that emails can send?
Any help would be greatly appreciated. I have been trying to figure this out for a few days now, and it is getting very frustrating. 2602:306:BC83:3AA0:4BFF:FFF2:2A38:E508 (talk) 01:30, 2 July 2017 (UTC)
- Also wanted to post my main.cf for postfix:
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
myhostname = files.devplateau.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = mail.devplateau.com, localhost.devplateau.com, localhost
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
2602:306:BC83:3AA0:4BFF:FFF2:2A38:E508 (talk) 02:49, 2 July 2017 (UTC)inet_protocols = all
Cannot modify header information - headers already sent
"PHP message: PHP Warning: Cannot modify header information - headers already sent by (output started at /var/www/wiki/includes/actions/RawAction.php:115) in /var/www/wiki/includes/WebResponse.php on line 45
2017/07/04 11:22:00 [error] 548#548: *452244 FastCGI sent in stderr: "PHP message: PHP Warning: Cannot modify header information - headers already sent by (output started at /wiki/includes/actions/RawAction.php:115) in /wiki/includes/WebResponse.php on line 45" while reading upstream, request: "GET /index.php?title=User:AnnAngela/js/SendWelcomeMessage.js&action=raw&ctype=text/javascript&_=1499138833786 HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "zh.moegirl.org", referrer: "https://zh.moegirl.org/%E6%88%91%E4%BB%AC%E7%9A%84%E5%BE%81%E9%80%94%E6%98%AF%E6%98%9F%E8%BE%B0%E5%A4%A7%E6%B5%B7"
Using MW 1.28.2 Deletedaccount4567435 (talk) 15:59, 2 July 2017 (UTC)
- This problem still exist when output_buffering = 4096 in php.ini Deletedaccount4567435 (talk) 04:04, 4 July 2017 (UTC)
- And you can active to zlib.output_compression on php.ini 46.1.127.88 (talk) 20:31, 21 June 2019 (UTC)
Thumbnail creation error code: -1
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello, starting to use upload an image file function (png, jpg, ...).
The thumbnail fails to display on any page ...
"Error while creating Thumbnail. Error code: -1"
But the file is correctly uploaded and displayed if tryed.
Any idea ?
Jessie cloud hosted
MediaWiki 1.28.0
PHP Version 7.1.3
imagick module version 3.4.3RC1
ImageMagick release date 2017-05-23
Many thanks . Kiksesoi (talk) 18:39, 2 July 2017 (UTC)
- As a starting point see Project:Support desk/Flow/2016/07#h-Error_creating_thumbnail-2016-07-31T20:02:00.000Z. AhmadF.Cheema (talk) 04:37, 3 July 2017 (UTC)
- Thank you for your answer.
- As in the original topic, the server is hosted by OVH, and there is no pbl with small images.
- I've tried with these settings in LocalSettings.php :
- $wgImageMagickConvertCommand = "/usr/bin/convert";
- $wgUseImageResize = true;
- $wgUseImageMagick = true;
- $wgMaxShellMemory = 307200;
- $wgGenerateThumbnailOnParse = true;
- Doesn't change anything 82.236.43.243 (talk) 20:16, 3 July 2017 (UTC)
- The poster of the original topic believed that this issue is due to restrictions by OVH hosting. Have you checked this issue with them? AhmadF.Cheema (talk) 05:09, 4 July 2017 (UTC)
- https://community.ovh.com/t/mediawiki-vs-imagemagick-pas-de-miniatures/3567 Kiksesoi (talk) 20:29, 4 July 2017 (UTC)
- up ? .... Kiksesoi (talk) 18:02, 11 July 2017 (UTC)
- See Manual:How to debug and enable a debug log, it will display the imagemagick command used to generate the thumb, and maybe some error messages. You can try to execute the imagemagick command directly in the command line to see if it crashes. Ciencia Al Poder (talk) 10:33, 12 July 2017 (UTC)
I need help in developping a main page
Is there someone that can help to solve a problem for our new Wikinews project? I have asked two days ago overhere but no-one has responded yet. Our launch is scheduled for wednesday and it would be nice if we could present our new main page to the Dutch users on all other projects too. Ymnes (talk) 20:21, 2 July 2017 (UTC)
Migrating from 1.21. to 1.28.2
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I installed a fresh 1.28.2 Mediawiki on a new machine, and would like to import the (backup of) the database of a 1.21.1 instance of another machine in this new installation.
Will this work without any extra steps I need to take ?
Thanks. 193.173.195.13 (talk) 07:13, 3 July 2017 (UTC)
- Hi!
- Yes, this will work, but you will need to do the following: After you imported the database, make sure to run update.php to make the old database compatible with the new MW version.
- You also need to make sure that your images and, if you had some installed, your extensions and also the skins, which your users used, are still/again available in MW 1.28.
- See Upgrade and Manual:Moving a wiki for more information. 2003:72:6D25:6A00:6071:7417:8498:C113 (talk) 18:12, 3 July 2017 (UTC)
Api login result NeedToken
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
the procedure that I follow is this:
- require login token with this http request:
http://localhost/mediawiki-1.28.2/api.php?action=query&meta=tokens&type=login
- start a http Post request with a test page written in php:
<?php
$url = 'http://localhost/mediawiki-1.28.2/api.php?action=login';
$data = array('lgname' => 'Ulisse', 'lgpassword' => 'itaca', 'lgtoken' => "4ae0db11ef80a42e29411c39f8c8a3f8595a09e8+\\");
// use key 'http' even if you send the request to https://...
$options = array(
'http' => array(
'header' => "Content-type: application/x-www-form-urlencoded\r\n",
'method' => 'POST',
'content' => http_build_query($data)
)
);
$context = stream_context_create($options);
$result = file_get_contents($url, false, $context);
if ($result === FALSE) { /* Handle error */ }
var_dump($result);
The result is:
{
"warnings": {
"login": {
"*": "Fetching a token via action=login is deprecated. Use action=query&meta=tokens&type=login instead."
}
},
"login": {
"result": "NeedToken",
"token": "edc7dace7148aeeed21dbeb0a54b0d43595a0a1f+\\"
}
}
Anyone help me? 88.149.178.175 (talk) 09:13, 3 July 2017 (UTC)
- You need to provide the cookies returned from the meta=tokens api call Ciencia Al Poder (talk) 17:52, 4 July 2017 (UTC)
- Hello Ciencia...
- here my consideration to your suggested way:
- From debugger console of browser I see in the Header request the cookie available (in the header response i can't see nothing):
- my_wikiUserName=Ulisse; my_wiki_session=6hmabg9nl6dlp35uniik14ilt90p9t4v; my_wikiUserName=Ulisse; Ulisse_Stampa=filtri=Mandante: PRATICHE - Itacapital Kruk,N. Contratto: PRATICHE = 257,; my_wiki_session=6hmabg9nl6dlp35uniik14ilt90p9t4v
- Now I call the http://localhost/mediawiki-1.28.2/api.php?action=login providing in the header request the cookie read above but in the result nothing is changed. 88.149.178.175 (talk) 10:57, 5 July 2017 (UTC)
- ok now i'm logged in but i receive this json:
{"warnings": {"login": {"*": "Main-account login via action=login is deprecated and may stop working without warning. To continue login with action=login, see Special:BotPasswords. To safely continue using main-account login, see action=clientlogin."}},"login": {"result": "Success","lguserid": 4,"lgusername": "Ulisse"}}- But...when I redirect to the default page on http://localhost/mediawiki-1.28.2/ I see that I'm not logged in. How can I reach my goal? 88.149.178.175 (talk) 12:15, 5 July 2017 (UTC)
- @Ciencia Al Poder
- Nothing else? 88.149.178.175 (talk) 07:22, 11 July 2017 (UTC)
- If you're using the api, why do you redirect to a non-api entry point? Anyway, you should send the same cookies to be logged in. Ciencia Al Poder (talk) 11:25, 11 July 2017 (UTC)
- @Ciencia Al Poder I have my site and i want that the user of my site can login automatically in my mediawiki site.
- I think that my goal is reached using api...there are alternative to this way?
- In the next days I will try to send the cookies received. 88.149.178.175 (talk) 07:13, 13 July 2017 (UTC)
- You must ensure the cookie is sent to the user, but of course this means the cookie needs to be visible for both sites. The best way would be if both sites are on the same domain, like app.example.com and wiki.example.com, you can set the cookie with the "example.com" domain which will be visible to both sites. You probably want to adjust MediaWiki so their cookies follow the same domain pattern, otherwise they'll overwrite yours probably causing duplicate session IDs. Ciencia Al Poder (talk) 10:12, 13 July 2017 (UTC)
- Hi @Ciencia Al Poder
- Ciencia: If you're using the api, why do you redirect to a non-api entry point? Anyway, you should send the same cookies to be logged in.
- --> When I obtain the success result from the API Login, i'll try to send the cookie used in the login phase in a request to main page of my wiki but i loose the login state.
- Ciencia: You must ensure the cookie is sent to the user, but of course this means the cookie needs to be visible for both sites. The best way would be if both sites are on the same domain, like app.example.com and wiki.example.com, you can set the cookie with the "example.com" domain which will be visible to both sites. You probably want to adjust MediaWiki so their cookies follow the same domain pattern, otherwise they'll overwrite yours probably causing duplicate session IDs.
- --> My site and my wikiSite are in two different domain.
- How can I reach my goal? 88.149.178.175 (talk) 12:44, 17 July 2017 (UTC)
- You can't set a cookie for a domain different than the current domain being requested. The browser will reject it.
- The only way would be if your script is in the same domain than the wiki Ciencia Al Poder (talk) 18:05, 19 July 2017 (UTC)
Hi, i want to use APCU, but its keeps having troubles with login
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, i had installed APCu
Its in the phpinfo, i tried using Zend Opcache and it works but its not as fast as APCu, and if i dont use APCu, if i use DB cache or none, pages takes forever to load.
The problem is, if i set CACHE_ACCEL, the login loads pretty fast, also de pages, but cant login into accounts, it says that tipical error "Bla bla bla hijacking account bla bla bla", its pretty anoying, i had teste APCu code and it seems to work very well.
here is the code i used to test
apcu_add('idCliente', 1788, 0);
apcu_add('correo', 'juan.gzz.salz@gmail.com');
echo 'IdCliente session is: ' . apcu_fetch('idCliente');
echo 'correo session is: ' . apcu_fetch('correo');
apcu_clear_cache();
//I only wanted to test if it really clears fully the cahe for this two lines
echo 'IdCliente session is: ' . apcu_fetch('idCliente');
echo 'correo session is: ' . apcu_fetch('correo');
And everything worked so its not APCu, that proves it is installed,
i installed php_apcu-5.1.8-7.0-ts-vc14-x86,
also its the only compatible thats why i used that,
x64 doesnt seems to work on any XAMPP installation nor windows,
even with 64bits processor, also non thread safe doesnt work,
so im using thread safe.
PHP version is 7.0.3, but it happens the same in an installation with 5.6.12, (i installed the accurate APCu version and test it too there).
I dont want to use anything that doesnt is CACHE_ACCEL, pages last long.
let me know if there is something im missing, requeriments, my system, etc. 187.176.240.244 (talk) 05:28, 4 July 2017 (UTC)
- Are you using MediaWiki version > v1.27?
- Try setting:
$wgSessionCacheType = CACHE_DB;AhmadF.Cheema (talk) 13:32, 4 July 2017 (UTC)
Extension:CategoryPermissions
Good morning,
My question or rather concern is that in the extension: categorypermissions (Extension:CategoryPermissions)
I am able to deny permissions but not to give readers access to the categorys that own my wiki, could they help me? Jcanos (talk) 15:59, 4 July 2017 (UTC)
Fresh install - Apache log error
Hello everybody,
Sorry for my english, just a French guy :)
So, I just do a fresh installation of Mediawiki successfully (debian 8/apache2/php7/mysql).
I try to connect to the web site : OK. Create a dedicated user for articles : OK.
In fact, everything works perfectly.
But, when I checked the apache error log, I've got these lines, every time I click on a link :
[Tue Jul 04 18:42:15.154314 2017] [access_compat:error] [pid 19612] [client <ip_address>:57331] AH01797: client denied by server configuration: /var/www/Main_Page, referer: https://www.XYZ.fr/w/Special:RecentChanges
[Tue Jul 04 18:42:32.107500 2017] [access_compat:error] [pid 19611] [client <ip_address>:57334] AH01797: client denied by server configuration: /var/www/Main_Page, referer: https://www.XYZ.fr/w/Main_Page
[Tue Jul 04 18:46:44.439008 2017] [access_compat:error] [pid 19611] [client <ip_address>:57388] AH01797: client denied by server configuration: /var/www/Main_Page, referer: https://www.XYZ.fr/public_html/mediawiki/index.php?title=Special:UserLogin&returnto=Main+Page&returntoquery=
What can I do, to remove these errors ?
Mediawiki isn't installed in the DocumentRoot, but in a subdirectory
Thanks for your help Thom yorle 59 (talk) 17:07, 4 July 2017 (UTC)
Numbered alternative texts in links
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hey,
I´d like to know if it is possible to have a numbered list of links using # ?
Just like
[[Link|#Linkwithnumber1]]
[[Link|#Linkwithnumber2]]
I just want to get the same result as if the links would be an ordered list. Blumenfuchs (talk) 11:40, 5 July 2017 (UTC)
- 137.147.1.122 (talk) 12:03, 5 July 2017 (UTC)
# [[Link1]] # [[Link2]]
- Thank you, but I realized I described my problem wrong. If I get the numbers by using # in front of the link (but also by using <ol>...</ol>) the numbers aren´t bold and blue, which is why I´d like them to be part of the link. Blumenfuchs (talk) 13:41, 5 July 2017 (UTC)
- This can be done with CSS counters. Add this to MediaWiki:Common.css:This assumes you use the default MediaWiki styling for ordered lists, otherwise you may need to tweak the
.linked-nums { counter-reset: linked-nums; list-style: none; position: relative; } .linked-nums > li > a:first-child:before { content: counter(linked-nums) ".\00a0"; counter-increment: linked-nums; left: -3.2em; position: absolute; text-align: right; text-decoration: inherit; width: 3.2em; }
leftandwidthvalues. If your list items only contain a link, you can remove the:first-child. - Then you can use the
linked-numsclass on any ordered list to move the numbers to inside the links. Example:121.214.7.243 (talk) 14:12, 6 July 2017 (UTC)<ol class="linked-nums"> <li>[[Link|Linkwithnumber1]] <li>[[Link|Linkwithnumber2]] </ol>
Extension:CategoryPermissions
Good morning,
My question or rather concern is that in the extension: categorypermissions (Extension:CategoryPermissions)
I am able to deny permissions but not to give readers (group) access to the categorys that own my wiki, could they help me? Jcanos (talk) 13:04, 5 July 2017 (UTC)
- You should probably contact the maintainers/authors listed or open a task (read How to report a bug) Reception123 (talk) 18:56, 8 July 2017 (UTC)
- You know that, probe putting the wiki in English (the one that is Spanish) and it worked for me, what can I do? Jcanos (talk) 13:29, 10 July 2017 (UTC)
Next (or previous) page in a category?
We see how to go to a random page in a category. How can you go to the next (or previous) page in a category?
The order would be the same order as displayed in Category:Category name. Mike46V (talk) 13:25, 5 July 2017 (UTC)
HTTP Error with EXTENSION Visual Editor
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I´m working with EasyPHP. installation of Mediawiki worked like a charm. I'm trying to get Visual Editor working in my test enviroment on a local pc. But I'm getting a stranger error that says 127.0.0.1: The strange thing is that it´s loading up halfway, then it stop´s and shows the message above error.
See here:
http://imageshack.com/a/img923/8360/WOo2rT.png
My Parsoid is up and running when i go to 127.0.0.1:8000
http://imageshack.com/a/img924/5767/rR6ju9.png
I think there´s nothing wrong with my configuration files.
Setup:
- MediaWiki version: 1.28.2
- PHP version: 5.6.26
- MySQL version: 5.7.17
Sorry, But I'm getting pretty clueless overhere :-) Dwergman25 (talk) 14:41, 5 July 2017 (UTC)
- What comes up in the Parsoid log file? MacFan4000 (talk) 17:15, 5 July 2017 (UTC)
- Is it the log file in C:\Users\myusername\AppData\Roaming\npm-cache\_logs?
- -- -- --
- cho FOO test
- http://imageshack.com/a/img923/1769/cqPqEV.png
- -- -- --
- NPM test:
- http://imageshack.com/a/img924/928/gMaD4V.png
- -- -- --
- Be
- 0 info it worked if it ends with ok
- 1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\node.exe',
- 1 verbose cli 'C:\\Users\\myusername\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
- 1 verbose cli 'run',
- 1 verbose cli 'nsp' ]
- 2 info using npm@5.0.4
- 3 info using node@v6.11.0
- 4 verbose run-script [ 'prensp', 'nsp', 'postnsp' ]
- 5 info lifecycle parsoid@0.7.1~prensp: parsoid@0.7.1
- 6 silly lifecycle parsoid@0.7.1~prensp: no script for prensp, continuing
- 7 info lifecycle parsoid@0.7.1~nsp: parsoid@0.7.1
- 8 verbose lifecycle parsoid@0.7.1~nsp: unsafe-perm in lifecycle true
- 9 verbose lifecycle parsoid@0.7.1~nsp: PATH: C:\Users\myusername\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;c:\Users\myusername\node_modules\parsoid\node_modules\.bin;c:\Users\myusername\node_modules\.bin;C:\Users\myusername\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;c:\Users\myusername\node_modules\parsoid\node_modules\.bin;c:\Users\myusername\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\nodejs\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\Git\cmd;C:\Users\myusername\AppData\Roaming\npm
- 10 verbose lifecycle parsoid@0.7.1~nsp: CWD: c:\Users\myusername\node_modules\parsoid
- 11 silly lifecycle parsoid@0.7.1~nsp: Args: [ '/d /s /c', 'nsp check' ]
- 12 silly lifecycle parsoid@0.7.1~nsp: Returned: code: 1 signal: null
- 13 info lifecycle parsoid@0.7.1~nsp: Failed to exec nsp script
- 14 verbose stack Error: parsoid@0.7.1 nsp: `nsp check`
- 14 verbose stack Exit status 1
- 14 verbose stack at EventEmitter.<anonymous> (C:\myusername\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16)
- 14 verbose stack at emitTwo (events.js:106:13)
- 14 verbose stack at EventEmitter.emit (events.js:191:7)
- 14 verbose stack at ChildProcess.<anonymous> (C:\Users\myusername\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
- 14 verbose stack at emitTwo (events.js:106:13)
- 14 verbose stack at ChildProcess.emit (events.js:191:7)
- 14 verbose stack at maybeClose (internal/child_process.js:891:16)
- 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
- 15 verbose pkgid parsoid@0.7.1
- 16 verbose cwd c:\Users\myusername\node_modules\parsoid
- 17 verbose Windows_NT 6.1.7601
- 18 verbose argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\myusername\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "nsp"
- 19 verbose node v6.11.0
- 20 verbose npm v5.0.4
- 21 error code ELIFECYCLE
- 22 error errno 1
- 23 error parsoid@0.7.1 nsp: `nsp check`
- 23 error Exit status 1
- 24 error Failed at the parsoid@0.7.1 nsp script.
- 24 error This is probably not a problem with npm. There is likely additional logging output above.
- 25 verbose exit [ 1, true ] Dwergman25 (talk) 06:54, 6 July 2017 (UTC)
- It’s somewhere and it’s called parsoid.log MacFan4000 (talk) 10:17, 6 July 2017 (UTC)
- Hello MacFan4000,
- Thanks for your interest. I resolved this issue by starting over with an XAMPP environment. This issue is now no longer occuring.
- I have another issue though with an warning Parameter 1 error on the top while using Visual Editor. But i will look into it myself first.
- Thanks! Dwergman25 (talk) 12:01, 7 July 2017 (UTC)
- Hello,
- I'm reopening this topic just for other people to see because i found the solution to the problem above. The problem that the HTTP message is popping up is because you have to enable the curl extension in the php.ini (extension=php_curl.dll).
- After this the problem is solved. Dwergman25 (talk) 11:26, 11 July 2017 (UTC)
Fail to login on an article
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I succesfully login in https://en.wikipedia.org/wiki/Main_Page but when I navigate or search for the article I would like to edit it seems as if I am logged out. If I retry to login within the article it fails without any error message (I am still logged out) (article https://en.wikipedia.org/wiki/Dirichlet_distribution) 77.138.241.42 (talk) 03:10, 6 July 2017 (UTC)
- I would like to post a method to solve differential equation numerical. I need help do it.
- itomas98@yahoo.com 2602:30A:2CE0:93A0:C84B:4535:9603:7D72 (talk) 00:27, 7 July 2017 (UTC)
- The problem with login is probably related to T169261. The workaround is to login into a WMF wiki you haven't visited before, like for example https://species.wikimedia.org/ or any other, and then you should be logged in consistently. Ciencia Al Poder (talk) 08:51, 7 July 2017 (UTC)
APC or APCu with PHP7?
I want to install Mediawiki with php 7. 1, apache, and MySQL on a single server that I do not own.
Should I ask for APC or APCu extension? Which one is better? 73.237.238.122 (talk) 04:03, 6 July 2017 (UTC)
Searching uploaded documents
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
We are considering creating a knowledge base for our company using Mediawiki. It would include a range of introduction pages plus user created pages with topic information, pointers, how to's, lessons learnt etc. We also have an an extensive library of existing scanned pdf and doc documents we'd like to access through this.
Is there a way for MediaWiki to search for words within uploaded documents as well as wiki pages themselves - i.e. bring up the file: info page in the search result for the document containing the search word/phrase? This is an important function/requirement so want to make sure this is possible.
Thanks Bressa 23:22, 6 July 2017 (UTC)
- @Tessa.phillips Yes, that is part of MediaWiki. Reception123 (talk) 18:55, 8 July 2017 (UTC)
embed content in own MediaWiki
I want to embed content from Wikipedia on my own MediaWiki.
What I have learned so far is that I can use something like https://en.wikipedia.org/wiki/Vienna?action=render to get a plain (HTML) view of the content. But how can I embed this content (or parts thereof) in my own MediaWiki?
Can you please point me to the right place to ask or even an help article? C Wagner (talk) 11:44, 7 July 2017 (UTC)
- See Transclusion and Manual:$wgEnableScaryTranscluding. AhmadF.Cheema (talk) 12:02, 7 July 2017 (UTC)
- Thanks for pointing me to information about Transclusion. Form me it looks like a possibility to use Templates on my own wiki.
- What I am looking for is a way to embed content (not Templates) in my own wiki. C Wagner (talk) 17:40, 8 July 2017 (UTC)
- Transcluding works pretty much the same way for templates as well as "content" pages. As Manual:$wgEnableScaryTranscluding#Pure transclusion mentions, pages other than templates can also be transcluded.
- The main limitation is that apparently specific sections (instead of entire pages) cannot be selectively transcluded through this method. AhmadF.Cheema (talk) 09:46, 9 July 2017 (UTC)
- Thank you very much!
- This works very good so far. Do you know how to embed parts from Wikipedia in my own MediaWiki? (e.g. only the first line of an article) C Wagner (talk) 13:32, 13 July 2017 (UTC)
- Using MediaWiki API, it should be comparatively straightforward but unfortunately, as far as I know, there is no presently available native way of achieving this. AhmadF.Cheema (talk) 15:44, 13 July 2017 (UTC)
- Is there some kind of MediaWiki API support desk where I can find experts to discuss the possibilities? C Wagner (talk) 08:41, 14 July 2017 (UTC)
Problems with Transcluded Form
Hey team
Right, I've managed to transclude a form (or perhaps a "sub-form"?) into my main form which is used to configure a product (choose various options for it). I've noticed that if the main form uses a "show on select" statement in one of the dropdown inputs, it can be used to vary the inputs that are displayed on the transcluded form. However, it is not consistent.
On a normal form, if a value is set as default for an input, and there is an associated "show on select", then it is applied well. However, throw in a form that is transcluded, and the "show on select" seems to be ignored (the default value does not call up the associated input that should result if that value is selected).
To transclude the "sub-form", I use the following method:
On the main form:
|-
! Option with dependencies:
| {{{field|Option|input type=dropdown|values=first,second,third|default=first|mandatory|show on select=first=>123abc;second=>456def;third=>789ghi;}}}
On the "sub-form"
|- id="abc123""
! Title:
| <nowiki>{{{field|abc123|input type=dropdown|values=1,2,3,a,b,c|mandatory}}}</nowiki>
So when the main form is shown, the row specified by the id abc123 (which is on the "subform") is not shown. But if the value in the "Option" field is changed from first to second, and then back to first, then the row from the transcluded sub-form is shown. But only then, and not before.
I need help getting the show on select to work correctly according to the option that is shown in that field.
If more info or a more clear description is needed, drop me a message. Ayteecee (talk) 14:48, 7 July 2017 (UTC)
Probleme mit Vorlagen und Parametern
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hallo ich versuche mich grade in Vorlagengestalltung mit Parameter Übergabe.
Dazu habe ich mir mal die Navigationsleiste von den Artikel Rockmusik sowie der passenden Vorlage:Infobox Genre ausgeliehen.
Wenn ich beide in mein Projekt einfüge passt das irgendwie nicht mit der Vorlage siehe [1] und die Vorlage [2]
Es währe nett wenn mir einer mal erklären würde was ich falsch mache bzw. wo der Fehler liegt. 91.43.31.89 (talk) 15:12, 7 July 2017 (UTC)
- 1. You’re using an unsupported version of MediaWiki
- 2. You don’t have Extension:ParserFunctions installed, which is why #if isn’t being rendered. MacFan4000 (talk) 16:15, 7 July 2017 (UTC)
Problems Creating a Page
upon trying to create a page via URL method I get the following error.
The requested URL was rejected. Please consult with your administrator.
Your support ID is: 7985255496803100009.
the Mediawiki:noarticletext is not displayed.
I can perform a search and it will allow me to create the page that way.
any help would be appreciated. Thank you.
MediaWiki1.28.0
PHP5.6.30-0+deb8u1 (apache2handler)
MySQL5.5.55-0 Blyoak (talk) 16:21, 7 July 2017 (UTC)
Update MediaWiki
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hallo ich benötige Hilfe. Ich möchte gern meine MediaWiki auf die neuste Version Updaten, habe das aber noch nie gemacht und weis nicht wie genau ich da vorgehen. muss.
Zurzeit läuft meine Version auf 1.26.2. Ich währe sehr für Hilfe und Tipps dankbar. 91.43.8.234 (talk) 23:36, 7 July 2017 (UTC)
- For comprehensive instructions, see Manual:Upgrading.
- Additionally, you can ask here if there are more specific questions. AhmadF.Cheema (talk) 09:47, 8 July 2017 (UTC)
- Hallo!
- Den Upgrade-Guide gibt's auch auf deutsch: Manual:Upgrading/de.
- Als erstes solltest du dafür sorgen, dass du ein Backup hast. Und du solltest testen, ob du aus dem Backup auch tatsächlich wieder eine lauffähige Installation erstellen kannst.
- Ansonsten würde ich vorschlagen zuerst "nur" auf MediaWiki 1-27 zu aktualisieren. Das ist eine LTS-Version, die noch bis 2019 unterstützt wird. 1.28 und auch die bald erscheinende 1.29 dagegen werden nur kürzer unterstützt. Siehe Version lifecycle/de! 2003:72:6D74:4E00:7966:A7A1:99FD:7D9C (talk) 10:16, 8 July 2017 (UTC)
Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I'm getting the following error on a page that uses an infobox
Install details:
| Product | Version |
|---|---|
| MediaWiki | 1.27.3 |
| PHP | 5.6.30 (cgi-fcgi) |
| SQLite | 3.8.5 with full-text search support |
| ICU | 57.1 |
| Lua | 5.1.5 |
Extensions:
MSUpload 12.0 (b2cf0fa)00:03, 25 October 201
ParserFunctions 1.6.0
Scribunto – (a665621)00:03, 25 October 2016
Error:
[WWD--lER-kEAAkv4zC0AAAAt] /wiki/WIKI/mediawiki/index.php?title=IF020 MWException from line 208 of wiki/WIKI/mediawiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php: The lua binary wiki/WIKI/mediawiki/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable. 2A02:8084:6A00:E80:684C:6927:27D0:FBF9 (talk) 16:09, 8 July 2017 (UTC)
- Make sure wiki/WIKI/mediawiki/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic is readable writable and executable ie: chmod it to 775 or higher. MacFan4000 (talk) 16:26, 8 July 2017 (UTC)
- Thanks for that @MacFan4000 2A02:8084:6A00:E80:A404:B3F2:CF8D:F4E6 (talk) 17:30, 8 July 2017 (UTC)
Permanently Delete user accounts for wiki
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
My wiki is a private wiki set up for my company. I have created user accounts and set everyone a temporary password but after I did, noticed that emails were not sending correctly from my server. My users did not receive there account information.
I have since gotten sendmail working on the server, and I am trying to get everyone there account details now. Since the previous emails did not come through, I guess I need to remove the accounts that are on the wiki already, and create them again?
The only problem I am finding is how to remove those users. I installed the extension, UserMerge, which would work but I have other test accounts that I made to figure out the email and I would like them all gone.
Is there a way to permanently delete all users on the wiki. No one has put anything on the wiki yet, so it wouldn't be like I'm losing anything important. 2602:306:BC83:3AA0:758A:92D1:F95A:CD7C (talk) 17:37, 8 July 2017 (UTC)
- You could use Extension:UserMerge. You can merge all accounts into one (so ultimately delete them). Reception123 (talk) 18:52, 8 July 2017 (UTC)
Upgraded but Mediawiki internal error
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
As suggested I upgraded to the latest version on my Wiki http://www.modelhorsepedigrees.com/wiki/index.php?title=Main_Page
I've followed the instructions but now have the following appearing on my Homepage:
MediaWiki internal error.
Exception caught inside exception handler.
Set $wgShowExceptionDetails = true; and $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information
Where would I need to go to update these exceptions? They arent in the LocalSettings.php (which I copied as back up from the old version). Any help gratefully received. Pinnygik (talk) 12:38, 9 July 2017 (UTC)
- Following the instructions (setting $wgShowExceptionDetails and DBErrorBakctrace) would help us see the problem. Reception123 (talk) 15:48, 9 July 2017 (UTC)
- What the error is telling you to do is to input the following code:at the end of your LocalSettings.php file. These should be absent in the beginning, you need to put them there. AhmadF.Cheema (talk) 15:54, 9 July 2017 (UTC)
$wgShowExceptionDetails = true; $wgShowDBErrorBacktrace = true;
- Added the code (thanks) and it is now asking to run the Database scheme - how?? Full code return below:
- MediaWiki internal error.
- Original exception: [WWPhXUKT9EEACRJzQlQAAAEJ] /wiki/index.php?title=Main_Page DBQueryError from line 1054 of /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
- Query: SELECT page_id,page_namespace,page_title,page_restrictions,page_is_redirect,page_is_new,page_random,page_touched,page_links_updated,page_latest,page_len,page_content_model FROM `page` WHERE page_namespace = '0' AND page_title = 'Main_Page' LIMIT 1
- Function: WikiPage::pageData
- Error: 1054 Unknown column 'page_links_updated' in 'field list' (localhost)
- Backtrace:
- #0 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(912): Database->reportQueryError(string, integer, string, string, boolean)
- #1 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(1254): Database->query(string, string)
- #2 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(1322): Database->select(string, array, array, string, array, array)
- #3 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(321): Database->selectRow(string, array, array, string, array)
- #4 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(340): WikiPage->pageData(DatabaseMysqli, array, array)
- #5 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(376): WikiPage->pageDataFromTitle(DatabaseMysqli, Title, array)
- #6 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(459): WikiPage->loadPageData()
- #7 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(500): WikiPage->exists()
- #8 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(225): WikiPage->getContentModel()
- #9 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(212): WikiPage->getContentHandler()
- #10 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/actions/Action.php(96): WikiPage->getActionOverrides()
- #11 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/actions/Action.php(154): Action::factory(string, WikiPage, RequestContext)
- #12 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/MediaWiki.php(151): Action::getActionName(RequestContext)
- #13 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/MediaWiki.php(767): MediaWiki->getAction()
- #14 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/MediaWiki.php(512): MediaWiki->main()
- #15 /home4/fortomor/public_html/modelhorsepedigrees/wiki/index.php(43): MediaWiki->run()
- #16 {main}
- Exception caught inside exception handler: [WWPhXUKT9EEACRJzQlQAAAEJ] /wiki/index.php?title=Main_Page DBQueryError from line 1054 of /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
- Query: SELECT page_id,page_namespace,page_title,page_restrictions,page_is_redirect,page_is_new,page_random,page_touched,page_links_updated,page_latest,page_len,page_content_model FROM `page` WHERE page_namespace = '0' AND page_title = 'Main_Page' LIMIT 1
- Function: WikiPage::pageData
- Error: 1054 Unknown column 'page_links_updated' in 'field list' (localhost)
- Backtrace:
- #0 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(912): Database->reportQueryError(string, integer, string, string, boolean)
- #1 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(1254): Database->query(string, string)
- #2 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/libs/rdbms/database/Database.php(1322): Database->select(string, array, array, string, array, array)
- #3 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(321): Database->selectRow(string, array, array, string, array)
- #4 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(340): WikiPage->pageData(DatabaseMysqli, array, array)
- #5 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(376): WikiPage->pageDataFromTitle(DatabaseMysqli, Title, array)
- #6 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(459): WikiPage->loadPageData()
- #7 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(500): WikiPage->exists()
- #8 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(225): WikiPage->getContentModel()
- #9 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/page/WikiPage.php(212): WikiPage->getContentHandler()
- #10 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/actions/Action.php(96): WikiPage->getActionOverrides()
- #11 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/actions/Action.php(154): Action::factory(string, WikiPage, SkinFallback)
- #12 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/skins/SkinTemplate.php(278): Action::getActionName(SkinFallback)
- #13 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/skins/SkinTemplate.php(464): SkinTemplate->wrapHTML(Title, string)
- #14 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/skins/SkinTemplate.php(250): SkinTemplate->prepareQuickTemplate()
- #15 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/OutputPage.php(2336): SkinTemplate->outputPage()
- #16 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/exception/MWExceptionRenderer.php(178): OutputPage->output()
- #17 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/exception/MWExceptionRenderer.php(50): MWExceptionRenderer::reportHTML(DBQueryError)
- #18 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/exception/MWExceptionHandler.php(71): MWExceptionRenderer::output(DBQueryError, integer)
- #19 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/exception/MWExceptionHandler.php(137): MWExceptionHandler::report(DBQueryError)
- #20 /home4/fortomor/public_html/modelhorsepedigrees/wiki/includes/MediaWiki.php(540): MWExceptionHandler::handleException(DBQueryError)
- #21 /home4/fortomor/public_html/modelhorsepedigrees/wiki/index.php(43): MediaWiki->run()
- #22 {main} Pinnygik (talk) 20:23, 10 July 2017 (UTC)
- Try running Update.php from the maintenance folder. MacFan4000 (talk) 21:20, 10 July 2017 (UTC)
- Also I can visit the version page just fine. There is a notice about the default skin not being available. MacFan4000 (talk) 21:25, 10 July 2017 (UTC)
- The page_links_updated column is missing in our page table.
- According to Manual:Page_table#page_links_updated, this column has been added in MediaWiki 1.23. Running update.php as noted on Upgrade should actually solve this issue. 2003:72:6D17:600:5DE1:C8C6:F59B:6D06 (talk) 22:00, 10 July 2017 (UTC)
Warning: Cannot modify header information
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Referring to this Manual page: Manual:Errors_and_symptoms#Warning:_Cannot_modify_header_information_-_headers_already_sent_by_.28....29
Since upgrading to Mediawiki 1.27.1, I get literally thousands of error messages in the apache logfile, telling "[:error] [pid ...] [client ...] PHP Warning: Cannot modify header information - headers already sent in /var/www/mediawiki/includes/WebResponse.php on line 42, referer: " & URL of wikipage. I found the above mentioned manual page but I cannot identify the problem. There are no additional characters in LocalSettings.php nor WebResponse.php, the latter of course has not been modified by anyone. So, where can I find the exact file that causes the problem?
- Ubuntu 14.04.5
- Apache 2.4.7
- PHP 5.5.9
- MySQL 5.5.54
- MediaWiki 1.27.1 AnonymusGdpr (talk) 14:18, 9 July 2017 (UTC)
- Maybe try copying the LocalSettings.php entire text and save it into a new file (as was done in this very old Project:Support desk/Flow/2011/11#h-Cannot_modify_header_information-2011-11-01T14:13:00.000Z). AhmadF.Cheema (talk) 08:27, 10 July 2017 (UTC)
- Done, no difference. Thank you anyway. The source of the evil seems to be a spambot that attacks our wiki since a few days. As soon as I excluded the IP, there have been no more of the above error messages.
- On the other hand I can hardly believe that a bot may cause such sort of errors. Either the wiki does send a wrong header for whatever reason, then the error should be corrected. Or the headers are correct, then there should be no error message at all. AnonymusGdpr (talk) 13:12, 10 July 2017 (UTC)
- Indeed. If browsing the wiki normally doesn't give this sort of errors, you may look at the access or error logs for the exact URL the spammer is hitting.
- The header error is usually caused by PHP errors or warnings being sent to the client, before sending headers Ciencia Al Poder (talk) 17:53, 10 July 2017 (UTC)
Text and banners bump into infoboxes
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi! I have no clue what I might have done, but my text, all top level banners, even the blockquote box, bump right into the infobox, almost as if the infobox doesn't have any padding to its left. I thought maybe it was with the text not having padding to its right but it stops nicely around image boxes and other boxes. It appears only to be affecting infoboxes. I've checked all css files I can but everything looks identical to the source I copied from (everything used to work) so I'm sure it must have been something I changed... I just don't know what. If anyone could help that would be greatly appreciated! Bttfvgo (talk) 19:42, 9 July 2017 (UTC)
- It should be much easier to help if a direct link to your Wiki can be provided.
- As a starting point, (in case you didn't already know) you can try using your browser developer tools (Press F12 on Chrome). Using the select an element feature (Shortcut for Chrome: Ctrl + Shift + C) of these tools you can select an element by clicking on it with your mouse, and the developer tools panel will show all the .CSS rules associated with that element. You can check and uncheck specific rules through the panel to narrow down the rules which are causing the problems. AhmadF.Cheema (talk) 08:10, 10 July 2017 (UTC)
- Ahmad, you are the man! I use Chrome's developer's tools all the time for other things but never once thought about using it in this case. Sure enough, I was able to find out what the problem was! I added css for various foreign language versions of pages I'm adding but I haven't been changing any of the style names. For instance, English, Arabic, and French all use the styles ".infobox" and ".infobox_v2". What happens is the Arabic margin style reverses the margin normally used. (When I checked and unchecked that rule I could see the box flipping!)
- So that's why there wasn't any margin to the element's left. The duplicate margin call overrode the first margin call, and reversed the margins! I'll have to change names (possibly to ".infobox-ar" and ".infobox-fr") to ensure other infoboxes will continue to work, but I can't thank you enough!! Bttfvgo (talk) 04:29, 12 July 2017 (UTC)
Echo can't work
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The Echo extension can't work in mywiki(MW 1.28.2). The debug report shows $IP/extensions/Echo/extension.json does not exist!
I see REL1_29 and master branches have this file. Is this BUG? Or is my installation wrong? 星耀晨曦 (talk) 20:21, 9 July 2017 (UTC)
- The Extension:Echo page already mentions that for MediaWiki versions upto 1.28 the old method of installing extensions should be used which uses the following code line:
require_once "$IP/extensions/Echo/Echo.php";AhmadF.Cheema (talk) 20:43, 9 July 2017 (UTC)- Thank you, the extension has been able to work properly. 星耀晨曦 (talk) 02:42, 10 July 2017 (UTC)
temporary password doesn't work.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
temporary password doesn't work. Tried a couple times, waited several minutes but still doesn't work. One of the characters isn't clear but I have tried a few things. 72.34.128.250 (talk) 14:29, 10 July 2017 (UTC)
- Please disregard. I created an account under another email until I can resolve the issue with my main account. 72.34.128.250 (talk) 14:38, 10 July 2017 (UTC)
No CSS in IIS Installation
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have just done a Server 2012 installation which is now set up, the only problem is that there is no CSS on the Vector skin or any of the others.
I have already given the IIS user (IUSR) full control of C:/Windows/Temp, as well as editing $wgServer to the server name not just 'LocalHost' ($wgServer = "http://emsv22")
does anyone know where I am going wrong? Tekgecko (talk) 15:04, 10 July 2017 (UTC)
- See Manual:Errors and symptoms#The wiki appears without styles applied and images are missing Ciencia Al Poder (talk) 17:50, 10 July 2017 (UTC)
- Thank you, I used &debug=true at the end of my link and CSS is displayed correctly. I checked under dev tools on Chrome and the load.php is getting an Error 500 message when loading the page. Do you know the best way to troubleshoot this? Tekgecko (talk) 08:59, 11 July 2017 (UTC)
- look at the developer console of firefox/Chrome/IE by hitting F11, reload the page and see if you get any error (JavaScript errors in the console, or HTTP 500 errors on the network tab)
- You should also see that CSS pages come with a text/css content-type, otherwise the browser will refuse to treat them as CSS, which may indicate the page is giving an error or redirecting to a weird page... Ciencia Al Poder (talk) 11:28, 11 July 2017 (UTC)
- I checked the Dev tools in Chrome and can see there is a 500 error. I can also see it tries to load it as a style-sheet like you said under type. Do you have any idea what could be causing the error? I attached a screenshot (CSS is only working here because debugging is turned on):
- Error Screenshot Tekgecko (talk) 12:02, 11 July 2017 (UTC)
- Open the URLs that give the error on a new window and see if they display an error message. See Manual:How to debug for things you may need to change to display an error there if you only get a blank page. For example:
- Ciencia Al Poder (talk) 13:18, 11 July 2017 (UTC)
error_reporting( -1 ); ini_set( 'display_errors', 1 ); $wgShowExceptionDetails = true;
- Thanks, I don't get a blank page, just this "The page cannot be displayed because an internal server error has occurred." which is useless for finding out the error.
- Is there any way I can set it to load CSS individually on a permanent basis as a workaround? Tekgecko (talk) 13:41, 11 July 2017 (UTC)
- You can set $wgResourceLoaderDebug to true.
- You may look at error logs to see the cause of the error. Maybe on system logs you'll find the error. Ciencia Al Poder (talk) 14:54, 11 July 2017 (UTC)
- Ok where can I set that? Can't see it in local settings. I checked the IIS error logs before and there is nothing of interest. Tekgecko (talk) 15:08, 11 July 2017 (UTC)
- You have to set it in LocalSettings.php. Simply add
$wgResourceLoaderDebug = true;at the end of LocalSettings.php - For logging errors, see https://stackoverflow.com/questions/4764230/where-does-iis-7-5-log-errors Ciencia Al Poder (talk) 15:32, 11 July 2017 (UTC)
Settings with DNS
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
My server has no fixed ip address. Which settings are used for an external access with dynamic DNS (Domain Name Service)? Cdsailor (talk) 15:59, 10 July 2017 (UTC)
- You should have a dyndns service to use with your wiki, otherwise the IP address will be cached on every edit and will render broken links everytime your IP changes Ciencia Al Poder (talk) 17:49, 10 July 2017 (UTC)
- I have a dyndns service, but which settings are necessary in the LoalSettings.php? Cdsailor (talk) 20:03, 10 July 2017 (UTC)
- $wgServer must use the dyndns domain name Ciencia Al Poder (talk) 20:20, 10 July 2017 (UTC)
Installed MediaWiki on ISPConfig 3.1.5 with Nginx and PHP 7.0 FPM
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hey i installed mediawiki on my system with ispconfig and nginx and php7.0 fpm but i become error 500 on site?
i dont know to set the nginx directive correctly please help me!
regards ktownmods Ktownmods (talk) 20:41, 10 July 2017 (UTC)
- More information on a server error 500 should be available in the server error log.
- A tool, which can moore or less automatically create a working server configuration for you is available at https://shorturls.redwerks.org! Give it a try! 2003:72:6D17:600:5DE1:C8C6:F59B:6D06 (talk) 22:02, 10 July 2017 (UTC)
- The tool doesnt work always error 500
- Or query api... 2003:5D:A2E:56E0:81DE:8E00:82B1:77EC (talk) 09:34, 12 July 2017 (UTC)
- Your wiki must be working for the tool to work. You should look at the error logs first and sort the problem.
- google:Nginx+php+fpm+error+logs Ciencia Al Poder (talk) 10:31, 12 July 2017 (UTC)
- hey i used the tool now and become blank page or this [3]
- php fpm no errors in log and ngnix also Ktownmods (talk) 17:33, 15 July 2017 (UTC)
- A blank page usually points to a PHP error...
- The screenshot looks more or less good. With what you have there, calls to load.php obviously are not yet working correctly. It would be interesting to see, what the server gives you, when you try calling load.php. Actually, the server should not touch such calls at all. It should just return what load.php gives back - and that should be the CSS styles of the page. 2003:72:6D32:2F00:8CB3:9640:DA9D:358D (talk) 19:15, 15 July 2017 (UTC)
"Cite" extension not working
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The "Cite" extension already came installed with my MediaWiki version. The problem is that when I use the "ref" tag it comes out like plain text. I used all the tags, including "references /", and nothing.
Any help would be appreciated. Jvlopestheidiot (talk) 20:04, 11 July 2017 (UTC)
- The Cite extension is bundled but you need to enable it in LocalSettings.php. See installation instructions in Extension:Cite. If installed it should appear in Special:Version on your wiki. Ciencia Al Poder (talk) 10:34, 12 July 2017 (UTC)
Problem with Edit-Mode/Hooks.php
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
When calling any edit-page of my wiki, I get this error message
Warning: Parameter 1 to ConfirmEditHooks::showEditFormFields() expected to be a reference, value given in .../Hooks.php on line 195
Any idea what's going wrong, what to do?
TIA! Dirk Bechtel (talk) 10:23, 12 July 2017 (UTC)
- The ConfirmEdit extension on your wiki isn't compatible with your MediaWiki version. Please download and install a version that matches your MediaWiki version Ciencia Al Poder (talk) 10:28, 12 July 2017 (UTC)
- Thank you, but this doesn't help. The ConfirmEdit was delivered with the MW-Version, so it should be compatible. Nevertheless I installed again a fresh downloaded version of this extension, but still get the same error message. Dirk Bechtel (talk) 10:38, 12 July 2017 (UTC)
- What MediaWiki version are we talking about? Ciencia Al Poder (talk) 11:35, 12 July 2017 (UTC)
- I had the same problem with the extension Visual Editor.
- in the extension map there is probably a hooks.php file. Open it en delete the "&" at the public static function. 176.74.236.217 (talk) 15:03, 12 July 2017 (UTC)
- Thank you, same problem here with the Visual Editor, too! I've found VisualEditor.hooks.php, but there are many lines with public static function and "&" … I've no idea, where to delete one, could you perhaps specify this? Dirk Bechtel (talk) 15:19, 12 July 2017 (UTC)
- Don't know if you still need the answer but here it comes. In line 42 you have the following statement:
- - - - - - -
- public static function onBeforePageDisplay( OutputPage &$output, Skin &$skin ) {
- - - - - - -
- Removing the & before $output should be enough. So it will be:
- - - - - - -
- public static function onBeforePageDisplay( OutputPage $output, Skin &$skin ) {
- - - - - - - Dwergman25 (talk) 08:37, 13 July 2017 (UTC)
- It's version 1.28.2: http://www.dirk-bechtel.de/wiki/index.php?title=Spezial:Version
- With disabled ConfirmEdit it works fine (but I had 3 Spam-User within 20 minutes).
- And I also get an error message with VisualEditor, which I had to disable. Dirk Bechtel (talk) 15:04, 12 July 2017 (UTC)
- Ugh, PHP 7.1. Yes, this is a known problem. See T153505.
- You need to do a change similar to https://gerrit.wikimedia.org/r/#/c/329341/2/includes/EditPage.php
- Sadly, it hasn't been backported to 1.28 Ciencia Al Poder (talk) 15:31, 12 July 2017 (UTC)
- Ah, okay - thank you! So I've I little work for tomorrow … Dirk Bechtel (talk) 15:40, 12 July 2017 (UTC)
- It is just a warning, it shouldn't affect functionality and can be ignored. 110.149.123.63 (talk) 10:28, 14 July 2017 (UTC)
- But you'll have to edit php.ini to disable error reporting for WARNINGs, otherwise they'll be puked all over the page :) Ciencia Al Poder (talk) 11:01, 14 July 2017 (UTC)
What is the mediawiki extension powering this support desk
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Have looked through all the discussion and chat extensions but couldn't identify it. Is really nice. coyotegirl (talk) 15:34, 12 July 2017 (UTC)
Upgraded to 1.28 and now my templates don't work
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have just upgraded from 1.13 to 1.28 and my templates no longer work.
Can someone tell me what I am doing wrong please.
The template is as follows:
{{{name}}} {{{surname}}}
[[Image:{{{name}}}_{{{surname}}}.jpg|right|border|frame|10px|{{{name}}} {{{surname}}}]]
Given Name: {{{name}}} {{{surname}}} Sex: {{{sex}}}
Parents
{{#vardefine: i | 1
}}{{#dowhile:
| |
{{
#vardefine: i
| Expression error: Unrecognized punctuation character "{".
}}
}}
{{#vardefine: i | 1}}
{{#vardefine: j | 1}}
{{#while:
| |
- {{{ sname{{#var: i }} }}}, married on Unknown
- Children{{#vardefine: j | 1}}{{ #dowhile:
| |
- None
{{ #vardefine: j | Expression error: Unrecognized punctuation character "{".
}} }}
{{ #vardefine: i | Expression error: Unrecognized punctuation character "{".
}} }}
And The result looks like this:
<<< I CUT OUT THE BIT THAT WORKS >>>>
Siblings {{#vardefine: i | 1 }}{{#dowhile:
| |
{{
#vardefine: i
| Expression error: Unrecognized punctuation character "{".
}}
}}
Partners {{#vardefine: i | 1}} {{#vardefine: j | 1}} {{#while:
| |
{{{ sname{{#var: i }} }}}, married on Unknown Children{{#vardefine: j | 1}}{{ #dowhile:
| |
None
{{ #vardefine: j | Expression error: Unrecognized punctuation character "{".
}} }}
{{ #vardefine: i | Expression error: Unrecognized punctuation character "{".
}} }} 121.73.1.114 (talk) 02:51, 13 July 2017 (UTC)
- Looks like you need to install or enable some of your old extensions Ciencia Al Poder (talk) 16:44, 13 July 2017 (UTC)
- Thanks - I will give it a go 121.73.1.114 (talk) 21:29, 13 July 2017 (UTC)
- Please see my post above ----- Call to undefined method Message::escape() on Loops extension 121.73.1.114 (talk) 05:02, 15 July 2017 (UTC)
- After upgrading to MediaWiki v1.28 did you update your extensions too, especially Extension:Loops? AhmadF.Cheema (talk) 08:29, 15 July 2017 (UTC)
- Yes I did. 121.73.1.114 (talk) 09:20, 15 July 2017 (UTC)
- What is the exact "Call to undefined method..." error that you are getting? Can you confirm it is related to Extension:Loops? AhmadF.Cheema (talk) 09:24, 15 July 2017 (UTC)
- <cut>PHP message: PHP Fatal error: Call to undefined method Message::escape() in <cut>/Loops.php on line 360" while reading response header from upstream, client: <cut> 121.73.1.114 (talk) 09:36, 15 July 2017 (UTC)
- <Bounce> Anyone got an answer? 121.73.1.114 (talk) 22:01, 16 July 2017 (UTC)
- This was fixed in rELOOf9fe1ad758a7447a3c96f8c3ae9ce407095c8d20. You should try to download the latest version (for MediaWiki 1.29 or master) because 1.28 is broken. Ciencia Al Poder (talk) 19:00, 19 July 2017 (UTC)
- Thank you - I have downloaded and installed 1.29 and installed the extensions, I ran the upgrade.
- Now I am receiving the following message
- "Maximum number of loops have been performed"
- I have tried to set the loops to the limits of phps environment by putting the following in LocalSettings.php
- ExtLoops::$maxLoops = -1;
- Am I doing the right thing??? 121.73.1.114 (talk) 22:44, 19 July 2017 (UTC)
- Reading the code, ExtLoops::$maxLoops = -1; should work, yes. Does it still break? You may need to purge the page (for example, by editing the page again and saving without doing modifications) Ciencia Al Poder (talk) 09:39, 20 July 2017 (UTC)
- I am still having great trouble with this.
- I am unable to edit a page I receive the following error
- [error] 2401#0: *18 FastCGI sent in stderr: "PHP message: PHP Fatal error: Maximum execution time of 120 seconds exceeded in /mediawiki/includes/parser/Preprocessor_DOM.php on line 1170" while reading response header from upstream, client: <CUT>, request: "POST /mediawiki/index.php?title=<CUT>&action=submit HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "helium", referrer: <CUT> 121.73.1.114 (talk) 22:31, 20 July 2017 (UTC)
- Either your server is too slow, or there's something stuck in one of the MediaWiki scripts. Maybe removing the limit in the loops extension was not a good idea after all, it probably causes an endless loop somewhere. You should review the logic of your loop templates to find where the problem is. Ciencia Al Poder (talk) 08:55, 21 July 2017 (UTC)
- Strange it should be a logic problem as those templates worked fine in 1.13 121.73.1.114 (talk) 09:07, 21 July 2017 (UTC)
How to set flow active for non-logged in users
The flow text entry box (which I'm typing in now) is inactive on my install for users logged out. Though on your setup here, users not logged in can still use the system (though it captures their IP addresses instead).
I've tried protecting the page for 'all users' (i.e. setting all users so they can edit) but this doesn't make any difference. I've also looked through all the published settings/switches for flow but am unable to locate one which allows me to set flow as available on a talk page for users whe not logged in.
Please, do you know how I can achieve the same as you have here. coyotegirl (talk) 09:51, 13 July 2017 (UTC)
- When you protect a page for all users, you're effectively removing the ability to edit to all users (except users with the editprotected right, usually sysops) Ciencia Al Poder (talk) 16:43, 13 July 2017 (UTC)
- Thanks, though still not understanding this as the option in the protect page wizard under edit is to 'allow all users' (presumably to edit and maybe by implication, to also use the Flow messaging text box). So when I'm logged in as a user I can use the messaging system. I just tested this and set the protect options to admins only and now whe logged in as a user I get a msg saying that only admins can use.
- The thing is though that seemingly visitors not logged in as not counted as users and so are not able to use the Flow messaging box. But there must be another way of letting them access and use it as the Flow system on this support site allows such use but logs IP addresses instead.
- It's this setting that I'm looking for. coyotegirl (talk) 17:06, 13 July 2017 (UTC)
- If logged-out users can't edit or create pages on your wiki, they'll be unable to write on flow boards. I suspect your wiki is blocked for unregistered users. Ciencia Al Poder (talk) 17:11, 13 July 2017 (UTC)
- Thanks, good idea - let me check that. coyotegirl (talk) 17:13, 13 July 2017 (UTC)
- BRAVO Cienca!!! :) Thankyou! That's what is was. What my plan had been is to lock down the public side of the wiki so that anon visitors can read all pages (and not edit them), but also in addition, are able to enter some comments on one particular Flow page.
- Is there anyway I can achieve this. The only other option I can think of (on a simple to use level for anon visitors) is to link them to a google document page (so they can enter relevant info there). I just thought it would be so much nicer and cleaner to set things up so they can enter comments on a single wiki page, set with relevant privileges. coyotegirl (talk) 17:22, 13 July 2017 (UTC)
- Unfortunately, it appears that Flow doesn't add specific rights for replying and creating new messages, and simply uses the edit right, so you can't configure specific rights for creating flow messages.
- Maybe you can allow everyone to edit, in general, and restrict edition on namespaces other than Thread and talk pages with Extension:Lockdown. Ciencia Al Poder (talk) 20:10, 13 July 2017 (UTC)
- This article: Flow#What about IP.2Fanonymous editors.3F states:
- ===== _____ =====
- === What about IP/anonymous editors? ===
- Anonymous users are able to use Flow-enabled talk pages as any other user. However, subscriptions to individual topics, and notifications based on those subscriptions, will only be available to logged-in users.
- _____
- but I'm not getting that functionality. How can I debug this please. coyotegirl (talk) 17:13, 13 July 2017 (UTC)
Cannot create new account
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am using ConfirmAccount plugin. Whenever I try to approve a account I am getting a error:
Could not create directory "mwstore://accountcreds-backend/accountcreds-public/m/my/my
Anyone? Reesejohn291 (talk) 12:10, 13 July 2017 (UTC)
- See Extension talk:ConfirmAccount/2015#h-Could_not_create_directory_"mwstore://accountcreds-backend/accountcreds-public/w-2015-04-10T13:55:00.000Z. Apparently it's fixed in 1.27, and a new problem happens in 1.28 and 1.29 which may be solved by downloading a snapshot of the latest version of the extension (master or REL1_29) Ciencia Al Poder (talk) 16:41, 13 July 2017 (UTC)
IIS 8.0 Installation Issues
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
So I'm installing Mediawiki on a 2016 Server, the wizard starts ok, but at the end when it comes to generate localsettings.php, it fails and I get a 500 error, has anyone experience this before 199.15.170.116 (talk) 14:49, 13 July 2017 (UTC)
- Try to look at the system's Log Viewer to find a useful error message to try to diagnose the problem. See https://stackoverflow.com/questions/4764230/where-does-iis-7-5-log-errors Ciencia Al Poder (talk) 16:36, 13 July 2017 (UTC)
"Email confirmation" does not send a mail
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
Clicking "Confirm your email address" should send a mail to the user, but it looks no mail is sent.
I'm using sharing web hosting server via Bluehost.com, and it doesn't seem to send.
In this case, what should I do? What should I check? Breadncup (talk) 15:47, 13 July 2017 (UTC)
- MediaWiki will try to use the default settings for sending emails, as defined in php.ini. You can try to specify custom values in $wgSMTP, if you also have PEAR's Mail package available. Try to contact your hosting inquiring if they have mail settings configured in php.ini. Depending on how cheap your hosting is, it may have SMTP blocked (some may enable it on request) Ciencia Al Poder (talk) 16:32, 13 July 2017 (UTC)
- I've checked php.info and sendmail_path = "/usr/sbin/sendmail -t -i", SMTP = "localhost", and smtp_port = 25
- Would it be good enough?
- Or should I set $wgSMTP explicitly? Breadncup (talk) 18:20, 13 July 2017 (UTC)
- Set up a debug log file, perform an action that would send an email, and see if it displays something interesting about it.
- Anyway, a quick search gave me those results that suggest bluehost won't send emails outside of bluehost email accounts:
- Thanks, but the following code is working.
<?php mail("my.private.address@gmail.com","My subject","My message body"); ?>- ( Of course, my.private.address has changed to valid email address )
- The above code is running fine in the bluehost.
- I've tried to set up wgSMTP, but no luck so far. Breadncup (talk) 20:14, 13 July 2017 (UTC)
- I had similar. Couldn't get postfix working (which was default on server) but was able to get sendmail working. In send mail I have to add all the domains (of the email, like gmail.com, live.com) to the relay list of servers allowed otherwise it doesn't work. coyotegirl (talk) 16:52, 13 July 2017 (UTC)
Securing the images directory.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
We have a media wiki installation active directory integrated authentication. Everything is working as I would expect. The only issue is that without being logged in you can still browse to the /images directory and access all the files. Not that I care about general images, but thats also where all the uploads are stored. .doc, .xls, etc. How can I secure that directory for only authenticated users? 65.119.35.242 (talk) 16:34, 13 July 2017 (UTC)
- Ignore me, found the answer here: Manual:Image Authorization 65.119.35.242 (talk) 16:38, 13 July 2017 (UTC)
The error where Flows msging box won't load (stays greyed out) and cursor sits above as an egg timer
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, have seen this error referenced a few times and seems related to the default skin on the wiki. Happens with all browsers though chrome is the only one which clearly shows error messages:
=====
With Vector skin as default and not logged in I get the following (is similar for logged in) and the flow msging box loads (though states user needs to be logged in).
Navigated to https://www.domain.com/trans/Talk:Add_you_questions_here load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector:4 [WWedrLAvb04YOselnQiN1gAAAAg] 2017-07-13 16:19:56: Fatal exception of type "InvalidArgumentException"(anonymous function) @ load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector:4 load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1jzc8hv:154 Use of "Map-values" is deprecated. mw.Map#values is deprecated. Use mw.Map#get() instead.
With Monoblock skin as default and not logged in I get the following (is similar for logged in) and the flow msging box won't load (is blocked and when mouse coursor above stays as an egg timer).
Navigated to https://www.domain.com/trans/Talk:Add_you_questions_here load.php?debug=false&lang=en&modules=startup&only=scripts&skin=monobook:4 [WWcZIDEyNSNPu2fwh8dC8wAAAAk] 2017-07-13 06:54:24: Fatal exception of type "InvalidArgumentException"(anonymous function) @ load.php?debug=false&lang=en&modules=startup&only=scripts&skin=monobook:4 load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:154 Use of "Map-values" is deprecated. mw.Map#values is deprecated. Use mw.Map#get() instead. load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:176 Exception in module-execute in module ext.flow: load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:176 TypeError: Cannot read property 'static' of undefined TypeError: Cannot read property 'static' of undefined(…)logError @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:176handler @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:155fire @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:45self.fireWith @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:46self.fire @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:46mw.track @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:154(anonymous function) @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:161fire @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:45self.add @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:45promise.always @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:46runScript @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:161checkCssHandles @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:162(anonymous function) @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:162fire @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:45self.fireWith @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:46self.fire @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:46fireCallbacks @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:156addEmbeddedCSS @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:157(anonymous function) @ load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=1s3z16s:156
Please can you help me find what the error is that's happening. coyotegirl (talk) 16:37, 13 July 2017 (UTC)
- Closing this as have ascertained that it is only happening on chrome browser, which is an out of date version on Vista. coyotegirl (talk) 17:09, 13 July 2017 (UTC)
Wikibase DBUnexpectedError
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I had a mediaWiki page and I tried to import some infobox from Wikipedia. Following the instructions, I got some errors on templates regarding LUA and modules. The error was
Error de Lua en Módulo:Categorización_de_buenos_y_destacados en la línea 197: attempt to index field 'wikibase' (a nil value).
And when I tried to install wikibase (to avoid the index file wikibase being a nil value), my mediawiki page crash, getting
[770ec333b71d127fef7612b8] 2017-07-13 20:46:50: Excepción grave de tipo "DBUnexpectedError"
on any wiki page. If I turn on the debug, on all the debug data I get this error:
[167e584c7c1fa55b7b4aa159] /index.php/P%C3%A1gina_principal DBUnexpectedError from line 2810 of /var/www/mediawiki-1.28.0/includes/libs/rdbms/database/Database.php: DatabasePostgres::reportQueryError: Expected mass rollback of all peer databases (DBO_TRX set).
Backtrace:
#0 /var/www/mediawiki-1.28.0/includes/libs/rdbms/database/DatabasePostgres.php(246): Database->rollback(string)
#1 /var/www/mediawiki-1.28.0/includes/libs/rdbms/database/Database.php(912): DatabasePostgres->reportQueryError(string, string, string, string, boolean)
#2 /var/www/mediawiki-1.28.0/includes/libs/rdbms/database/Database.php(1254): Database->query(string, string)
#3 /var/www/mediawiki-1.28.0/includes/libs/rdbms/database/Database.php(1322): Database->select(string, array, array, string, array, array)
#4 /var/www/mediawiki-1.28.0/extensions/Wikibase/lib/includes/Store/Sql/SiteLinkTable.php(232): Database->selectRow(string, array, array)
#5 /var/www/mediawiki-1.28.0/extensions/Wikibase/lib/includes/Store/CachingSiteLinkLookup.php(151): Wikibase\Lib\Store\SiteLinkTable->getItemIdForLink(string, string)
#6 /var/www/mediawiki-1.28.0/extensions/Wikibase/lib/includes/Store/CachingSiteLinkLookup.php(77): Wikibase\Lib\Store\CachingSiteLinkLookup->getAndCacheItemIdForLink(string, string)
#7 /var/www/mediawiki-1.28.0/extensions/Wikibase/client/includes/LangLinkHandler.php(104): Wikibase\Lib\Store\CachingSiteLinkLookup->getItemIdForLink(string, string)
#8 /var/www/mediawiki-1.28.0/extensions/Wikibase/client/includes/LangLinkHandler.php(342): Wikibase\LangLinkHandler->getEntityLinks(Title)
#9 /var/www/mediawiki-1.28.0/extensions/Wikibase/client/includes/LangLinkHandler.php(365): Wikibase\LangLinkHandler->getEffectiveRepoLinks(Title, ParserOutput)
#10 /var/www/mediawiki-1.28.0/extensions/Wikibase/client/includes/Hooks/ParserOutputUpdateHookHandlers.php(132): Wikibase\LangLinkHandler->addLinksFromRepository(Title, ParserOutput)
#11 /var/www/mediawiki-1.28.0/extensions/Wikibase/client/includes/Hooks/ParserOutputUpdateHookHandlers.php(88): Wikibase\Client\Hooks\ParserOutputUpdateHookHandlers->doContentAlterParserOutput(Title, ParserOutput)
#12 /var/www/mediawiki-1.28.0/includes/Hooks.php(195): Wikibase\Client\Hooks\ParserOutputUpdateHookHandlers::onContentAlterParserOutput(WikitextContent, Title, ParserOutput)
#13 /var/www/mediawiki-1.28.0/includes/content/AbstractContent.php(501): Hooks::run(string, array)
#14 /var/www/mediawiki-1.28.0/includes/poolcounter/PoolWorkArticleView.php(139): AbstractContent->getParserOutput(Title, integer, ParserOptions)
#15 /var/www/mediawiki-1.28.0/includes/poolcounter/PoolCounterWork.php(123): PoolWorkArticleView->doWork()
#16 /var/www/mediawiki-1.28.0/includes/page/Article.php(651): PoolCounterWork->execute()
#17 /var/www/mediawiki-1.28.0/includes/actions/ViewAction.php(71): Article->view()
#18 /var/www/mediawiki-1.28.0/includes/MediaWiki.php(495): ViewAction->show()
#19 /var/www/mediawiki-1.28.0/includes/MediaWiki.php(289): MediaWiki->performAction(Article, Title)
#20 /var/www/mediawiki-1.28.0/includes/MediaWiki.php(851): MediaWiki->performRequest()
#21 /var/www/mediawiki-1.28.0/includes/MediaWiki.php(512): MediaWiki->main()
#22 /var/www/mediawiki-1.28.0/index.php(43): MediaWiki->run()
#23 {main}
I'm using those versions:
MediaWiki 1.28.0
PHP 7.0.18-0ubuntu0.16.04.1 (apache2handler)
PostgreSQL 9.5.7
Lua 5.1.5
How can I avoid this error? What is triggering? Is Postgres supported on wikibase?
I just want to add some infobox for the mediawiki page ): Feandoe (talk) 20:50, 13 July 2017 (UTC)
- If you're not going to use WikiData, just edit the module that's using wikibase and comment out/remove the logic where it's trying to access wikibase.
- I don't know about postgres support on wikibase, though. Ciencia Al Poder (talk) 07:37, 14 July 2017 (UTC)
- Thanks, I read the code and Postgres isn't supported on WikiBase. I tried to comment the lines that triggered the error, but the template didn't work. So, I will try to change to mysql http://www.winterrodeln.org/trac/wiki/MediaWikiPostgresqlToMysql Feandoe (talk) 14:21, 14 July 2017 (UTC)
Call to undefined method Message::escape() on Loops extension
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Just upgraded to 1.28 and have replaced the loops, loopfunctions and variables extensions with the new 1.28 ones but I am getting the following error
[error] 936#0: *53 FastCGI sent in stderr: "PHP message: PHP Fatal error: Call to undefined method Message::escape() in <cut>/mediawiki/extensions/Loops/Loops.php on line 360" while reading response header from upstream, client: <cut>
Anyone help me out with this please 121.73.1.114 (talk) 22:10, 13 July 2017 (UTC)
- This was fixed in rELOOf9fe1ad758a7447a3c96f8c3ae9ce407095c8d20. You should try to download the latest version (for MediaWiki 1.29 or master) because 1.28 is broken. Ciencia Al Poder (talk) 18:59, 19 July 2017 (UTC)
Creating New Page?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am planning to create a new page for my Boss who is World renowned Laparoscopic surgeon. Can anyone help me out here? Creativesgem (talk) 03:50, 14 July 2017 (UTC)
- See Help:Starting a new page. If you want to create a new page on Wikipedia, be sure to follow their rules about notability, etc Ciencia Al Poder (talk) 07:32, 14 July 2017 (UTC)
Имя учетной записи
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
- При регистрации учетной записи я указывал имя профиля "FD_KIM", но учетная запись создалась с именем "FD KIM", т.е. без нижнего подчеркивания, что привело к невозможности авторизации в мобильном приложении....
- Как сменить имя учетной записи на то, которое я указывал при регистрации?
- PS: форма регистрации не ругалась на наличие нижнего подчеркивания в имени профиля. FD KIM (talk) 06:26, 14 July 2017 (UTC)
- На самом деле нет. Эт показывается она без символа подчеркивания, таковы особенности вики.
- На самом деле, в базе ты с тем ником, который указал.
- А авторизация, проходит в обоих случаях, что вводи без подчеркивания, что с ним.
- Возможно, в мобилках есть какие-то заморочки, не могу проверить, так что точно не скажу. Aka sektor (talk) 00:46, 29 July 2017 (UTC)
- Which "mobile application" does this refer to and why exactly does login not work? AKlapper (WMF) (talk) 11:01, 14 July 2017 (UTC)
Error Saving edited System (i.e. MediaWiki:x) Pages
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I just upgraded my MediaWiki installation from version 1.23.1 to 1.28.2. I am also using PHP 7.1.6 and SQLIte 3.15.1.
Everything so far seems to be working ok except that we can no longer save edits for the MediaWiki:Sidebar and MediaWiki:Mainpage. I can navigate to MediaWiki:Mainpage and click Edit to bring up the edit box ok and the Show preview works. When I click Save Changes however I receive an Internal Error message:
Internal error
[bd5a9c5eda1b36d701550ed9] 2017-07-14 15:06:19: Fatal exception of type "Error"
The only information I could find on this issue was to check the permissions to make sure the user account has the editinterface permission.
My user account is a member of Administrators and Bureaucrats. When I look at the Special:UserGroupRight page in my wiki it indicates the Administrator group includes the editinterface, editprotected, editsemiprotected etc., permissions.
I am not extremely knowledgeable about the wiki/php/SQLIte software. Any assistance in fixing this is greatly appreciated. Joanne222 (talk) 15:16, 14 July 2017 (UTC)
- This could be due to an incompatibility of newer MediaWiki version with some older extension version.
- Try Manual:How to debug to get more detailed error description. AhmadF.Cheema (talk) 17:51, 14 July 2017 (UTC)
- Thank you for the debug instructions link. I added some of the debug calls to my LocalSettings.php file as indicated and the following was displayed in the Fatal Error area when I attempted to save changes to the MediaWiki:Mainpage page:
- 0623456c8d721035156ed27f] /wikilinc/index.php?title=MediaWiki%3AMainpage&action=submit Error from line 138 of C:\inetpub\wwwroot\WikiLinc\extensions\TitleBlacklist\TitleBlacklist.hooks.php: Call to undefined method Title::newFromRedirect()
- Backtrace:
- #0 C:\inetpub\wwwroot\WikiLinc\includes\Hooks.php(195): TitleBlacklistHooks::validateBlacklist(EditPage, string, string, string, string)
- #1 C:\inetpub\wwwroot\WikiLinc\includes\EditPage.php(1803): Hooks::run(string, array)
- #2 C:\inetpub\wwwroot\WikiLinc\includes\EditPage.php(1470): EditPage->internalAttemptSave(NULL, boolean)
- #3 C:\inetpub\wwwroot\WikiLinc\includes\EditPage.php(612): EditPage->attemptSave(NULL)
- #4 C:\inetpub\wwwroot\WikiLinc\includes\actions\EditAction.php(59): EditPage->edit()
- #5 C:\inetpub\wwwroot\WikiLinc\includes\actions\SubmitAction.php(38): EditAction->show()
- #6 C:\inetpub\wwwroot\WikiLinc\includes\MediaWiki.php(495): SubmitAction->show()
- #7 C:\inetpub\wwwroot\WikiLinc\includes\MediaWiki.php(289): MediaWiki->performAction(Article, Title)
- #8 C:\inetpub\wwwroot\WikiLinc\includes\MediaWiki.php(851): MediaWiki->performRequest()
- #9 C:\inetpub\wwwroot\WikiLinc\includes\MediaWiki.php(512): MediaWiki->main()
- #10 C:\inetpub\wwwroot\WikiLinc\index.php(43): MediaWiki->run()
- #11 {main}
- Also, will add that when I was performing the upgrade and following the instructions, I attempted to change the require_once extension calls to wfLoadExtension calls in LocalSettings.php and it would not work. I had to change them back to the require_once calls which I presume might indicate that I have done something incorrectly during my upgrade? The require_once calls work though.
- Thank you for your help. Joanne222 (talk) 18:19, 14 July 2017 (UTC)
- So I have made a little progress on this issue. When I did the upgrade, I copied the LocalSettings.php file as well as the extensions and images directories. After I extracted my new version into my website directory, I copied in and overwrote the LocalSettings.php, extensions and images directories with the old ones. I had to add some code to the LocalSettings.php file, but everything seemed to work ok except for the MediaWiki:x pages.
- Since the debugging was indicating the TitleBlacklist extension was an issue, I copied the new TitleBlacklist extension directory into my installation path replacing the old one that I had copied over during installation.
- I can now save the edited MediaWiki:Sidebar and MediaWiki:Mainpage pages.
- I still have the issue with the new extension calls not working so am using the require_once method still. I assume that must also be an extension issue as well?
- I attempted to use the entire new extension directory and contents instead of my old ones, but then my wiki website was not displaying at all so I only am using the new TitleBlacklist extension and all the reset are from my old version of 1.23.
- Please let me know if you have any suggestions or solutions.
- Thank you. Joanne222 (talk) 20:14, 14 July 2017 (UTC)
- You appear to be under the mistaken impression that wfLoadExtension is to be used because of the new MediaWiki core version. This has more to do with the extension files than with MediaWiki core.
- The newer method can only be used when an extension.json file is present in the extension directory. The older require_once method is deprecated and now wfLoadExtension method for enabling extensions is encouraged. Note that not all extensions are enabled using the new method as some extensions haven't been updated with the extension.json file.
- As all but one of your extension files are from the days of MediaWiki v1.23 and the extension.json files are absent from the extension directories, therefore the new method of calling extensions will not work for them.
- It is recommended that you upgrade all your extensions due to reasons of security and incompatibility with MediaWiki core. Upgrade the extensions one at a time, and then debug them to get a better idea of which extensions are causing fatal errors so that all the issues can be systematically resolved one-by-one. AhmadF.Cheema (talk) 23:09, 14 July 2017 (UTC)
- Thank you very much for the information and clarification on what drives the Extension call method. That definitely points me in the right direction. Joanne222 (talk) 13:52, 17 July 2017 (UTC)
- The original issue I posted about has been resolved. Thank you for your help.
- I have another issue now that I cannot solve. It seems to be the same issue posted here:
- https://www.mediawiki.org/wiki/Project%3ASupport%20desk/Flow/2016/12#h-Error%3A_1_cannot_start_a_transaction_within_a_transaction-2016-12-07T21%3A30%3A00.000Z
- by Dbeidle I tried some of things mentioned in that thread and the thread referenced in that post from here:
- https://phabricator.wikimedia.org/T88312
- I do not see where his issue was ever fixed. I am hoping that you can help me fix it with mine though.
- Specifically, I have an intermittent issue where we try to edit a page and when we save or preview it may or may not work. If we then Retry on the error page it might post then. I have turned on debugging information to capture what is happening. When the page fails to post the debugging message displayed is:
- [2e80a656914a00173f89ea4b] /wikilincluden/index.php?title=Counsel_Portfolio_Services&action=submit DBQueryError from line 1054 of C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
- Query: BEGIN
- Function: Database::query (MessageCache::loadFromDB(en)-big)
- Error: 1 cannot start a transaction within a transaction
- Backtrace:
- #0 C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\Database.php(912): Database->reportQueryError(string, integer, string, string, boolean)
- #1 C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\DatabaseSqlite.php(752): Database->query(string, string)
- #2 C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\Database.php(2718): DatabaseSqlite->doBegin(string)
- #3 C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\Database.php(851): Database->begin(string, string)
- #4 C:\inetpub\wwwroot\WikiLincluden\includes\libs\rdbms\database\Database.php(1254): Database->query(string, string)
- #5 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(485): Database->select(string, string, array, string)
- #6 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(408): MessageCache->loadFromDB(string, NULL)
- #7 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(330): MessageCache->loadFromDBWithLock(string, array, NULL)
- #8 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(932): MessageCache->load(string)
- #9 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(862): MessageCache->getMsgFromNamespace(string, string)
- #10 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(831): MessageCache->getMessageForLang(Language, string, boolean, array)
- #11 C:\inetpub\wwwroot\WikiLincluden\includes\cache\MessageCache.php(771): MessageCache->getMessageFromFallbackChain(Language, string, boolean)
- #12 C:\inetpub\wwwroot\WikiLincluden\includes\Message.php(1188): MessageCache->get(string, boolean, Language)
- #13 C:\inetpub\wwwroot\WikiLincluden\includes\Message.php(950): Message->fetchMessage()
- #14 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\includes\MediaWikiGadgetsDefinitionRepo.php(113): Message->exists()
- #15 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\includes\MediaWikiGadgetsDefinitionRepo.php(83): MediaWikiGadgetsDefinitionRepo->fetchStructuredList()
- #16 C:\inetpub\wwwroot\WikiLincluden\includes\libs\objectcache\WANObjectCache.php(1004): MediaWikiGadgetsDefinitionRepo->{closure}(boolean, integer, array, NULL)
- #17 C:\inetpub\wwwroot\WikiLincluden\includes\libs\objectcache\WANObjectCache.php(906): WANObjectCache->doGetWithSetCallback(string, integer, Closure, array)
- #18 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\includes\MediaWikiGadgetsDefinitionRepo.php(90): WANObjectCache->getWithSetCallback(string, integer, Closure, array)
- #19 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\includes\MediaWikiGadgetsDefinitionRepo.php(23): MediaWikiGadgetsDefinitionRepo->loadGadgets()
- #20 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\includes\GadgetRepo.php(36): MediaWikiGadgetsDefinitionRepo->getGadgetIds()
- #21 C:\inetpub\wwwroot\WikiLincluden\extensions\Gadgets\GadgetHooks.php(52): GadgetRepo->getStructuredList()
- #22 C:\inetpub\wwwroot\WikiLincluden\includes\Hooks.php(195): GadgetHooks::userGetDefaultOptions(array)
- #23 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(1552): Hooks::run(string, array)
- #24 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(5131): User::getDefaultOptions()
- #25 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(483): User->loadOptions()
- #26 C:\inetpub\wwwroot\WikiLincluden\includes\libs\objectcache\WANObjectCache.php(884): User->{closure}(boolean, integer, array, NULL)
- #27 C:\inetpub\wwwroot\WikiLincluden\includes\libs\objectcache\WANObjectCache.php(1004): WANObjectCache->{closure}(boolean, integer, array, NULL)
- #28 C:\inetpub\wwwroot\WikiLincluden\includes\libs\objectcache\WANObjectCache.php(889): WANObjectCache->doGetWithSetCallback(string, integer, Closure, array, NULL)
- #29 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(495): WANObjectCache->getWithSetCallback(string, integer, Closure, array)
- #30 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(437): User->loadFromCache()
- #31 C:\inetpub\wwwroot\WikiLincluden\includes\user\User.php(401): User->loadFromId(integer)
- #32 C:\inetpub\wwwroot\WikiLincluden\includes\session\UserInfo.php(88): User->load()
- #33 C:\inetpub\wwwroot\WikiLincluden\includes\session\CookieSessionProvider.php(119): MediaWiki\Session\UserInfo::newFromId(string)
- #34 C:\inetpub\wwwroot\WikiLincluden\includes\session\SessionManager.php(486): MediaWiki\Session\CookieSessionProvider->provideSessionInfo(WebRequest)
- #35 C:\inetpub\wwwroot\WikiLincluden\includes\session\SessionManager.php(189): MediaWiki\Session\SessionManager->getSessionInfoForRequest(WebRequest)
- #36 C:\inetpub\wwwroot\WikiLincluden\includes\WebRequest.php(735): MediaWiki\Session\SessionManager->getSessionForRequest(WebRequest)
- #37 C:\inetpub\wwwroot\WikiLincluden\includes\session\SessionManager.php(128): WebRequest->getSession()
- #38 C:\inetpub\wwwroot\WikiLincluden\includes\Setup.php(759): MediaWiki\Session\SessionManager::getGlobalSession()
- #39 C:\inetpub\wwwroot\WikiLincluden\includes\WebStart.php(137): require_once(string)
- #40 C:\inetpub\wwwroot\WikiLincluden\index.php(40): require(string)
- #41 {main}
- Thank you in advance for your help with this. Joanne222 (talk) 16:45, 21 July 2017 (UTC)
- As a starting point, have you already run update.php? Through SSH, in your Wiki directory run the following command:
php maintenance/update.php - (Manual:Update.php)
- Part of the error which mentions "Did you forget to run your application's database schema updater after upgrading?" indicates that update.php has not been run. AhmadF.Cheema (talk) 20:05, 21 July 2017 (UTC)
- I did the update via the web browser using these instructions in the Upgrade document:
- === Web browser[edit] ===
| MediaWiki version: | ≥ 1.17 |
- See also update.phpManual:update.php
- If your database is already big and in high production usage, then you should not be using the Web updater, e.g. because the update process will time out when the maximum_execution_time is reached. In that case you should use update.php from the command-line interface (not from the web). What exactly is "too big" depends on your server (e.g. on its performance, the load and on how long the maximum execution time of PHP allows the script to run). If your wiki is too big for the web updater and your hosting provider does not allow command-line access, then you need to migrate your wiki to another hosting account, preferably to one that does have shell access.
- Always backup before performing database maintenance.
- Navigate your webbrowser to
/mw-config/. For example, if your wiki is athttp://example.org/w/index.php, then navigate tohttp://example.org/w/mw-config/. - Select your language and click continue.
- The existing installation should be detected. Follow the instructions on the screen to upgrade it. If asked for the "upgrade key", open your LocalSettings.phpManual:LocalSettings.php file and look for the key assigned to $wgUpgradeKeyManual:$wgUpgradeKey.
- The message at the end indicated that everything updated ok.
- This is an intermittent problem, and does not happen every time you try to save a change. It may not happen for 5 times in a row on one page, then the 6th time it will throw the error. Joanne222 (talk) 20:27, 21 July 2017 (UTC)
- In-between these "5th" and "6th" edits, you haven't by any chance been involved in enabling or disabling any extensions, have you? The need to update the database using update.php usually comes up when some new extension is enabled/disabled. AhmadF.Cheema (talk) 08:15, 22 July 2017 (UTC)
- Nothing is changed between the edits while I am testing. I simple select to edit the page, change a simple text value to "test" then press the Save Changes button. Then I select Edit and change text value to "test2" then press the Save Changes button. Then select Edit and change the text value to "test3" and continue with this test until it fails.
- I did add the CollapsibleVector extension and change some of my extensions to the new ones after I did the initial upgrade, so I went ahead and rat the mw-config again just now to see if that would improve matters but it did not. The very first edit I did after this triggered the exact same error....page was not saved and error message indicated database may not have been updated.
- When I run the upgrade it states:
- Environmental checks
- Basic checks will now be performed to see if this environment is suitable for MediaWiki installation. Remember to include this information if you seek support on how to complete the installation.
- PHP 7.1.6 is installed.
- Warning: Could not find APCu, XCache or WinCache.
- Object caching is not enabled.
- GNU diff3 not found.
- Found ImageMagick: C:\ImageMagick\convert.exe.
- Image thumbnailing will be enabled if you enable uploads.
- Git version control software not found.
- Using server name "http://wiki".
- Using server URL "http://wiki/wikilincluden".
- Warning: Your default directory for uploads C:\inetpub\wwwroot\WikiLincluden/images/ is vulnerable to arbitrary scripts execution.
- Although MediaWiki checks all uploaded files for security threats, it is highly recommended to close this security vulnerability before enabling uploads.
- Warning: The intl PECL extension is not available to handle Unicode normalization, falling back to slow pure-PHP implementation.
- If you run a high-traffic site, you should read a little on Unicode normalization.
- The environment has been checked. You can install MediaWiki.
- Then:
- Upgrade existing installation
- There are MediaWiki tables in this database. To upgrade them to MediaWiki 1.28.2, click Continue
- Then pressing Continue:
- Upgrade existing installation
- ...index ls_field_val already set on log_search table.
- ...index change_tag_rc_tag already set on change_tag table.
- ...have rd_interwiki field in redirect table.
- ...transcache tc_time already converted.
- ...fulltext search table appears to be in order.
- ...iwlinks table already exists.
- ...index iwl_prefix_title_from already set on iwlinks table.
- ...have ul_value field in updatelog table.
- ...have iw_api field in interwiki table.
- ...iwl_prefix key doesn't exist.
- ...have cl_collation field in categorylinks table.
- ...module_deps table already exists.
- ...ar_page_revid key doesn't exist.
- ...index ar_revid already set on archive table.
- ...index user_email already set on user table.
- ...uploadstash table already exists.
- ...user_former_groups table already exists.
- ...index type_action already set on logging table.
- ...batch conversion of user_options: nothing to migrate. done.
- ...user table does not contain user_options field.
- ...have rev_sha1 field in revision table.
- ...have ar_sha1 field in archive table.
- ...index page_redirect_namespace_len already set on page table.
- ...have us_chunk_inx field in uploadstash table.
- ...have job_timestamp field in job table.
- ...index page_user_timestamp already set on revision table.
- ...have ipb_parent_block_id field in ipblocks table.
- ...index ipb_parent_block_id already set on ipblocks table.
- ...category table does not contain cat_hidden field.
- ...have rev_content_format field in revision table.
- ...have rev_content_model field in revision table.
- ...have ar_content_format field in archive table.
- ...have ar_content_model field in archive table.
- ...have page_content_model field in page table.
- Content Handler DB fields should be usable now.
- ...site_stats table does not contain ss_admins field.
- ...recentchanges table does not contain rc_moved_to_title field.
- ...sites table already exists.
- ...have fa_sha1 field in filearchive table.
- ...have job_token field in job table.
- ...have job_attempts field in job table.
- ...have us_props field in uploadstash table.
- ...ug_group in table user_groups already modified by patch patch-ug_group-length-increase-255.sql.
- ...ufg_group in table user_former_groups already modified by patch patch-ufg_group-length-increase-255.sql.
- ...index pp_propname_page already set on page_props table.
- ...index img_media_mime already set on image table.
- ...index iwl_prefix_from_title already set on iwlinks table.
- ...have ar_id field in archive table.
- ...have el_id field in externallinks table.
- ...have rc_source field in recentchanges table.
- ...index log_user_text_type_time already set on logging table.
- ...index log_user_text_time already set on logging table.
- ...have page_links_updated field in page table.
- ...have user_password_expires field in user table.
- ...have pp_sortkey field in page_props table.
- ...recentchanges table does not contain rc_cur_time field.
- ...index wl_user_notificationtimestamp already set on watchlist table.
- ...have page_lang field in page table.
- ...have pl_from_namespace field in pagelinks table.
- ...have tl_from_namespace field in templatelinks table.
- ...have il_from_namespace field in imagelinks table.
- ...hitcounter doesn't exist.
- ...site_stats table does not contain ss_total_views field.
- ...page table does not contain page_counter field.
- ...fa_deleted_reason in table filearchive already modified by patch patch-editsummary-length.sql.
- ...msg_resource_links doesn't exist.
- ...msg_resource doesn't exist.
- ...bot_passwords table already exists.
- ...have wl_id field in watchlist table.
- ...cl_collation key doesn't exist.
- ...index cl_collation_ext already set on categorylinks table.
- ...collations up-to-date.
- ...index rc_name_type_patrolled_timestamp already set on recentchanges table.
- ...have ct_id field in change_tag table.
- ...have ts_id field in tag_summary table.
- ...site_stats is populated...done.
- Purging caches...done.
- Upgrade complete.
- You can now start using your wiki
- It seems to me that the database upgrade message is not the cause of the pages not saving or else I would think that I would be unable to post messages every time I make an attempt. The database upgrade error message appears whether the page posts ok or not.
- Thank you for helping me try to figure this out. Joanne222 (talk) 20:16, 24 July 2017 (UTC)
Available space per wiki
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I want to know if there are a max space of words in each page of my wiki, and if there are another restrictions of space, and if yes, which are they.
Thank you Eliuth Franco (talk) 15:27, 14 July 2017 (UTC)
- See:
- Manual:$wgMaxArticleSize
- Page title size limitations (Unsure whether it is still up-to-date or not)
- Manual:Configuring file uploads#Set maximum size for file uploads AhmadF.Cheema (talk) 17:45, 14 July 2017 (UTC)
- Thank you so much, nice day Eliuth Franco (talk) 17:49, 14 July 2017 (UTC)
Safe update of PHP for the current versions
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello!
We currently have the following:
- MediaWiki is 1.26.0
- PHP 5.6.26
- MySQL was upgraded to the latest 5.7.18.1
We have some alerts related to PHP and would like to make an upgrade of PHP.
Two questions:
1) With MediaWiki 1.26.0 and MySQL 5.7.18.1 to what the latest PHP we can make an upgrade safely?
2) That PHP should be php-X.X.X-nts-Win32-VC11-x64.zip or what kind of?
Thank you,
Alex 198.232.185.11 (talk) 22:15, 14 July 2017 (UTC)
- For compatible PHP versions see, Compatibility#Software required to run MediaWiki.
- Also, note that MediaWiki 1.26 is no longer supported, consider upgrading. AhmadF.Cheema (talk) 23:16, 14 July 2017 (UTC)
- Thank you for your reply!
- So, if MediaWiki 1.26.0 is not supported anymore, should we upgrade it safely to 1.28 ?
- Where is the link then with steps how to upgrade MediaWiki from 1.26.0 to 1.28.0 ?
- And matching PHP for MediaWiki 1.28.0 will be 7.0.x ?
- Please let us know. Thank you! 198.232.184.254 (talk) 18:57, 17 July 2017 (UTC)
- MediaWiki v1.28 also has recently become outdated, the latest stable version is MediaWiki v1.29. "Matching PHP" is PHP 5.5.9 to PHP 7.x.
- For detailed upgrading instructions, see Manual:Upgrading.
- For first-time upgraders it is somewhat complicated but if you do decide to go through with the upgrade, whatever you do, remember to backup your Wiki. AhmadF.Cheema (talk) 01:18, 18 July 2017 (UTC)
- Note that 1.28 is still supported as a legacy release. MacFan4000 (talk) 19:14, 18 July 2017 (UTC)
Sharing wiki user database with forum website
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
How do I share a wiki's user database with a forum website? NostalgicLorikeet (talk) 00:29, 15 July 2017 (UTC)
- Depends on the "forum website" and its software's user authentication system. Malyacko (talk) 12:40, 16 July 2017 (UTC)
Show logo on MobileFrontend
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Is there a way to show my logo when using the Extension:MobileFrontend ? NitaiDas (talk) 08:46, 15 July 2017 (UTC)
- I ended up adding HTML in MobileFrontend/includes/skins/minerva.mustache NitaiDas (talk) 09:18, 15 July 2017 (UTC)
- This is probably the way to do it, although it would be better to include the added code through your Wiki's MediaWiki:Mobile.css (if it's not too difficult). AhmadF.Cheema (talk) 09:36, 15 July 2017 (UTC)
Thumbnail linking to full size image with one click?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Is there any code that would do this in a way that the actual full image size is displayed (not an image version adapted to maximum screen height for example). Spiros71 (talk) 16:58, 15 July 2017 (UTC)
[[File:Test.png|thumb|link={{filepath:Test.png}}]]121.220.96.200 (talk) 04:10, 16 July 2017 (UTC)- Edit: Thanks, I got it! Spiros71 (talk) 07:18, 16 July 2017 (UTC)
How do I detect page moves/deletions using MediaWiki API?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
I'm writing a small tool for my internal project and I would like to know: does MediaWiki API provide any API to detect page moves and deletions? I was trying to use action=query&prop=revisions&rvprop=... but it does not return what I want.
Am I missing something for revisions queries, or should I use another API action?
Thank you! 194.44.30.3 (talk) 08:53, 16 July 2017 (UTC)
- I think what you're looking for is the list module logevents: Special:Apihelp/query+logevents. —Mainframe98 talk 11:42, 16 July 2017 (UTC)
- @Mainframe98 It does exactly what I want. Thank you very much! 195.234.74.137 (talk) 10:28, 19 July 2017 (UTC)
Parser error on running update.php from command line
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am trying to update an installation which is currently 1.23.11 to 1.29.0
I have ugraded the server PHP version to 5.6.31 (cgi-fcgi)
When I run update.php from the command line I get the following message:
PHP Parse error: syntax error, unexpected '[' in (wiki pathname)/maintenance/update.php on line 165.
Any suggestions as to how to investigate further/solve would be much appreciated.
Many thanks
PaulMcM 86.189.241.69 (talk) 19:26, 16 July 2017 (UTC)
- On the command line, please run PHP, just as you used it to run update.php, but do not run the update.php file, but instead run it with parameter "-v" like php -v.
- I bet that the CLI version of PHP (checked from comand line) is different from the one served by your webserver. You might still have to update the CLI version. 2003:72:6D2C:2A00:E556:D2D6:85A6:AEB9 (talk) 19:54, 16 July 2017 (UTC)
- You got it in 1! - the command suggested returns PHP 5.3.3 - is there a standard approach to updating the CLI version or do you suggest I just request this from the hosting company? 86.189.241.69 (talk) 20:12, 16 July 2017 (UTC)
- The hosting company indicated that changing the CLI PHP version may cause problems in the management software (Plesk) and that they believe that this message is not a result of the difference in PHP version 86.189.241.69 (talk) 08:39, 17 July 2017 (UTC)
- What the hosting company really indicated is that they don't know what they are talking about.
- MediaWiki 1.29 at least needs PHP 5.5.9 to work properly. The ancient PHP version 5.3 just is too old. MediaWiki 1.29 is not working with this PHP version, because this PHP version is too old.
- You might want to point the hosting company to Compatibility#PHP. And although they should know, you maybe also want to explain them that PHP 5.3 does not support short array syntax, which is one of the features of newer PHP versions and which is one of the features, which MediaWiki 1.29 is using. Without looking up the code, your error message looks like the old PHP version errored out at exactly such a short array declaration. An employee of a hosting company should be able to see that from the error message, but... 2003:72:6D1F:4400:68B2:8:698F:7463 (talk) 09:09, 17 July 2017 (UTC)
PHP Warning: OutputPage::transformFilePath: Failed to hash ..../resources/assets/wiki.png
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
After updating to MediaWiki 1.30.0-alpha, I get:
PHP Warning: md5_file(C:\inetpub\wwwroot\OlePedia/../resources/assets/wiki.png): failed to open stream: No such file or directory in C:\inetpub\wwwroot\OlePedia\includes\OutputPage.php on line 3794
PHP Warning: OutputPage::transformFilePath: Failed to hash C:\inetpub\wwwroot\OlePedia/../resources/assets/wiki.png [Called from OutputPage::transformFilePath in C:\inetpub\wwwroot\OlePedia\includes\OutputPage.php at line 3796] in C:\inetpub\wwwroot\OlePedia\includes\debug\MWDebug.php on line 309
I use:
PHP 7.0.20 (cgi-fcgi)
MySQL 5.6.17
Lua 5.1.4
My wiki, www.hattebol.no is running under Windows Server 2008 R2 using IIS 7.5 OlePedia (talk) 22:01, 16 July 2017 (UTC)
- Have you noticed that the file path C:\inetpub\wwwroot\OlePedia/../resources/assets/wiki.png points to the wrong folder level? I think it points one level too high. Maybe this can be fixed by adjusting some of the configuration variables, but I don't know that.
- However, something else: MediaWiki 1.30 is in early alpha stage. It is not production ready and it can not be called stable. You should not use it for your production page. 2003:72:6D2C:2A00:E1FC:D643:EEE4:72B5 (talk) 22:57, 16 July 2017 (UTC)
- The MediaWiki logo wiki.png is shown on the pages so it is found by MediaWiki.
- I was recommended to use a newer version than 1.28.2 to be compatible with Wikibase which I need for my Template:Infobox person. So I installed the latest code With git as suggested by @Lydia Pintscher (WMDE) in https://www.mediawiki.org/w/index.php?title=Extension%20talk%3AWikibase%20Client#c-Lydia_Pintscher_%28WMDE%29-2017-07-05T08%3A39%3A00.000Z-OlePedia-2017-07-04T23%3A46%3A00.000Z OlePedia (talk) 23:18, 16 July 2017 (UTC)
New installation gets session_write_close error
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I installed MediaWiki version 1.29.0 manually, apparently successfully, but after logging in, the bottom of the front page shows this error:
Warning: session_write_close(): Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp) in [path to my directory] /includes/session/SessionManager.php on line 469
Line 469 is in the function "shutdown()".
I am not a PHP programmer, so have no clue how to fix this.
Any suggestions? Pwforaker (talk) 22:36, 16 July 2017 (UTC)
- Try to set $wgSessionCacheType to
CACHE_DB. Ciencia Al Poder (talk) 18:54, 19 July 2017 (UTC) - I am having the same problem. set $wgSessionCacheType to CACHE_DB did'n work. Danilomibr (talk) 16:13, 14 August 2017 (UTC)
- Take a look at Project:Support desk/Flow/2016/07#h-Login_error_(session_hijacking_protection)-2016-07-11T08:56:00.000Z, see if that helps. AhmadF.Cheema (talk) 19:23, 14 August 2017 (UTC)
Default value for max image size on image description page
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello! I would like to change the default value for the max image size which is 800x600. I know that every user can change this for himself in his preferences, but I want to change it for everyone, i.e. for random visitors who are not logged in, which is probably the same as the default value for new users. Elektroschrottsammler (talk) 00:21, 17 July 2017 (UTC)
- See Manual:$wgImageLimits. AhmadF.Cheema (talk) 06:20, 17 July 2017 (UTC)
- $wgDefaultUserOptions['imagesize'] is what I was looking for. Thank you! Elektroschrottsammler (talk) 22:39, 18 July 2017 (UTC)
No active login attempt is in progress for your session
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
When I try to log in with correct password wikipedia gives me message "No active login attempt is in progress for your session." In case I tried with wrong password then wikipedia gives me "wrong password" message. In any case it is not allowing me to log in. Please tell me why? Kindly post reply on my user talk page instead if possible as my IP is dynamic and I might not get same IP address again.
--- @User:ALM_scientist 210.2.145.90 (talk) 07:11, 17 July 2017 (UTC)
- Try to login to any WMF wiki you've never accessed before being logged-in (like a Wikipedia in another language), and login from there. Ciencia Al Poder (talk) 18:52, 19 July 2017 (UTC)
- Known issue, https://phabricator.wikimedia.org/T141482 Reception123 (talk) 12:02, 20 July 2017 (UTC)
The WikiEditor Edit bar disappears after first load
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hey there,
Mediawiki 1.27.3
Facing this strange issue.
When I login to the wiki and edit the page for the first time, the wikieditor loads properly and I am able to see the toolbar.
But later for all subsequent pages and for all subsequent edits, the wiki editor bar does not really load. (see below)
We looked at this solution
But it didn't help. Wondering how to solve this, or what is causing this.
Any thoughts how this can be solved?
~ Arnab Arnab vani (talk) 09:57, 17 July 2017 (UTC)
- Hey guys, any idea how to fix this?
- ~ Arnab Arnab vani (talk) 06:24, 18 July 2017 (UTC)
- The only errors I can see are in the Console of the developer tools (press F12 and click the Console tab on the new panel that appears). Maybe those are related to your issue? AhmadF.Cheema (talk) 08:31, 18 July 2017 (UTC)
- Yes, you're right. The error in the console was creating the issue. Basically we were loading an external javascript file and that javascript file had a few errors, which were being displayed in the console. And that error was causing the toolbar to not load, for some reason. Now that I have removed the script and it no longer loads on page refreshes, the toolbar is working fine.
- Thanks @AhmadF.Cheema
- yO
- ~ Arnab Arnab vani (talk) 05:44, 19 July 2017 (UTC)
External links auto formatting doesnt work
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Last week was working just fine, but today if i write something like [https://google.com google] i will see exactly like "[https://google.com google]" instead of just a google link. Any ideas? 91.126.38.98 (talk) 11:56, 17 July 2017 (UTC)
- found the reason, the {{WIKI}} tag wasnt on the header of the page, but i dont know why it is a must. 91.126.38.98 (talk) 12:03, 17 July 2017 (UTC)
- What version of MediaWiki are you using? MacFan4000 (talk) 12:12, 17 July 2017 (UTC)
Unable to save edits to page when on a wireless connection
I'm fairly new to MediaWiki and I have version 1.26.3 and I recently found that if I try to save any edits I make to a page from a computer connected via wifi, the page just hangs and the save doesn't commit.
The saves commit fine when I go back to using my PC connected via a wired network cable.
Any idea what is causing this? Any insight will be more than appreciated. 137.207.232.72 (talk) 15:20, 17 July 2017 (UTC)
- Can I get help on this please too? Though I found that my issue lies when I try to connect via a connection that is different from what is on campus 137.207.232.149 (talk) 20:24, 19 July 2017 (UTC)
Keep getting blocked and unable to post some information.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have been having a problem with information. For the last few days, I have been blocked by the server, after trying to post specific information on this website: http://horseacademy.com/wiki/index.php?title=Main_Page I have been able to post a huge amount of information already but there are a few last paragraphs remaining that I wish to post in certain sections. I did attempt to post the information here Project:Sandbox and all of the information did show up fine! I can post what information it is as well, if needed.The version we have is 1. 28.2
I am wondering as to why I keep getting blocked and is there anything that can be done to allow the information on the site? My user account is a member of Administrators and Bureaucrats as well. This is my first time using Media wiki software, so thank you very much to anyone who is able to help me! Juliet Vr (talk) 17:29, 17 July 2017 (UTC)
- Exactly what error message do you get on trying to submit the edit? AhmadF.Cheema (talk) 01:25, 18 July 2017 (UTC)
- That is the strange thing, there is no error message after trying to save the writing edits I've made. Either I try edit a small subsection of the guide and I click save Edits, it then goes to the WHOLE edit page or the server ends up blocking me, taking away the information I just had written up. Juliet Vr (talk) 07:42, 18 July 2017 (UTC)
- Because the Wiki doesn't have many Spam prevention extensions, I think this is more likely to be a server side issue. Can you access the server error logs? AhmadF.Cheema (talk) 08:04, 18 July 2017 (UTC)
- I cannot access them, but I can ask the Main Admin of the Page, if he can?
- Where would you find the error logs?
- Thank you so far for the help. Juliet Vr (talk) 08:20, 18 July 2017 (UTC)
- We were able to fix our problem with the site. What we had to do was: "disable mod_security for the domain"!
- Will mark this as resolved now and thank you Ahmad for the help! Juliet Vr (talk) 08:19, 19 July 2017 (UTC)
Can't get past the captcha - what is that "?" doing in there?
Trying to create an account but don't understand the captcha - am I too stupid to join? What's with the question mark? I've added the figures several times and been rejected.
help please. 2601:194:8280:7A50:E06E:707D:7263:CC36 (talk) 17:34, 17 July 2017 (UTC)
Help trying to log into private wiki page (log in credentials not working)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Please help. Our private wiki page hasn't been in-active for a few years, I have the log in credentials but are not working. I don't know what email address is associated with this account. This was created a few years ago before I was working for this organization.. 173.160.116.169 (talk) 19:11, 17 July 2017 (UTC)
Share login session between multiple language wikis
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
On Wikipedia, if you login to the English version, and then switch to the French version, you remain logged in.
I have a multi language wiki with shared database of users ($wgSharedDB), however the cookies seem to be separate. The documentation for $wgSharedDB states "Shared database for multiple wikis. Commonly used for storing a user table for single sign-on (actually not real SSO, since the user may still have to log in into each wiki separately, but at least registration has to be done only once)."
I'm wondering where the documentation is for sharing the login session/cookies across multiple language wikis? 52.53.169.169 (talk) 20:43, 17 July 2017 (UTC)
- Wikimedia uses CentralAuth for this, but it's rather Wikimedia specific and it's not well documented how to configure all of that in situations other than Wikimedia's. —TheDJ (Not WMF) (talk • contribs) 21:38, 17 July 2017 (UTC)
What is the default username and password for the mediawiki login and how can I change both of them
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I created a offline mediawiki website and install it using phpmyadmin from Bitnami, but I want to log in as whatever default admin/user it came with, it appears to accept the username "root" but I don't know where I can find the current password or know how to change it. I went through LocalSettings.php but not 100% sure what to do next.
Many thanks. Vauxford (talk) 09:51, 18 July 2017 (UTC)
- Didn't you enter some username and password during your installation?
- In any case, according to this, the default username for MediaWiki stacks on Bitnami is
user. AhmadF.Cheema (talk) 12:50, 18 July 2017 (UTC) - YES! it works! Thank you. I can finally log in my offline wiki. Vauxford (talk) 16:41, 18 July 2017 (UTC)
Certain subpages not listed in their designated page
I have a main page for all my meeting notes within my org. The main page designates or categorizes all listed under a tag of Category: Meetingnotes. Lately I noticed a few meeting notes from June through July not showing up on my main page.
They show up on the category page - but not the main page. These pages stopped after end of May and won't appear or get listed anymore.
They are all created from the same template using the same format - not sure why they are missing. Anyone know? 2602:301:779F:5D50:E9B4:CA18:285B:DC31 (talk) 17:24, 18 July 2017 (UTC)
- Try performing a Null edit on the page which isn't showing the updates and see if it helps:
- "Click on "Edit" and save without changing anything." AhmadF.Cheema (talk) 17:47, 18 July 2017 (UTC)
- Thanks for the reply!
- I've attempted null edits and that did not work.
- I've also tried typing out the category label/tag for each page and that didn't work. 2602:301:779F:5D50:E9B4:CA18:285B:DC31 (talk) 17:51, 18 July 2017 (UTC)
- Did you perform the null edit on your Main page or the category pages?
- You can also take a look whether there are pending jobs or not by browsing to your Wiki's:
- api.php?action=query&meta=siteinfo&siprop=statistics
- If there are a lot of remaining jobs, try running the following command through SSH in your Wiki directory:
php maintenance/runJobs.php- (Manual:RunJobs.php) AhmadF.Cheema (talk) 18:14, 18 July 2017 (UTC)
- The following:
- I did a null update through the category page where these non-displayed subpages are listed. Nothing
- I pointed my URL to the meeting minutes page directly, performed a null edit. Nothing
- Ran the API above and got no current jobs: 0
- Created a new test page and still not showing up 2602:301:779F:5D50:E9B4:CA18:285B:DC31 (talk) 18:20, 18 July 2017 (UTC)
- I was talking about performing the null edit on your Main page i.e. where the category pages should be showing up but aren't. AhmadF.Cheema (talk) 18:26, 18 July 2017 (UTC)
- Hi Ahmed,
- I went ahead and performed that null edit on these main pages and still nothing. 2602:301:779F:5D50:E9B4:CA18:285B:DC31 (talk) 18:31, 18 July 2017 (UTC)
Media Viewer configuration
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello, I have a doubt.
I installed mediawiki on my server and would like to use the media view to view the images.
I do not know how to set it up. Could someone give me some tips? Arturmafezzoli (talk) 17:50, 18 July 2017 (UTC)
- Maybe you are talking about Extension:MultimediaViewer.
- If not can you mention where did you see this "media view" in action? AhmadF.Cheema (talk) 18:27, 18 July 2017 (UTC)
- Thank you very much. That was it. But to configure it, I need to enable beta.
- "Log in to the wiki and go to Special:Preferences, then visit the "Beta features" tab and check the appropriate box."
- This page for me does not seem to appear =/ Arturmafezzoli (talk) 19:09, 18 July 2017 (UTC)
- Are you using Extension:BetaFeatures. If not, then it should be enabled by default.
- Just to be sure, you have gone through the steps mentioned in Extension:MultimediaViewer#Installation and have actually installed the extension, right? AhmadF.Cheema (talk) 19:39, 18 July 2017 (UTC)
- Yes I did everything as it shows. In the file LocalSetting I added the line require_once "$IP/extensions/BetaFeatures/BetaFeatures.php";
- When I try to access the Beta tab it shows the message:
- There was an error querying the database. This may indicate a bug in the software
- [d889caac84a7f162e442111a] 2017-07-18 20:36:58: Excepção fatal do tipo "DBQueryError" Arturmafezzoli (talk) 20:38, 18 July 2017 (UTC)
- Have you already run update.php? AhmadF.Cheema (talk) 20:46, 18 July 2017 (UTC)
- Noo. I can not believe I forgot that. Tksss :) Arturmafezzoli (talk) 11:43, 20 July 2017 (UTC)
VisualEditor
I have media wiki .29 installed on a virtual machine and when i try to edit the page using visualeditor nothing changes. The URL changes but nothing else happens, the page just stays the same. No error messages or loading bars appear like they did in a previous version i ran(which also did not get visual editor to fully function on).@Mediwiki~mediawikiwiki@Visual edit Austenjacoba (talk) 19:59, 18 July 2017 (UTC)
- How did you download the extension? MacFan4000 (talk) 20:47, 18 July 2017 (UTC)
- I've extracted it with cmd and git into the extensions folder, i also tried to download it from the site manually and putt it into the extensions folder. Austenjacoba (talk) 13:18, 19 July 2017 (UTC)
- It sounds like your missing lib/ve submodule. MacFan4000 (talk) 15:26, 19 July 2017 (UTC)
- is that when you do the submodule command in cmd? If so i have do that but i dont know if it actually brought them in. Austenjacoba (talk) 15:35, 19 July 2017 (UTC)
- Yes if you cloned it from github or downloaded it from GitHub. Otherwise no. MacFan4000 (talk) 16:42, 19 July 2017 (UTC)
- i re-downloaded the visualeditor from git using:
cd extensions git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.gitcd VisualEditorgit submodule update --init- Everything came through, i think. Is there anyway to check if i have the lib/ve. Also is this the correct version for mediawiki .29? Austenjacoba (talk) 14:42, 20 July 2017 (UTC)
- By default, the branch that should be downloaded would be the master branch.
- To change to the REL1_29 branch, use the following code:
git checkout -b REL1_29 origin/REL1_29AhmadF.Cheema (talk) 15:10, 20 July 2017 (UTC) - Still nothing, its like the page gets stuck after i click edit. Nothing changes though. Austenjacoba (talk) 19:46, 20 July 2017 (UTC)
- Are there any errors logged in the Console tab of the browser F12 developer tools? AhmadF.Cheema (talk) 03:33, 21 July 2017 (UTC)
Error after migraton: Call to a member function getCode() on null
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
After migrating my mediawiki site to a new server i caught this error i cannot solve:
PHP Fatal error: Uncaught Error: Call to a member function getCode() on null in /var/www/html/mediawiki/includes/user/User.php:1578
I'm running apache on centos7 (old server was apache on centos6) and i tried differrent versions of php. Right now i have php7.
The wiki works as it warned me i forgot to install a php extension, but i cannot access my pages. 185.48.55.208 (talk) 07:28, 19 July 2017 (UTC)
- As a starting point, see Project:Support desk/Flow/2016/09#h-I_updated_my_wiki_and_ran_into_another_problem-2016-09-20T18:51:00.000Z. AhmadF.Cheema (talk) 11:32, 19 July 2017 (UTC)
- I receive the same error message after a migration. Did you resolve this? 85.234.217.39 (talk) 07:31, 24 August 2017 (UTC)
- after adding $wgShowExceptionDetails = true; $wgShowDBErrorBacktrace = true; to LocalSettings.php i saw there was a problem updating the db during the update process (/maintenance/update.php).
- In my case the db user in LocalSettings.php didn't have enough rights on the db. 85.234.217.39 (talk) 07:39, 24 August 2017 (UTC)
Restrict access to mainspace with Lockdown
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I want to restrict the access to the mainspace.
For example:
Our company worked for a while with MW and created new sites in the mainspace.
Now we want a customer namespace where our customers have read access to. But they are not allowed to view the company intern content already created in mainspace.
I have Lockdown in use so I can restrict the access to costum namespaces. But how can I select the mainspace in Lockdown? 217.8.49.230 (talk) 08:15, 19 July 2017 (UTC)
- Found it.
- $wgNamespacePermissionLockdown[NS_MAIN]['read'] = array('companyuser'); 217.8.49.230 (talk) 10:16, 19 July 2017 (UTC)
I have installed spreadsheet extension in my local wiki and everything is configured correctly but when i am opening one wiki page that has reference to one excel file but getting message Spreadsheet is loading.
Checked in developer window and getting mime type error.
Refused to execute script from 'http://localhost:8080/mediawiki/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. 171.76.112.16 (talk) 12:20, 19 July 2017 (UTC)
- In which browser are you seeing this error and have you tried opening the page in a different browser? AhmadF.Cheema (talk) 13:13, 19 July 2017 (UTC)
After moving to a new server, i getting this error
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I was moving to a new server, its the same database and same folderpath.
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; GeSHi has a deprecated constructor in C:\server\apache\htdocs\wiki\public\extensions\SyntaxHighlight_GeSHi\geshi\geshi.php on line 259
[3b3740a4] /index.php/Mainpage MWException from line 226 of C:\server\apache\htdocs\wiki\public\includes\Hooks.php: Detected bug in an extension! Hook InputBoxHooks::register has invalid call signature; Parameter 1 to InputBoxHooks::register() expected to be a reference, value given
Backtrace:
#0 C:\server\apache\htdocs\wiki\public\includes\parser\Parser.php(310): Hooks::run(string, array)
#1 C:\server\apache\htdocs\wiki\public\includes\StubObject.php(105): Parser->firstCallInit()
#2 C:\server\apache\htdocs\wiki\public\includes\StubObject.php(129): StubObject->_call(string, array)
#3 C:\server\apache\htdocs\wiki\public\includes\cache\MessageCache.php(1009): StubObject->__call(string, array)
#4 C:\server\apache\htdocs\wiki\public\includes\cache\MessageCache.php(986): MessageCache->getParser()
#5 C:\server\apache\htdocs\wiki\public\includes\Message.php(1058): MessageCache->transform(string, boolean, Language, Title)
#6 C:\server\apache\htdocs\wiki\public\includes\Message.php(726): Message->transformText(string)
#7 C:\server\apache\htdocs\wiki\public\includes\Message.php(789): Message->toString()
#8 C:\server\apache\htdocs\wiki\public\includes\OutputPage.php(928): Message->text()
#9 C:\server\apache\htdocs\wiki\public\includes\OutputPage.php(975): OutputPage->setHTMLTitle(Message)
#10 C:\server\apache\htdocs\wiki\public\includes\page\Article.php(512): OutputPage->setPageTitle(string)
#11 C:\server\apache\htdocs\wiki\public\includes\actions\ViewAction.php(44): Article->view()
#12 C:\server\apache\htdocs\wiki\public\includes\MediaWiki.php(395): ViewAction->show()
#13 C:\server\apache\htdocs\wiki\public\includes\MediaWiki.php(273): MediaWiki->performAction(Article, Title)
#14 C:\server\apache\htdocs\wiki\public\includes\MediaWiki.php(566): MediaWiki->performRequest()
#15 C:\server\apache\htdocs\wiki\public\includes\MediaWiki.php(414): MediaWiki->main()
#16 C:\server\apache\htdocs\wiki\public\index.php(41): MediaWiki->run()
#17 {main} 178.7.42.127 (talk) 21:43, 19 July 2017 (UTC)
- To start with the first issue:
- Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP
- This means that you are now using PHP 7. The Syntaxhighlight extension used GeSHi as highlighter up to version 1.25. So you are using MediaWiki 1.25 or older.
- MediaWiki 1.25 and older is not compatible with PHP 7. Also note that these old MediaWiki versions no longer are supported - they have known security holes.
- You should upgrade MediaWiki to a supported version. E.g. upgrading to MW 1.27 is a good choice - this version will still be supported for more than two years. See Upgrading for more details!
- This should also solve the error in the InputBox extension. 79.228.217.226 (talk) 07:05, 20 July 2017 (UTC)
Upgraded to 1.29 - Fatal Exception
I have just upgraded from 1.28 to 1.29. When I attempt to open the main page I get the following error:
[056a2df837ca6662c8607fea] 2017-07-19 23:28:46: Fatal exception of type "Exception"
The number changes each time I refresh.
I have added:
error_reporting( E_ALL );
ini_set( 'display_errors', 1 ); to my Local settings, but receive no further information.
My PHP version is 7.0.18
Mysql version is 5.0.12
http://54.206.106.229/phpinfo.php
http://54.206.106.229/Wiki/index.php/Main_Page
I hope this is an easy one. Grantkinkead (talk) 23:32, 19 July 2017 (UTC)
- Did you run maintenance/update.php? If not than try running it. MacFan4000 (talk) 00:00, 20 July 2017 (UTC)
- That helped a lot and I managed to clean up a lot of stuff from a maps extension that was causing grief. However, now I have hit a bit of a wall. It appears that composer is not uploading a couple of files it could upload before the upgraded. The errors I am now getting are:
- Warning: Class 'Wikimedia\Timestamp\TimestampException' not found in /var/www/html/Wiki/includes/compat/Timestamp.php on line 18
- Warning: require(/var/www/html/Wiki/vendor/composer/../hamcrest/hamcrest-php/hamcrest/Hamcrest.php): failed to open stream: No such file or directory in /var/www/html/Wiki/vendor/composer/autoload_real.php on line 70
- Fatal error: require(): Failed opening required '/var/www/html/Wiki/vendor/composer/../hamcrest/hamcrest-php/hamcrest/Hamcrest.php' (include_path='/var/www/html/Wiki/vendor/pear/pear_exception:/var/www/html/Wiki/vendor/pear/console_getopt:/var/www/html/Wiki/vendor/pear/mail_mime:/var/www/html/Wiki/vendor/pear/mail_mime-decode:/var/www/html/Wiki/vendor/pear/mail:/var/www/html/Wiki/vendor/pear/pear-core-minimal/src:/var/www/html/Wiki/vendor/pear/net_socket:/var/www/html/Wiki/vendor/pear/net_smtp:.:/usr/share/php') in /var/www/html/Wiki/vendor/composer/autoload_real.php on line 70
- I have had a look in the composer.json file and it has the following:
- "autoload": {
- "psr-0": {
- "ComposerHookHandler": "includes/composer"
- },
- "files": [
- "includes/compat/Timestamp.php"
- ]
- },
- "autoload-dev": {
- "files": [
- "vendor/hamcrest/hamcrest-php/hamcrest/Hamcrest.php",
- "vendor/wmde/hamcrest-html-matchers/src/functions.php"
- ]
- },
- I am not too sure where to go from here. Any suggestions would be greatly appreciated. Grantkinkead (talk) 05:30, 20 July 2017 (UTC)
- I have sorted out the Timestamp issue. Grantkinkead (talk) 09:23, 20 July 2017 (UTC)
- Was the composer.json file updating to match the REL1_29 file? Reception123 (talk) 12:00, 20 July 2017 (UTC)
- I am experiencing a similar problem as well:
- Warning: require(/opt/htdocs/mediawiki/vendor/composer/../symfony/var-dumper/Resources/functions/dump.php): failed to open stream: Permission denied in /opt/htdocs/mediawiki/vendor/composer/autoload_real.php on line 70
- Fatal error: require(): Failed opening required '/opt/htdocs/mediawiki/vendor/composer/../symfony/var-dumper/Resources/functions/dump.php' (include_path='/opt/htdocs/mediawiki/vendor/pear/console_getopt:/opt/htdocs/mediawiki/vendor/pear/mail_mime:/opt/htdocs/mediawiki/vendor/pear/pear-core-minimal/src:/opt/htdocs/mediawiki/vendor/pear/pear_exception:.:/usr/share/pear:/usr/share/php') in /opt/htdocs/mediawiki/vendor/composer/autoload_real.php on line 70
- any advice? Revansx (talk) 22:38, 25 June 2018 (UTC)
- Do you installed by tarball, or using Git? 星耀晨曦 (talk) 00:49, 26 June 2018 (UTC)
- i have installed MW via Meza Revansx (talk) 02:40, 26 June 2018 (UTC)
- For the error message, your web server can't read
opt/htdocs/mediawiki/vendor/composer/../symfony/var-dumper/Resources/functions/dump.php. Make sure your web server can read the MW code files. 星耀晨曦 (talk) 02:46, 26 June 2018 (UTC) - facing the same issue with 1.34.0 version
- mediawiki\vendor\composer\autoload_real.php on line 61
- any advice? 202.89.106.200 (talk) 10:09, 26 February 2020 (UTC)
- Please paste all error messages. 星耀晨曦 (talk) 11:10, 2 March 2020 (UTC)
MediaWikiChat error
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I'm trying to access Special:Chat from Extension:MediaWikiChat, but it says "You are not allowed to chat, try logging in first." even though I am already logged in. Example of the error: https://allthetropes.org/wiki/Special:Chat Reception123 (talk) 12:18, 20 July 2017 (UTC)
- According to https://allthetropes.org/wiki/Special:ListGroupRights only synops and chatmods have the “Chat” user right. MacFan4000 (talk) 12:41, 20 July 2017 (UTC)
- That is unusual. It says "Defaults to all registered users, except those in the '
blockedfromchat' group" Reception123 (talk) 12:43, 20 July 2017 (UTC)
When editing, asking to type two words in a box that does not exist
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am a novice editor and have made written changes to a page without difficulty. However, I am not able to save changes involving references despite having done so successful with this software elsewhere.
For example, I attempted to insert, using the biomedical citation maker, a reference. A number was assigned, just as it was here when I pasted it in.[1] However, when I selected save, I got a message saying
"Your edit includes new external links. To protect the wiki against automated spam, we kindly ask you to type the two words you see in the box below"
However the box below is the editing box and I see no two words or where to type them in.
Recommendations?
- ↑ Ebell MH, Siwek J, Weiss BD, Woolf SH, Susman J, Ewigman B et al. (2004). "Strength of recommendation taxonomy (SORT): a patient-centered approach to grading evidence in the medical literature.". J Am Board Fam Pract 17 (1): 59-67. PMID 15014055.
- On which page exactly are you trying to make this edit? Can you provide a link? AhmadF.Cheema (talk) 15:20, 20 July 2017 (UTC)
- https://en.wikipedia.org/wiki/Prolotherapy is the page link. Thanks for your help. Dr Reeves (talk) 23:24, 20 July 2017 (UTC)
- It is possible some extension in your browser is inadvertently blocking the box from showing up, maybe try making the edit in another browser?
- You probably won't have to go through this issue repeatedly, as once you have made enough edits on Wikipedia, this spam check will automatically get disabled for you. AhmadF.Cheema (talk) 00:17, 21 July 2017 (UTC)
- I think I may be confused. I did ok on Wikipedia. I am having difficulty with Wikidoc editing.
- The page is https://www.wikidoc.org/index.php/Prolotherapy
- The spam check is on Wikidocs, not Wikipedia and it happens in both explorer and chrome.
- Still should go away with time? Perhaps I can put the references in written until the spam checker gets turned off. Dr Reeves (talk) 03:54, 22 July 2017 (UTC)
- As Wikidocs is unrelated to the Wikimedia Foundation, so your Wikipedia profile/edits are completely separate from Wikidocs edits.
- Regarding Wikidocs, they are using Extension:ConfirmEdit, which forces "new" users to solve a Captcha before allowing them to post external links. Probably because of some configuration mistake on the part of the Wiki admins that captcha is not getting displayed.
- A user is no longer considered "new" after he/she performs a particular number of edits and a particular number of days have passed since the account was created. Only admins would know what these particular numbers are. They are usually 5-15 edits and 2-3 days.
- One solution is to make the admins aware of teh Captcha not getting shown issue, the second solution is to make some simple edits to increase your edit count and wait a few more days. The Captcha request should automatically get disabled for you. AhmadF.Cheema (talk) 08:08, 22 July 2017 (UTC)
Error code after upgrade to latest version: Warning: session_write_close(): Failed to write session data (user).
I have just updated to 1.28 and now at the bottom of every page is the following error:
Warning: session_write_close(): Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/var/cpanel/php/sessions/ea3) in /home/domain1/public_html/kb/includes/session/SessionManager.php on line 469
Any advice would be appreciated, thanks. 203.167.191.74 (talk) 21:28, 20 July 2017 (UTC)
- As per Project:Support desk/Flow/2017/07#h-New_installation_gets_session_write_close_error-2017-07-16T22:36:00.000Z,
- "Try to set $wgSessionCacheType to
CACHE_DB." AhmadF.Cheema (talk) 00:23, 21 July 2017 (UTC) - Thank you for the quick reply. What file would I find $wgSessionCacheType in, it does not seem to be in SessionManager.php 203.167.191.74 (talk) 03:04, 21 July 2017 (UTC)
- It would be in your LocalSettings.php file. AhmadF.Cheema (talk) 03:30, 21 July 2017 (UTC)
- In the LocalSettings.php file I have a $wgMainCacheType but not a $wgSessionCacheType 203.167.191.74 (talk) 04:21, 21 July 2017 (UTC)
- Then add it below the $wgMainCacheType value. AhmadF.Cheema (talk) 04:37, 21 July 2017 (UTC)
- I tried adding it (presuming I did it correctly) and it did not help. Here is the line of code (I added the last line only) as I added it:
- ## Shared memory settings
- $wgMainCacheType = CACHE_NONE;
- $wgMemCachedServers = array();
- $wgSessionCacheType = CACHE_DB; 203.167.191.74 (talk) 23:09, 24 July 2017 (UTC)
- bump 203.167.191.74 (talk) 22:17, 27 July 2017 (UTC)
- This issue is still unresolved if anyone can shed any light. 203.167.191.74 (talk) 02:49, 11 August 2017 (UTC)
One user is unable to edit or create pages, why?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
- == Installed software ==
| Product | Version |
|---|---|
| MediaWiki | 1.28.0 |
| PHP | 5.6.24 (cgi-fcgi) |
| MySQL | 5.7.17-log |
- I deleted his mwiki_user record in the mySQL table, then ran the createuser SpecialPage option, he still does not see the "(edit)" option on any pages. What can I do to troubleshoot this problem? His database record is the same as everyone else's and all other users are able to edit pages just fine. I'm all out of ideas. Mushu999 (talk) 22:21, 20 July 2017 (UTC)
- Unrelated, but you are running an old and now insecure MediaWiki version. Please follow upgrades and use the latest 1.28 version. See https://www.mediawiki.org/wiki/Download and https://www.mediawiki.org/wiki/Manual:Upgrading AKlapper (WMF) (talk) 12:11, 21 July 2017 (UTC)
- Is it possible that the issue is from the that user's side?
- Maybe some gadget is enabled, some extension is blocking some resource (can be checked by looking at the Console tab of the browser F12 developer tools)? Has the user already tried using a different browser? AhmadF.Cheema (talk) 00:57, 21 July 2017 (UTC)
- He has used multiple browsers with the same result. He is on the same network as the other users. I'm totally stumped! 147.55.130.182 (talk) 15:56, 21 July 2017 (UTC)
- FOUND IT! I am using the LDAP auto-login extension in Windows. His account name was put into Active Directory as all upper-case, but his login username is normal case. Because php is case-sensitive it never matched. Ugh. Hope this helps anyone else who Googles for this problem. 147.55.130.182 (talk) 23:01, 21 July 2017 (UTC)
submit request for any changes in mediawiki project
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have mediawiki 1.28 on a hosted platform. I want a feature, if someone creates or edit a page on my wiki, the user has to submit that page to admin and when the admin approves that, then only the page published on the wiki (just like Wikipedia). Mukulpandey007 (talk) 06:52, 21 July 2017 (UTC)
- That is done with Extension:FlaggedRevs! 2003:72:6D1E:C000:357C:F938:9A92:76E6 (talk) 08:43, 21 July 2017 (UTC)
- No, Extension:FlaggedRevs! is not working on 1.28. Mukulpandey007 (talk) 12:28, 21 July 2017 (UTC)
- Extension:FlaggedRev is compatible with MediaWiki v1.28.
- Can you be more specific about exactly what error you're receiving?
- See methods outlined in How to debug to get detailed information regarding errors. AhmadF.Cheema (talk) 12:46, 21 July 2017 (UTC)
- There's also Extension:Moderation Ciencia Al Poder (talk) 14:07, 21 July 2017 (UTC)
How can I remove picture that is on server with out my concern?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
- help some one. can't delete picture from http://ftpmirror.your.org/pub/wikimedia/images/wikipedia/is/7/7b/
- it is not there with my consent!!!
- regards Magnús Sveinbjörnsson Maggimus (talk) 07:54, 21 July 2017 (UTC)
- By contacting the owners of the address http://ftpmirror.your.org/ ? AKlapper (WMF) (talk) 12:09, 21 July 2017 (UTC)
- Which picture are you talking about? There are several inside that folder...
- I guess you need to contact the site owner. Is that site an old copy of a Wikipedia wiki, of is.wikipedia.org maybe? Or whose wiki is that? 2003:72:6D1E:C000:357C:F938:9A92:76E6 (talk) 08:41, 21 July 2017 (UTC)
What is $wgCachePages for?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
What exactly is controlled by the Manual:$wgCachePages configuration setting? Manual page is very minimal. Waanders (talk) 09:05, 21 July 2017 (UTC)
- I have expanded the page a little.
- THe code is at https://github.com/wikimedia/mediawiki/blob/d6dcf23a8f22245e311d5582e4f9cd0f302e3738/includes/AjaxResponse.php#L223, so if you want to have a look yourself, you also can do that. 2003:72:6D1E:C000:6C6E:A0EA:9390:36A8 (talk) 11:22, 21 July 2017 (UTC)
Display of indentation (:) on talk pages
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
In the talk pages of our (local) instance, indentation does not display the background colors ; alternation of blue and white frames. I searched on cascading style sheets, and many ressources on the web, but I didn't found anything about it. May you explain how to define this rendering, please ? I hope to do this request on the good place. Apologize if doesn't it. Thanks in advance. Rdarovare (talk) 09:31, 21 July 2017 (UTC)
- Hi there!
- Alternating background colors are not part of one of the default skins. To help you we need to know, how these colors are implemented. Do you have a URL of the wiki so that one of us can have a look? 2003:72:6D1E:C000:6C6E:A0EA:9390:36A8 (talk) 11:12, 21 July 2017 (UTC)
- Thank you for your quick answer. In fact, MediaWiki is deployed on the private network of my company. Consequently, you can't access it. About my subjet, there is no background, quite simply. When we use « : » to do a response, we just have the indentation ; before the text, as expected. Of the blow, how could we define or specify the rendering ; including background-color and border-color ? Regards. Rdarovare (talk) 12:00, 21 July 2017 (UTC)
- For creating CSS rules, you can use select element feature of browser development tools. For Chrome browser, press (Ctrl + Shift + C), this will allow you to select any element on a web page and see its id, class names etc. and the CSS rules associated with those elements.
- From what I can see, the blank indentation before the text starts has class
dland for the text, the class is nameddd. Adding some rules such asbackground-color: crimson;for these classes directly in the developer tools will allow you to see the changes happening live. AhmadF.Cheema (talk) 13:02, 21 July 2017 (UTC) - Thanks. Yes : I saw that. I used the browser developpment tools to have a feel of the desired rendreing. However, I don't know to alternate two colors ; like in this page. In more, where insert this change ? In which file ? Those elements are not defined on the MediaWiki:Common.css. Certainly on the server, accessible via a technical console... ? ^o) Rdarovare (talk) 14:06, 21 July 2017 (UTC)
- They have been defined exclusively for the Vector skin through https://fr.wikipedia.org/wiki/MediaWiki:Vector.css.
- The first section titled
/* PAGES DE DISCUSSION : COLORATION INDENTÉE */deals with the relevant indentation related .CSS. - It would've been easier if you could have provided the link from the beginning. AhmadF.Cheema (talk) 15:31, 21 July 2017 (UTC)
- Sorry. My Mistake. Thank you so much for all your time, and your answers. Rdarovare (talk) 06:20, 24 July 2017 (UTC)
api call triggers wrong db commands
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I Have 2 Mediawiki 1.27, the server setup is cloned. but wiki A is an old wiki, updatet to 1.27 and wiki B is a fresh 1.27.
I have a script (to edit articles) that makes some API - calls, which works fine on Wiki B . in Wiki A it SEEM to work fine as well, except that none article is actually edited as it should. But no errors anywhere!? So we began to the jurney through all the possible log files till we saw the difference in the sql-Logs. So both server have same set-up and both wikis run at v. 1.27 and with the same script, calling the same API-functions, we get different commands/logs.
i have uploaded an example extract from the logs: [4](weTrransfer) - true.txt & false.txt
true.txt is form the server where everything works fine. false.txt is from the other server
One thin i recognized beneath many missing lines is that the lines 20,21 of false.txt are called in the true.txt at lines 11,12.
So please can you give me an idea about what is going on here? 213.252.150.178 (talk) 13:14, 21 July 2017 (UTC)
- what's the output of the api call? Maybe the api rejects the edit because it matches a spam filter, the page is protected and the user doesn't have the required permissions... Ciencia Al Poder (talk) 14:05, 21 July 2017 (UTC)
- Well, good hint.. the API returns "error: permission denied". So where can i manage the permission and Which permission is it? 213.252.150.178 (talk) 06:52, 24 July 2017 (UTC)
- Ok, i manged to succeed, thx for your help 213.252.150.178 (talk) 07:04, 24 July 2017 (UTC)
نصب ویرایشگر دیداری
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
سلام
وقت بخیر
افزونه پارسروید را لطفا توضیح دهید
چگونگی نصب افزونه ویرایشگر دیداری و
بنده اصلا سر در نمیارم
mahdi.alavi.nasab@gmail.com Sokote zaman (talk) 14:41, 21 July 2017 (UTC)
- For instructions see: Extension:VisualEditor
- For any more specific queries ask here or Extension talk:VisualEditor. AhmadF.Cheema (talk) 15:20, 21 July 2017 (UTC)
- ممنون
- نصب کرده بودم، ولی نیاز به نصب پارسروید داره
- و این دو تا باید با هم ربط پیدا کنن Sokote zaman (talk) 15:41, 21 July 2017 (UTC)
- Are you talking about this: Parsoid/Setup? AhmadF.Cheema (talk) 20:09, 21 July 2017 (UTC)
- yes
- and visual editor setup Sokote zaman (talk) 02:02, 22 July 2017 (UTC)
- I'm confused. The installation instructions are available at Extension:VisualEditor and Parsoid/Setup.
- Is there anything more that you want to ask? AhmadF.Cheema (talk) 08:25, 22 July 2017 (UTC)
- tank you
- I can not install
- Can you do this for me? Sokote zaman (talk) 12:19, 30 July 2017 (UTC)
- I haven't personally installed Extension:VisualEditor, at-least not the normal recommended way.
- It would be better if you ask someone else; for paid professional work see Professional development and consulting. AhmadF.Cheema (talk) 13:28, 30 July 2017 (UTC)
- tank you Sokote zaman (talk) 14:43, 30 July 2017 (UTC)
Inline SVG in Slideshow Gallery
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Is it in any way possible to use inline svg:s in a gallery? In the example below i'm using a widget to create the inline svg.
I'm trying to use a gallery like this:
<gallery>
{{#widget:InlineSVG}}
</gallery> Ikabodo (talk) 22:45, 21 July 2017 (UTC)
- .svg images can be used like other .png (or some other extension) images.
- The only thing you are probably missing is to specifically allow the .svg file extension for your Wiki (as it isn't enabled by default).
- For this purpose add the following line in your LocalSettings.php file:
$wgFileExtensions[] = 'svg'; // Allow .svg filesAhmadF.Cheema (talk) 08:23, 22 July 2017 (UTC)
Sternograph Extension
Has anyone gotten the extension Sternograph (https://www.mediawiki.org/wiki/Extension:Sternograph) to work with recent versions of MediaWiki? It seems to be outdated as far as I can tell. 46.28.53.125 (talk) 02:37, 23 July 2017 (UTC)
- I have not used the extension, but having a look at its code, it is not really big or complex.
- The extension has not yet been converted to use an extension.json file (which can easily be done using the convertExtensionToRegistration.php maintenace script. And it is still using the old l18n format. This also can be changed rather easily using the generateJsonI18n.php maintenace script. But both, also if not fixed, should not cause errors (at least not up to MediaWiki 1.29).
- Have you tried using the extension and did you get an error message? 2003:72:6D5E:1B00:122:9ADF:F46F:B9FC (talk) 10:15, 23 July 2017 (UTC)
- I tried using it without running any conversions, which gives the error
- [a6942289832b9d747070c930] 2017-07-23 21:07:02: Fatal exception of type "Error"
- I haven't used those scripts before, so I want to be sure I'm doing this correctly, I run
- php .. \convertExtensionToRegistration.php ...\extensions\Sternograph\Sternograph.php
- php .. \generateJsonI18n.php ...\extensions\Sternograph\Sternograph.i18n.php
- The first one yields an error, should it be run on Sternograph.body.php instead? Then, I add
- $wgMessagesDirs['Sternograph'] = '/extensions/Sternograph/i18n';
- Does this all seem right? Apologies, I'm new to this. C46a29c803 (talk) 21:30, 23 July 2017 (UTC)
How to make an image simply size to the users screen?
Hi everyone,
I am familiar with using the thumb option on pictures, to make them a particular size. I have a rather large picture (more than a 4K screen can show) which I would like to appear at a size that is scaled to the user's screen. I don't know any way to have it scale to their screen... if I simply say [[File:Whatever.JPG]], it is HUGE (they only see a tiny portion). The only other option seems to be a thumb, which makes it be some arbitrarily fixed size I have to specify.
How can I let an image fit the user's screen width? Surely there must be a way.
Thanks if you can help! RedKnight7 (talk) 06:01, 23 July 2017 (UTC)
- There should be a few ways to achieve responsive images.
- You can try Extension:AdaptiveThumb, not sure if it still works.
- Use CSS,
/* Images should be responsive */ res-img { max-width:100%; height:auto; }- Or define different images for different screen resolutions.
- If the extension doesn't work the CSS should be the best option. AhmadF.Cheema (talk) 10:49, 23 July 2017 (UTC)
@media (-webkit-min-device-pixel-ratio: 1.5), (min-resolution: 1.5dppx), (min-resolution: 144dpi) { #mp-topbanner-inner { background-image: url(//upload.wikimedia.org/wikipedia/commons/thumb/d/d9/Wikipedia-logo-v2-o10.svg/375px-Wikipedia-logo-v2-o10.svg.png) } } @media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 2dppx), (min-resolution: 192dpi) { #mp-topbanner-inner { background-image: url(//upload.wikimedia.org/wikipedia/commons/thumb/d/d9/Wikipedia-logo-v2-o10.svg/500px-Wikipedia-logo-v2-o10.svg.png) } }- Thanks greatly for the reply Ahmad,
- The CSS page didn't seem to have any effect? The description above is vague, "images should be responsive". Am I missing some further setting in the my call for the graphics file? Should I be saying a thumb of some percent, or something?
- Otherwise, I don't want your third (webkit) solution solution because it uses fixed sizes. That's my question - isn't there anything that's NOT a fixed size? That's automatically the user's screen width?
- I guess the AdaptiveThumb is a fallback option, but it would be nice to get the CSS to work, if I can. So,
- Am I doing something wrong or leave something out? A straight, enormous image (
[[File:Whatever.JPG]]) is still much larger than screen width. If the CSS code affects thumbnails somehow, I don't how to turn it on. If I state a thumb that's much larger the screen width (like 10000px), the CSS did not resize it to 100% of my screen width. - Is there a way to specify thumb nails as a PERCENT of user's screen size, instead of fixed pixels?
- Thanks so much if you can help! Can't MediaWiki tell a user's screen size?? RedKnight7 (talk) 14:41, 24 July 2017 (UTC)
- Make a class for responsive images, i.e. insert the following in your MediaWiki:Common.css
/* To make images responsive */ .res-img img { max-width:100%; height:auto; }- The "responsive" in the description is the term used for the automatic size-change functionality that you want for your images.
- Here, res-img is the .CSS class name. Including it in your Wiki's MediaWiki:Common.css page makes it available to all pages on your Wiki. This .CSS rule applies the two height and width style attributes to all the images that come under it.
- Using this class you can use, in your content pages, something of the form:
<div class="res-img"> [[File:Whatever.JPG]] </div>
- Or if you have a lot of these high-resolution images you can even turn this into a template.
- For some reason, I was unable to make this work through inline div styling i.e. by using
<div style="max-width:100%; height:auto;"> - Note that using this method, the image will get stretched if the user's screen size is greater than the "100%" size of the image. It shouldn't be an issue for larger images and smaller screen sizes. For details see, Responsive Web Design - Images.
- You can also automatically apply this .CSS rule to all the images on your Wiki without having to call the class, again and again by inserting the following in your MediaWiki:Common.cssAhmadF.Cheema (talk) 15:10, 24 July 2017 (UTC)
/* To make images responsive */ img { max-width:100%; height:auto; }
- It worked! Thank you so much Ahmad!
- I also noticed you put a period (.) before res-img in your reply, and also, I had no clue on the rest, but you made it all clear. This example is worth a thousand words.
- Thank you for all the other notes, which I'll try to remember. You're a good man. RedKnight7 (talk) 00:07, 27 July 2017 (UTC)
- You can simply use this extension: MultimediaViewer Fokebox (talk) 13:38, 24 July 2017 (UTC)
- Fokebox, the description for MultimediaViewer says it "Provides a better experience to users when they click on thumbnails in a page".
- I don't want to make thumbnails better. I want to simply display a picture on the screen (
[[File:Whatever.JPG]]) at full width. - This is what I'm saying... Right now, the only way I know to present it is either with a thumbnail (too small plus forces user to click through) OR the straight-up graphic (
[[File:Whatever.JPG]]) is far too large. - I just want to show a pic at full size width, whatever is full width for the user, without me having to specify anything specific. (A percent width is okay, but not fixed pixels.)
- Thanks if you can help. RedKnight7 (talk) 14:20, 24 July 2017 (UTC)
- Hi everyone I am coming to this a bit late but I have the same problem only rendering images on the mobile front end. They scale perfectly well on desktop, but when it comes to the mobile front-end they don't seem to scale. The images in question are in a table format and I wonder if that is causing the problem
- Example:
- Desktop; https://jollycontrarian.com/index.php?title=Service_catalog&mobileaction=toggle_view_desktop
- Vs
- Mobile view: https://jollycontrarian.com/index.php?title=Service_catalog&mobileaction=toggle_view_mobile
- Any thoughts appreciated! ElectricRay (talk) 22:01, 15 October 2021 (UTC)
- If you are using a skin providing the Bootsrap framework (Chameleon, Medik, etc.) one could specify the Boostrap "img-fluid" class e.g.
- [[kgh]] (talk) 18:14, 22 January 2023 (UTC)
[[File:NameOfMyFile.jpg|class=img-fluid]]
How I can add a new title in the left column (under Main page)?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
How I can add a new title in the left column (under Main page) in my Wiki? For example '''Community portal''' or '''User help'''. Thanks for answers. Regards Klaus 79.200.72.106 (talk) 07:37, 23 July 2017 (UTC)
- See Manual:Sidebar wargo (talk) 09:33, 23 July 2017 (UTC)
- I thank you very much for help. Regards Klaus 79.200.72.106 (talk) 10:23, 23 July 2017 (UTC)
"Download as PDF" not showing in leftpanel
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
We have downloaded free version of mediawiki 1.28.2 . We are done with all configuration setting during installation. I am not seeing option "Download as PDF" in local site as it is showing in main site of media wiki. i have enabled PDF extension but it is not supporting .
Please help us in resolving this issue.
Thanks and Regards.
Yogendra Trivedi YogendraAAES (talk) 06:35, 24 July 2017 (UTC)
- Which "PDF extension" are you talking about? Is it Extension:PdfHandler?
- I think the "Download as PDF" link in the sidebar is due to Extension:ElectronPdfService. AhmadF.Cheema (talk) 06:47, 24 July 2017 (UTC)
approval revision on custom namespace pages
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I have downloaded free version of mediawiki 1.28.2 and done with all configuration setting during installation. I am trying to provide approval revision extension for custom namespace.
Can you guide me approval revision on pages which is created under custom namespace ?
Thanks & Regards,
Yogendra Trivedi YogendraAAES (talk) 09:49, 24 July 2017 (UTC)
- For this, you will have to use Extension:FlaggedRevs. For custom namespaces you will have to further set the setting:
$wgFlaggedRevsNamespaces. - For example, in your LocalSettings.php:Use Manual:Namespace#Built-in namespaces for namespace numbers.
// Enable the extension require_once("$IP/extensions/FlaggedRevs/FlaggedRevs.php"); // Set FlaggedRevs for Project namespace $wgFlaggedRevsNamespaces = array ( 4 ); - Although in T30662 and T970 (Miraheze) for
$wgFlaggedRevsNamespacesnamespace names are being used instead of their numbers, but the documentation only mentions namespace numbers. It probably should work using either method. AhmadF.Cheema (talk) 10:18, 24 July 2017 (UTC)
how can we bulk upload in mediawiki and can show all uploads as wiki page
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
Can you please suggest how can we upload our files in mediawiki in bulk and can show all uploads as wiki page in mediawiki?
Now what we are doing we manually doing copy and pasting content in wiki page and it automatically generating markup.
But we have 2000 documents and is there any automated way for creating wiki pages in bulk on fly. Barsaiyan (talk) 09:50, 24 July 2017 (UTC)
- Maybe these can help:
Hur skapar man rubriker/kategorier, såsom diskografi, på en sida?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hej!
Jag har tre frågor inför att vi inom kort kommer uppdatera In Deed /musikgrupps) Wikipedia-sida, då vi (In Deed) snart ska släppa ett nytt album! Hoppas någon kan svara på detta:
1) Andra bandsidor, t ex Brainpool Musikgrupp, finns kategorierna Medlemmar och diskografi. Hur skapar man dessa rubriker/kategorier när man uppdaterar?
2) Vi kommer göra en sida på engelska också. Gör man en ny sida då som man kopplar ihop? Hur funkar det?
3) Vi vill gärna lämna ett bidrag till Wikipedias verksamhet. Hur går vi till väga då?
Tacksam för svar!
//In Deed the band Popspark73 (talk) 10:51, 24 July 2017 (UTC)
- This support desk is primarily for support regarding technical issues related to the MediaWiki software on which Wikipedia runs.
- For questions regarding the content on the Swedish Wikipedia, maybe you should ask here: https://sv.wikipedia.org/wiki/Wikipedia:Deltagarportalen. AhmadF.Cheema (talk) 13:28, 24 July 2017 (UTC)
- Aha, thanx! Popspark73 (talk) 15:00, 25 July 2017 (UTC)
change display name
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello
How can i change display name in bar?
In db this name equal user_name. I want change user_name to user_real_name.
How??? Starnikser (talk) 15:02, 24 July 2017 (UTC)
- Use {{DISPLAYTITLE|Title}} MacFan4000 (talk) 15:17, 24 July 2017 (UTC)
transformFilePath() or path problem
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I have just install mediawiki-1.29.0 ( tryed 1.28.2, before... - same problem) on localhost OpenServer 5.2.2.
After sucessful instalation I copied LocalSettings.php, opened the start page and got the error:
Warning: md5_file(D:\soft\OpenServer64\OpenServer\domains\mediawiki/../resources/assets/wiki.png): failed to open stream: No such file or directory in D:\soft\OpenServer64\OpenServer\domains\mediawiki\includes\OutputPage.php on line 3802
Warning: OutputPage::transformFilePath: Failed to hash D:\soft\OpenServer64\OpenServer\domains\mediawiki/../resources/assets/wiki.png [Called from OutputPage::transformFilePath in D:\soft\OpenServer64\OpenServer\domains\mediawiki\includes\OutputPage.php at line 3804] in D:\soft\OpenServer64\OpenServer\domains\mediawiki\includes\debug\MWDebug.php on line 309
after this i make test file:
<?php $hash = md5_file( "D:\soft\OpenServer64\OpenServer\domains\mediawiki\resources\assets\mediawiki.png" );
echo $hash ?>
- same error
<?php $hash = md5_file( "http://mediawiki/resources/assets/mediawiki.png" );
echo $hash ?>
- without errors, md5_file is working
Why wediawiki using local paths ? it's normaly ?
how can I test transformFilePath() from OutputPage.php ?
I am a beginner in MW, please help me to start it.
Any advice would be appreciated, thanks 77.108.66.140 (talk) 10:11, 25 July 2017 (UTC)
- http://mediawiki - is correct local domane name 77.108.66.140 (talk) 10:13, 25 July 2017 (UTC)
- backslash ( "\" ) is an escape character in strings in PHP. Try replacing them in paths using the forward slash instead ( "/" ) as PHP will convert them appropriately on Windows:
- md5_file( "D:/soft/OpenServer64/OpenServer/domains/mediawiki/resources/assets/mediawiki.png" ); Ciencia Al Poder (talk) 08:59, 27 July 2017 (UTC)
Trying to run Mediawiki on a Raspberry PI A ~20s loadtimes
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I'm trying to create a site on a Raspberry PI A running Raspbian, and whilst everything works, and pages are very slow, whether I'm logged in or not. I'm using Apache as the server, and postgres as the backend. I was wondering if I was doing something wrong, or if this hardware is just too light for this. The traffic on the site will be negligible, barely a few hits a day, almost none concurrent.
I don't really have enough memory to install memcached and I tried installing XHprof but couldn't work out how to do that on an RPi.
I've tried to install libapache2-mod-fcgid, (a replacement for fastcgi) in apache, and I've tried implementing some of the solutions in here; https://www.mediawiki.org/wiki/User:Aaron_Schulz/How_to_make_MediaWiki_fast
Here's the LocalSettings.php, any help you can offer would be appreciated, James
<?php
# This file was automatically generated by the MediaWiki 1.28.2
# installer. If you make manual changes, please keep track in case you
# need to recreate them later.
#
# See includes/DefaultSettings.php for all configurable settings
# and their default values, but don't forget to make changes in _this_
# file, not there.
#
# Further documentation for configuration settings may be found at:
# https://www.mediawiki.org/wiki/Manual:Configuration_settings
# Protect against web entry
if ( !defined( 'MEDIAWIKI' ) ) {
exit;
}
## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;
$wgSitename = "viewwiki";
$wgMetaNamespace = "Viewwiki";
## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs
## (like /w/index.php/Page_title to /wiki/Page_title) please see:
## https://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath = "/viewswiki";
## The protocol and server name to use in fully-qualified URLs
$wgServer = "http://192.168.2.213:8080";
## The URL path to static resources (images, scripts, etc.)
$wgResourceBasePath = $wgScriptPath;
## The URL path to the logo. Make sure you change this from the default,
## or else you'll overwrite your logo when you upgrade!
$wgLogo = "$wgResourceBasePath/images/HydrogenSonata.jpg";
## UPO means: this is also a user preference option
$wgEnableEmail = true;
$wgEnableUserEmail = true; # UPO
$wgEmergencyContact = "<blanked>";
$wgPasswordSender = "<blanked>";
$wgEnotifUserTalk = false; # UPO
$wgEnotifWatchlist = false; # UPO
$wgEmailAuthentication = true;
## Database settings
$wgDBtype = "postgres";
$wgDBserver = "127.0.0.1";
$wgDBname = "wikidb";
$wgDBuser = "wikiuser";
$wgDBpassword = "<blanked>";
# Postgres specific settings
$wgDBport = "5432";
$wgDBmwschema = "mediawiki";
## Shared memory settings
$wgMainCacheType = CACHE_ACCEL;
#changes 22nd
$wgSessionCacheType = CACHE_DB;
#Changed by JA 20th July
$wgUseFileCache = true;
$wgMessageCacheType = CACHE_ACCEL;
$wgCacheDirectory = '/var/www/apache/www/viewswiki/cache';
$wgUseLocalMessageCache =true;
$wgParserCacheType = CACHE_DB;
$wgUseGzip = true;
$wgEnableSidebarCache = true;
$wgDisableCounters = true;
$wgMiserMode = true;
$wgCompressRevisions = true;
$wgRevisionCacheExpiry = 3*24*3600;
$wgParserCacheExpireTime = 14*24*3600;
$wgMemCachedServers = [];
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = false;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";
# InstantCommons allows wiki to use images from https://commons.wikimedia.org
$wgUseInstantCommons = false;
# Periodically send a pingback to https://www.mediawiki.org/ with basic data
# about this MediaWiki instance. The Wikimedia Foundation shares this data
# with MediaWiki developers to help guide future development efforts.
$wgPingback = true;
## If you use ImageMagick (or any other shell command) on a
## Linux server, this will need to be set to the name of an
## available UTF-8 locale
$wgShellLocale = "en_GB.utf8";
## Set $wgCacheDirectory to a writable directory on the web server
## to make your wiki go slightly faster. The directory should not
## be publically accessible from the web.
#$wgCacheDirectory = "$IP/cache";
# Site language code, should be one of the list in ./languages/data/Names.php
$wgLanguageCode = "en";
$wgSecretKey = "<blanked>";
# Changing this will log out all existing sessions.
$wgAuthenticationTokenVersion = "1";
# Site upgrade key. Must be set to a string (default provided) to turn on the
# web installer while LocalSettings.php is in place
$wgUpgradeKey = "<blanked>";
## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsUrl = "https://creativecommons.org/licenses/by/4.0/";
$wgRightsText = "Creative Commons Attribution";
$wgRightsIcon = "$wgResourceBasePath/resources/assets/licenses/cc-by.png";
# Path to the GNU diff3 utility. Used for conflict resolution.
$wgDiff3 = "/usr/bin/diff3";
# The following permissions were set based on your choice in the installer
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;
## Default skin: you can change the default skin. Use the internal symbolic
## names, ie 'vector', 'monobook':
$wgDefaultSkin = "DuskToDawn";
# Enabled skins.
# The following skins were automatically enabled:
wfLoadSkin( 'CologneBlue' );
#wfLoadSkin( 'Modern' );
wfLoadSkin( 'MonoBook' );
wfLoadSkin( 'Vector' );
# Enabled extensions. Most of the extensions are enabled by adding
# wfLoadExtensions('ExtensionName');
# to LocalSettings.php. Check specific extension documentation for more details.
# The following extensions were automatically enabled:
wfLoadExtension( 'Cite' );
wfLoadExtension( 'Gadgets' );
wfLoadExtension( 'ImageMap' );
wfLoadExtension( 'PdfHandler' );
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
wfLoadExtension( 'WikiEditor' );
# End of automatically generated settings.
# Add more configuration options below.
wfLoadSkin( 'DuskToDawn' );
81.96.127.254 (talk) 11:54, 25 July 2017 (UTC)
- The configuration looks sane. Probably RPi is not fast enough. MediaWiki is a complex software built in PHP, and having the database on the same device will probably affect, specially if it has only 1 CPU core (which needs to be shared by apache, php and database on every request) and the disk is slow (an SD card, maybe?)
- You may try using nginx (if there's an ARM build for it) and php-fpm instead of apache, as nginx provides better performance in this setup. Ciencia Al Poder (talk) 08:56, 27 July 2017 (UTC)
Cannot start editing (create) Common.css
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
When I type mysitename/mediawiki/w/index.php?title=MediaWiki:Common.css (or MediaWiki:Common.css in serachbox) it shows "Internal Error". Lower in my language someyhing like "[WXcnzmRZrap6EUtZM1v@VwAAAUo] 2017-07-25 11:13:18: Exception cannot be solved «Symfony\Component\Process\Exception\RuntimeException» (Italic is my translation, not exactly). What can I do with this? MediaWiki:Sidebar is working at the same time. B.Shapoval (talk) 13:35, 25 July 2017 (UTC)
- Do you have syntaxhighlighting enabled? AhmadF.Cheema (talk) 00:52, 26 July 2017 (UTC)
- It is seen in Special:Version. How does it help me? B.Shapoval (talk) 04:27, 26 July 2017 (UTC)
- Did you install the extension from Git?
- If you did, then it requires composer installation too. Through SSH change to the directory containing the extension and run the following commands:If
chmod a+x /pygments/pygmentize composer install
composer install, had been run once before and this time the extension was updated then run:composer update. AhmadF.Cheema (talk) 06:55, 26 July 2017 (UTC) - Excuse me, I did not understand. In my 1.28.1 mediawiki there is extension SyntaxHighlight_GeShi with pygments inside. So do I need download and insert GeSHi from GitHub and composer for creating CSS additionally? Could I simply do something with already installed extention? B.Shapoval (talk) 21:00, 28 July 2017 (UTC)
- I'm not sure but it's possible that the errors you are seeing are because when your Wiki tries to access a page where syntax highlighting has to be shown (such as MediaWiki:Common.css) it runs into problems accessing the extension. For which reason, I mentioned the steps to solve issues with the extension.
- Now that I think about it, you should first try just disabling Extension:SyntaxHighlight, to see if that is indeed what is causing the problems. AhmadF.Cheema (talk) 05:28, 29 July 2017 (UTC)
- Thank you for answers. I cannot check right now because my hoster don't work from last weekend (hostafirm.com). B.Shapoval (talk) 18:43, 1 August 2017 (UTC)
- Yes! It is woking. As soon as I deleted the line
- wfLoadExtension( 'SyntaxHighlight_GeSHi' );
- in LocalSettings.php , internal error of Common.css disappeared.
- I will reload the SyntaxHighlight_GeShi. This is another issue.
- So solved. B.Shapoval (talk) 19:48, 3 August 2017 (UTC)
Display uname
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I want that instead of the name of the participant, at the entrance, another attribute from the database should be displayed. For example user_real_name. In the upper right corner. How to do it? Starnikser (talk) 13:44, 25 July 2017 (UTC)
- Maybe Extension:Realnames will work? AhmadF.Cheema (talk) 15:20, 25 July 2017 (UTC)
My PDF's Files cant viewed / Showed
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
How do I view a PDF file in my mediawiki?
I tried using PdfHandler and PDF Integrate without success.
I added the plugin to the server / and modified the LocalSettings.php file
you can see the specialpage in : http://wikiageing.org/index.php?title=%D8%AE%D8%A7%D8%B5:%D9%86%D8%B3%D8%AE%D8%A9
I forget a setting or what? Dezedien (talk) 14:56, 25 July 2017 (UTC)
- MediaWiki 1.23 is unsupported, we recomend upgrading. MacFan4000 (talk) 15:35, 25 July 2017 (UTC)
- to upgrade with a simple FTP access is it possible ? Dezedien (talk) 12:17, 26 July 2017 (UTC)
- It seems that you will also need to update php to 5.5.9 or newer. MacFan4000 (talk) 12:48, 26 July 2017 (UTC)
- thanks Mac :) but and how to update php to newer version ... Dezedien (talk) 13:37, 26 July 2017 (UTC)
- You need SSH access.Do you know which version of debian you are using? -MacFan4000 (Logged Out) 2002:43F4:3186:1234:394A:44CD:84A4:2CBD (talk) 14:03, 26 July 2017 (UTC)
- sorry i haven't SSH access Dezedien (talk) 14:31, 26 July 2017 (UTC)
- What host are you using? You should probably look for a new one if your current one only allows you to run MediaWiki 1.23, as that is a very old, and as MacFan4000 said unsupported version. Reception123 (talk) 16:42, 27 July 2017 (UTC)
Improved search in deleted pages archive
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
During Wikimedia Hackathon 2016, the Discovery team worked on one of the items on the 2015 community wishlist, namely enabling searching the archive of deleted pages. This feature is now ready for production deployment, and will be enabled on all wikis, except Wikidata.
Right now, the feature is behind a feature flag - to use it on your wiki, please go to the Special:Undelete page, and add &fuzzy=1 to the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=1. Then search for the pages you're interested in. There should be more results than before, due to using ElasticSearch indexing (via the CirrusSearch extension).
We plan to enable this improved search by default on all wikis soon (around August 1, 2017). If you have any objections to this - please raise them with the Discovery team via email or on this announcement's discussion page. Like most Mediawiki configuration parameters, the functionality can be configured per wiki.
Once the improved search becomes the default, you can still access the old mode using &fuzzy=0 in the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=0
Please note that since Special:Undelete is an admin-only feature, this search capability is also only accessible to wiki admins.
Thank you! CKoerner (WMF) (talk) 18:36, 25 July 2017 (UTC) MediaWiki message delivery (talk) 18:36, 25 July 2017 (UTC)
Can I use the MediaWiki engine for a social media website that works similar to Facebook?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am planning to design a social media site that functions similar to Facebook but using the MediaWiki engine in addition to the Social tools and perhaps Semantic MediaWiki. I don't have any servers yet and I plan to learn PHP, HTML, and Javascript,. How it would work is that the website would have user profiles where they can edit their own profiles, and have personal name spaces for their messages, blogs, personal pages, and posts. Also the users are able to friend other users, and create and join groups, with the group having their own fourm and wiki pages in which the group members can edit, as well as having group chatrooms. Users can also create pages about their businesses and interests. MediaWiki would also be useful for special rights over each groups and the entire wiki. Perhaps I can research some extensions that can be useful, and if there isn't an extension that I need I can develop my own for the website.
Do you think MediaWiki can be used to create a social media site, and if so is it a good idea to use MediaWiki or give it any wiki functionality? Sapphire Williams (talk) 23:32, 25 July 2017 (UTC)
- And if any traditional social media site has used MediaWiki, may you please give me examples? Sapphire Williams (talk) 23:55, 25 July 2017 (UTC)
- Wouldn't it probably be much easier to use some forum, or better yet, social networking open source application for this purpose?
- For all the things you will want in your social wiki, will require MediaWiki to be heavily modified while most of those should be available out-of-the-box for social networking applications.
- To make a website successful, a lot of the work needs to be put into the content of the website. If you end up spending most of your time in learning "PHP, HTML, and Javascript" (I'm assuming you already don't have a working knowledge of them) and further customizing extensions, you are going to have no time left for the more important work needed to make a website popular.
- See Social Networking and Forum applications for a relevant list. Discourse is one forum application that I think can do all the things you want to do, out-of-the-box. AhmadF.Cheema (talk) 00:36, 26 July 2017 (UTC)
- I have two questions: If I decide to make a wiki - based social media site, can I use a wiki engine other than MediaWiki?
- Or can the above applications can be used with MediaWiki or other wiki engines? Sapphire Williams (talk) 01:46, 26 July 2017 (UTC)
- You can use other Wiki applications too, but you will have to look through the different services to see what fits your needs. I don't have the personal experience to be sure what would be the best fit for you.
- Some things one type of application does better, while in other things another type of application is better. Mainly depends on what kind of a community you are trying to create.
- Most of your needs in one way or another do get fulfilled by MediaWiki, but it doesn't provide the most smooth and intuitive user experience. For example, live chat extension for MediaWiki is not that impressive while other Social Networking applications and Discourse does much better. A good (but far from the best) chat implementation that I saw used with MediaWiki was a third-party chat application like the one you can see used on some sites for customer support. The feature to restrict all but one group of users from editing a particular page, although does get implemented by a few extensions, as far as I remember, all of them suffered from one issue or another.
- It is also possible to use multiple web applications at the same time. For example, to have wiki.sitename.com as the Wiki part of the site and forum.sitename.com as the Forum. However, you might need a very supportive community to make such an implementation popular. AhmadF.Cheema (talk) 07:28, 26 July 2017 (UTC)
- Okay got it, thanks!
- But is it okay if you list some extensions that can restrict a group of users from editing a particular page? Sapphire Williams (talk) 17:47, 26 July 2017 (UTC)
- See Extension:Restrict access by category and group and Extension:CategoryPermissions.
- But there are usually some limitations and bugs to such restriction extensions. AhmadF.Cheema (talk) 19:51, 26 July 2017 (UTC)
How to make it so images appear at full size in search engines?
Say I have a page with a gallery with all the images sized 120px. How do I make it so that these images appear at full size on Google Images, like they do on Wikia? If a gallery on Wikia also had images at 120px, their images would actually appear at their proper size. 68.185.215.47 (talk) 05:01, 26 July 2017 (UTC)
GIFs choose not to render.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have installed ImageMagick -- I went through the installation through PuTTy and it tells me that it is installed correctly, and I can see in the directory where it is, and I can see the convert in the place it's supposed to be, and my LocalSettings set $wgUseImageMagick to true and set the location. I doubled the $MaxShellMemory and tripled the $MaxShellTime Even after all this, GIF images refuse to create thumbnails at all, and still only 1 GIF thumbnail renders.
http://wikizilla.org/wiki/ShinGoji#First_Form
Here are the stats of the wiki. http://wikizilla.org/wiki/Special:Version --- Linux hosting. $wgCacheEpoch didn't work, and regardless I tried to upload small GIF images after I got ImageMagick and even those don't render properly.Manual:Image_administration#Image_thumbnailing I am guessing the two possible things I can have wrong are the "absolute path" for the $wg ImageMagick location thing, which is located outside of the /wiki/ folder ------- or that "the command is executable by the web server process," which I don't know what that means.
We've had this non-rendering GIFs problem for a year now, so please help me out. 68.185.215.47 (talk) 05:56, 26 July 2017 (UTC)
- Use Manual:thumb.php (on your wiki) to force the generation of a thumbnail of a file from your server. If you enable the display of errors and exception details (see Manual:How to debug) you should see a descriptive error message about what failed in the thumbnail generation. Ciencia Al Poder (talk) 08:46, 27 July 2017 (UTC)
- Also, MediaWiki 1.26 is unsupported. We recommend upgrading. MacFan4000 (talk) 11:17, 27 July 2017 (UTC)
- Where should I put the code found on the thumb.php page? The page doesn't say, for what reason I can't possibly understand. I tried putting the Apache thing in .htaccess but nothing happened? I don't have a clue where the ngix one would even begin to go.
- I found this with the Debugging toolbar:
- ImageGallery::add Kamata-kun Front of Gills.gif
- Query i2607325_mw1 (343) (slave): SELECT /* LocalFile::loadFromDB Titanollante */ img_size,img_width,img_height,img_bits,img_media_type,img_major_mime,img_minor_mime,img_metadata,img_timestamp,img_sha1,img_user,img_user_text,img_description FROM `mw_image` WHERE img_name = 'Kamata-kun_Leaks_Red_Fluid_from_Gills.gif' LIMIT 1 Didn't find any errors anywhere other than this, I turned on show errors on LocalSettings, turned on errors on the php.ini, and still got no errors. 68.185.215.47 (talk) 01:29, 28 July 2017 (UTC)
- You don't have to touch any server configuration. What I mean is to do a normal web request (from your browser) to the thumb.php script, which is in the same path as index.php, load.php and api.php, namely http://wikizilla.org/wiki/thumb.php, with the parameters described in the manual page to provide a filename and width, since you're the one knowing which files don't thumbnail properly. Ciencia Al Poder (talk) 13:06, 28 July 2017 (UTC)
Updating to 1.29 can only be done in non-readonly mode (revised for 1.31.0)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
All, this is an odd one. I updated my 1.28.2 install to 1.29 today and at the end I do my usual 'php maintenance/update.php'. But on doing that, things failed. If I tried to load a wikipage I got:
[WXihOq3smIUAAEBThTYAAAAb] 2017-07-26 14:03:39: Fatal exception of type "Wikimedia\Rdbms\DBQueryError".
Huh. So, looking around I followed:
Set $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information
and then re-ran the update.php and:
...wl_notificationtimestamp is already nullable.
...index times already set on logging table.
...have ipb_range_start field in ipblocks table.
[37fe685e9f4eecdeed47e3a4] [no req] Wikimedia\Rdbms\DBReadOnlyError from line 858 of /home/site/site.org/wiki/includes/libs/rdbms/database/Database.php: Database is read-only: Maintenance is underway. Website is on read-only mode
Backtrace:
#0 /home/site/site.org/wiki/includes/installer/MysqlUpdater.php(833): Wikimedia\Rdbms\Database->query(string, string)
#1 [internal function]: MysqlUpdater->doPageRandomUpdate()
#2 /home/site/site.org/wiki/includes/installer/DatabaseUpdater.php(472): call_user_func_array(array, array)
#3 /home/site/site.org/wiki/includes/installer/DatabaseUpdater.php(436): DatabaseUpdater->runUpdates(array, boolean)
#4 /home/site/site.org/wiki/maintenance/update.php(174): DatabaseUpdater->doUpdates(array)
#5 /home/site/site.org/wiki/maintenance/doMaintenance.php(111): UpdateMediaWiki->execute()
#6 /home/site/site.org/wiki/maintenance/update.php(219): require_once(string)
#7 {main}
(urls mangled for safety's sake)
So, I then edited my LocalSettings.php to turn off readonly and, bang, it worked. But I'm sure in the past I'd not needed to and even this page:
Manual:Upgrading#Can my wiki stay online while it is upgrading.3F
seems to say I can do the update in readonly mode.
Any idea what I did wrong? FYI my PHP is 5.6.29 and my MySQL is 5.6.34-log TheMatt (talk) 14:42, 26 July 2017 (UTC)
- Reported in T151833. Apparently update.php is honoring $wgReadOnly since MediaWiki 1.27... You'll have to unset $wgReadOnly, and if you want nobody to be able to edit while upgrading, you may want to fiddle with Manual:User rights revoking edit, move, upload, deletion rights for everyone during the upgrade... Ciencia Al Poder (talk) 08:32, 27 July 2017 (UTC)
- I'm reopening this topic, as it applies to my upgrade from 1.27.4 to 1.31.0. @Ciencia Al Poder provided the solution I was looking for.
- I also ran my usual 'php maintenance/update.php' and encountered the same exception when I attempted to view my wiki in the web browser.
[W48fI-QM63YPxj1AGEiUeQAAAA8] 2018-09-05 00:11:15: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"- My command line and results:
$ php update.php MediaWiki 1.31.0 Updater Your composer.lock file is up to date with current dependencies! Going to run database updates for wiki 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. ...have ipb_id field in ipblocks table. ...have ipb_expiry field in ipblocks table. ...already have interwiki table ...indexes seem up to 20031107 standards. ... ...wl_notificationtimestamp is already nullable. ...index times already set on logging table. ...have ipb_range_start field in ipblocks table. Set $wgShowExceptionDetails = true; and $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information.
- The important point is that the error message did not display. Only the 2nd line explaining how to set the error reporting appears. The MariaDB error log contained this error:
1180903 10:44:25 [ERROR] Incorrect definition of table mysql.proc: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA- Without an error message, I was very concerned my database was broken. I then implemented the error reporting variables in LocalSettings.php. The error message is displayed:
...wl_notificationtimestamp is already nullable. ...index times already set on logging table. ...have ipb_range_start field in ipblocks table. [75cb065940c7af8c0bae4737] [no req] Wikimedia\Rdbms\DBReadOnlyError from line 1121 of /var/www/html/w/includes/libs/rdbms/database/Database.php: Database is read-only: Software upgrade Backtrace: #0 /var/www/html/w/includes/installer/MysqlUpdater.php(878): Wikimedia\Rdbms\Database->query(string, string) #1 /var/www/html/w/includes/installer/DatabaseUpdater.php(482): MysqlUpdater->doPageRandomUpdate() #2 /var/www/html/w/includes/installer/DatabaseUpdater.php(446): DatabaseUpdater->runUpdates(array, boolean) #3 /var/www/html/w/maintenance/update.php(200): DatabaseUpdater->doUpdates(array) #4 /var/www/html/w/maintenance/doMaintenance.php(94): UpdateMediaWiki->execute() #5 /var/www/html/w/maintenance/update.php(245): require_once(string) #6 {main}- I then set unset $wgreadonly and the upgrade proceeded with no error.
- Not displaying the error message is a bug. Should it be reported as a new bug, or add this report to Bug T151833?
- Bug T151833 also provides a good solution to have the wiki set to read-only for users, but unset for command line updates.
- I recommend this implementation for the user manual: Can my wiki stay online while it is upgrading?
- Alternatively, you can also place the wiki in read-only mode for users, but keep the wiki writable for the upgrade script.
$wgReadOnly = ( PHP_SAPI === 'cli' ) ? false : 'This wiki is currently being upgraded to a newer software version.';
- ----
- A side effect of setting $wgReadOnly during the upgrade is that I am prevented from logging in to my wiki. I am using https:// protocol. This error message is displayed:
There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form.
- Perhaps Manual:$wgReadOnly should be updated? Lady G2016 (talk) 02:59, 5 September 2018 (UTC)
- I've added this information to Manual:$wgReadOnly Ciencia Al Poder (talk) 09:42, 5 September 2018 (UTC)
- My production wiki has been successfully updated. I have created Bug T203914 to report the missing error message.
- Suggestion: Please link the revised $wgReadOnly configuration to the upgrade page.
- I recommend changing the text from:
- Place the database in read-only mode by inserting the following variable into LocalSettings.php in the old directory - users will see this message if they attempt an edit during the upgrade process:
$wgReadOnly = 'Upgrading to MediaWiki 1.45.3';- This no longer works since MediaWiki 1.27, which also prevents running the update script. See T151833.
- Place the database in read-only mode by inserting the following variable into LocalSettings.php in the old directory - users will see this message if they attempt an edit during the upgrade process:
- To:
- Place the database in read-only mode by inserting the following variable into LocalSettings.php in the old directory - users will see this message if they attempt an edit during the upgrade process:
$wgReadOnly = 'Upgrading to MediaWiki 1.45.3';- This no longer works since MediaWiki 1.27, which also prevents running the update script. A workaround for versions since MediaWiki 1.27 can be found in $wgReadOnly. Also see T151833. Lady G2016 (talk) 17:14, 9 September 2018 (UTC)
- Place the database in read-only mode by inserting the following variable into LocalSettings.php in the old directory - users will see this message if they attempt an edit during the upgrade process:
- Done. Ciencia Al Poder (talk) 20:08, 12 September 2018 (UTC)
Can't identify category for Mediawiki srnamespace parameter
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I would like to issue requests like the following. I'm unable to find values for the namespace parameter that are acceptable. Please give me some guidance. I want to limit searches to the cookbook itself, preferably to items in the, or a, recipe category.
https://en.wikibooks.org/w/api.php?action=query&list=search&srnamespace=Cookbook:Recipes&srsearch=meatballs&format=xml SewerCat (talk) 18:04, 26 July 2017 (UTC)
- Manual:Namespaces MacFan4000 (talk) 18:07, 26 July 2017 (UTC)
- Thank you. I think I've grasped something of the meaning of that page. I regret to say I don't know what a suitable parameter value might be instead of 'Cookbook:Recipe'. Please, throw me a bone. :) SewerCat (talk) 18:36, 26 July 2017 (UTC)
- List of namespaces: https://en.wikibooks.org/w/api.php?action=query&meta=siteinfo&siprop=namespaces
- Cookbook is namespace 102. Note that there's no 'Cookbook:Recipe' namespace Ciencia Al Poder (talk) 21:36, 26 July 2017 (UTC)
how to count MW's ParserCache hit rate?
There were lots of pages talking about Wikipedia's Parser cache hit rate (e.g. https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-03-19/Technology_report)
However, I can't find any page documented in mediawiki.org about how to count ParserCache hit rate for their own wiki. Currently I knew that my Varnish cache hold about 70% hit of request, uAPC 85%, and redis 80%. Is there a way to only count hit rate for ParserCache? Deletedaccount4567435 (talk) 20:39, 26 July 2017 (UTC)
Unable to use FileCache
So I tried to enable filecache with following settings:
$wgUseFileCache = true;
$wgUseGzip = true;
$wgFileCacheDirectory = "/var/cache/mw-filecache";
mw-filecache folder were set to 777, php-zlib installed. But nothing generated. So I tried RebuildFileCache.php. Then all the pages showing:
Page 'xxx' (id 962) not cacheable
How can I identify the cause of this "not cacheable" problem? Deletedaccount4567435 (talk) 21:43, 26 July 2017 (UTC)
MediaWiki GraphViz Extension not rendering images
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello!
I'm trying to set up a XAMPP Server PHP v5.6 which is supposed to run MediaWiki v.1.28.2 and GraphViz v.2.38.
I installled the GraphViz and ImageMap extension and set $wgGraphVizSettings (execPath) to the bin.exe. If I edit an article, the added GraphViz Code won't render the image. It throws an empty <p class="error"></p> tag. I'm having trouble figuring out where exactly the problem is and where I'm missing something. There is no error code, no message, just an empty blank box. Rendering externally and uploading via edit works though.
I spent some time researching but it's hard to find answers to this specific problem.
So any idea how to resolve this problem will be much appreciated.
If you need any more information feel free to ask.
Link to my Dropbox with three log screenshots
Greetings 87.139.209.139 (talk) 11:56, 27 July 2017 (UTC)
- Do you have a GraphViz on your main page? because otherwise the screenshots are of no use.
- The extension provides several logs that should appear in the debug log if the extension is actually doing anything on the page being rendered. To be sure it doesn't get cached, try to preview a page that contains a GraphViz and see what the logs say.
- Since logs are plain text, you can share them by pasting it in http://dpaste.de/ or pastebin, and providing the link here. Ciencia Al Poder (talk) 13:29, 27 July 2017 (UTC)
- Thanks for being so patient with me. So I edited the Main Page and added a GraphViz Code.
- Here's the log: https://dpaste.de/R8S5 87.139.209.139 (talk) 13:40, 27 July 2017 (UTC)
- From the logs I see MediaWiki is trying to execute this command:
"C:/Users/Lucas/Documents/release/bin/dot.exe" -T "gif" -o "C:\XAMPP\apps\mediawiki\htdocs\images\graphviz\images\File_graph_GraphVizExtensionDummy_dot.gif" "C:\XAMPP\apps\mediawiki\htdocs\images\graphviz\File_graph_GraphVizExtensionDummy.src"- (and other variants, with jpg, jpeg and png extensions).
- It first creates the file C:\XAMPP\apps\mediawiki\htdocs\images\graphviz\File_graph_GraphVizExtensionDummy.src, I guess that's a plain text file with the contents of the GraphViz tags. Try to create it yourself, open a command line and issue the command, to see if it errors out or something. The log says it returns an exit code of 1. Ciencia Al Poder (talk) 15:07, 27 July 2017 (UTC)
TimedMediaHandler just not working
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Once I activate TimedMediaHandler (together with MwEmbedSupport), "File:XXXX" links simply change to red as if the files wouldn't exist (previously they were ok).
Files have been uploaded correctly. Database has been updated after installing extensions.
Tested on a vanilla MW 1.27.3 (LTS) with TMH 1.27 and 1.28. 194.154.200.228 (talk) 14:02, 27 July 2017 (UTC)
- Same with 1.29.0 194.154.200.228 (talk) 14:27, 27 July 2017 (UTC)
- We need more information than that, please see Manual:How_to_debug and provide errors logs. Reception123 (talk) 16:39, 27 July 2017 (UTC)
Infobox help on new wiki
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello. I recently created a new wiki via the XAMPP program. I'm not familiar with the programming, so I need some help. Right now, I'm trying to create the basic Template:Infobox so I can move on and do more specific infoboxes, but I haven't been able to do so.
First, is it possible to integrate the Lua programming language another way besides Extension:Scribunto? I am using a Windows computer, and the article said it required Unix/Linux-based systems.
If that's not possible, how do I bypass Lua to format infoboxes? I tried to copy an old pre-Lua form of Template:Infobox, but my wiki cannot format {{#:if. Any help would be greatly appreciated.
God bless Matthewshill (talk) 17:45, 27 July 2017 (UTC)
- No. Under Windows, Scribunto will run Lua only as "LuaSandbox", so linux is not necessary.
- Also, the #if comes from Extension:ParserFunctions which you should enable Ciencia Al Poder (talk) 15:31, 30 July 2017 (UTC)
- Thanks! I ended up getting Lua and just enables Parser Functions. However, I am getting the following error:
- Parameter 1 to ScribuntoHooks::showDocPageHeader() expected to be a reference, value given in C:\XAMPP\apps\mediawiki\htdocs\includes\Hooks.php on line 195
- It hasn't seem to cause any problems, but it is annoying seeing it at the top of the wiki all the time. Do you or anybody else know what this means? Thanks!
- God bless Matthewshill (talk) 20:45, 31 July 2017 (UTC)
- First, be sure you have downloaded the Scribunto extension that matches your MediaWiki version (1.29 for MediaWiki 1.29, etc).
- You can hide those errors by setting display_errors to off in php.ini Ciencia Al Poder (talk) 09:12, 1 August 2017 (UTC)
Update source of Manual:Pywikibot for translation
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The page Manual:Pywikibot got major changes. Please update Manual:Pywikibot/en and all set of Translations:Manual:Pywikibot/*/en from the source page and mark translations of changed strings as outdated. Dvorapa (talk) 18:45, 27 July 2017 (UTC)
- I marked it for translation. MacFan4000 (talk) 18:54, 27 July 2017 (UTC)
Extensions not updated in 9 years
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Are extensions which haven't been updated in 9 years safe to use? Common sense tells me no, but I don't know if these extensions, being open source, are regularly checked by anyone on MediaWiki? I can't find any evidence of a comprehensive audit ever been done on the extensions though.
Specifically, Extension:Wiki-httpbl hasn't been updated in 9 years and appears to be unmaintained. Same goes for Extension:GroupPermissions - would it be better to archive these extensions if they haven't been audited? Entrusted Capsule (talk) 19:18, 27 July 2017 (UTC)
- Extension:GroupPermissions possibly allowed changing $wgGroupPermissions. However, I would say the save way of dong this is using one of the hooks! The code of the extension no longer is available anyway as Google Code is down. So it is impossible to say, if this old colde in theory might still be working with current versions of MediaWiki. 2003:72:6D1C:EE00:C14:C8AF:141A:321B (talk) 14:24, 28 July 2017 (UTC)
Embed file history on a page
Is it possible to embed a file's history on a page?
I want to embed a file's history on a page related to the file so that someone can download older versions without having to click into the file's page. It would be nice if I can show just the history section of that file. Is that possible? History Smason3346 (talk) 19:26, 27 July 2017 (UTC)
RESET PASSWORD
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I forget my password.i dont can loggin,
at the loggin time noot given the recovery e mail address.
how can loggin?
please help me 2.51.208.104 (talk) 19:43, 27 July 2017 (UTC)
- Do you have SSH access/database access? If you are just trying to login on a wiki, you should contact the local administrators. Reception123 (talk) 08:28, 28 July 2017 (UTC)
Question about how $wgParserCacheType = CACHE_ANYTHING; work
So currently there were two type of cache available in my wiki: 'redis' & CACHE_DB.
'redis' can't store all the ParserCache while CACHE_DB is too slow. (Although CACHE_DB still work faster than re-generate entire page)
When $wgParserCacheType = CACHE_ANYTHING; set.
Does MediaWiki search for the first cache method found and then stick with it (redis have higher priority than DB)?
OR does it query redis first, then if there were no available page in the reids, query DB next? Deletedaccount4567435 (talk) 21:42, 27 July 2017 (UTC)
Removing a boilerplate response from the Response:en list
We have a pretty long list of drop-down boilerplate responses on the Response:en- list, and I am wondering if the clutter might be cut down a bit but don't see a process for nominating any of these for "deletion" (as I would do on the English Wikipedia). I have looked through the basic Help info and saw nothing about this— has a response ever been removed before? How was it done? How can I propose that one or another of the current responses be deleted? Please advise. Thanks! KDS4444 (talk) 06:29, 28 July 2017 (UTC)
Please mark pages for translation
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Please mark Manual:Pywikibot and Manual:Pywikibot/Installation for translation (you can mark also other subpages of Manual:Pywikibot with untranslated changes) Dvorapa (talk) 09:17, 28 July 2017 (UTC)
Rendering blur or not?
At wikimedia commons https://commons.wikimedia.org/wiki/Help:Inkscape#Bugs_and_workarounds it's written like this: "W3C states that SVG supports blurring effects. Inkscape version 0.46 provides blurring. Unfortunately, the rendering program rsvg used on MediaWiki does not support blurring. Therefore please avoid using blurring."
But I have made a test file test_blur.svg (you can download it) which I have run thru SVG checker. The test file consist of blur in an Inkscape svg file (plain svg), on the left side is the svg blur but on the right side is a png version of the left side so you can see if blur works here at commons. To me it works despite what is written.
So I really need an answer on this as I do some svg work at commons, thanks. --~~~~ Goran tek-en (talk) 18:04, 28 July 2017 (UTC)
Using 'twitter' as an internal link is not shown
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello,
For a couple of years I have been maintaining a mediawiki-based wiki as a content editor. It has been updated recently to mediawiki version 1.26.3, and I discovered that the wikilinks (or internal links) to our own 'Twitter'-page have stopped working (e.g. [ [ Twitter ] ]). I just tested this in your own sandbox, and there it also doesn't show up.
What gives? I guess this behaviour is caused by giving the term 'twitter' a special status as an immediate redirection to a twitter account.
My questions: a) How can this behaviour be circumvented? Renaming our own Twitter-page is not negotiable. b) Is there a configuration setting that must be altered? If so, how? I'm not the sysadmin, and I must give him very specific instructions. c) Are there other special keywords now to consider?
If all else fails I'm more than willing to step in and butcher the source code, but I'd rather keep my current life PHP-free, peaceful, and civil.
Thanks in advance 77.173.52.241 (talk) 18:54, 28 July 2017 (UTC)
- I forgot to mention that I searched your site and the past help-topics, of course. 77.173.52.241 (talk) 18:57, 28 July 2017 (UTC)
- MediaWiki 1.26 is unsupported, we recommend upgrading. MacFan4000 (talk) 19:00, 28 July 2017 (UTC)
- Since your own current sandbox exhibits <em>same behaviour</em> I'm afraid that upgrading won't make the problem go away. 77.173.52.241 (talk) 07:10, 29 July 2017 (UTC)
- The upgrade recommendation is partially for security reasons too.
- Coming to your query, how exactly did you set these "internal links"? Did you set them in Special:Interwiki or something? AhmadF.Cheema (talk) 08:35, 29 July 2017 (UTC)
- I mean internal wikilinks, like this: A programmer is a person who converts Coca-Cola into code. When a programmer is tired, he uses Twitter for relaxation. 77.173.52.241 (talk) 08:49, 29 July 2017 (UTC)
- Note the missing twitter between 'uses' and 'for' in your own current mediawiki. 77.173.52.241 (talk) 08:50, 29 July 2017 (UTC)
- Apologies, but I'm still unable to understand.
- What missing twitter? Isn't it being shown "between 'uses' and 'for'"? AhmadF.Cheema (talk) 11:49, 29 July 2017 (UTC)
- If I use a WikiWord, like this WikiWord, then a link to another wiki page is created. If the page exists, the word is by default coloured blue. If it doesn't, it is coloured red. This is how MediaWiki works since about the beginning. However, if I use 'Twitter' (or 'twitter') as a wiki word, it doesn't show up at all. Example given: Twitter See? The word 'twitter' isn't showing up at all. Now this happens in MediaWiki version 1.26.3, but also here at www.mediawiki.org at the moment, running at whatever version you do.
- My questions remain: Is this on purpose? If it is: how to circumvent it? If not, I've discovered a bug and I claim my 15 minutes of internet fame ;) 77.173.52.241 (talk) 13:23, 29 July 2017 (UTC)
- Blue coloured 'twitter' is showing up on my end.
- If I have understood your problem correctly, try disabling all browser plugins or opening your Wiki in a different browser. AhmadF.Cheema (talk) 13:34, 29 July 2017 (UTC)
- (Checking with other browsers, phones, etc)<br />
- I'll be darned! It's ad blocker or one of its extensions, which I have running by default everywhere I can. I would have never thought of that. I'm very sorry for your wasted time. I'll look at my ad blocker settings. Thanks all for your patience. 77.173.52.241 (talk) 14:47, 29 July 2017 (UTC)
MW 1.29.0 bug with SyntaxHighlight extension
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
After upgrade MediaWiki from 1.28.2 to 1.29.0 - I am find, what appeared bug Extension:SyntaxHighlight
Not highlight lang "LUA"
Sample:
<syntaxhighlight lang="lua">
there_is_code
</syntaxhighlight>
In the bottom just write: "Pages with syntax highlighting errors" Aka sektor (talk) 00:21, 29 July 2017 (UTC)
- Like in this topic: Project:Support desk/Flow/2017/01#h-syntax_highlighter_doesn't_work_properly-2017-01-17T04:15:00.000Z Aka sektor (talk) 00:55, 29 July 2017 (UTC)
- Is it again developers of MediaWiki allowed mistake in packaging, like in 1.28.0 & 1.28.1? Aka sektor (talk) 01:03, 29 July 2017 (UTC)
- I am assuming the extension worked when you were using MediaWiki 1.28.2.
- Can you again make sure that execute permissions are set for the pygmentize binary:
extensions/SyntaxHighlight_GeSHi/pygments/pygmentize? - Sometimes, upgrades mess up file permissions.
- In case you installed the extension from Git, you will also need to update composer. AhmadF.Cheema (talk) 05:21, 29 July 2017 (UTC)
- Yes, that work on 1.28.2
- How to check execute permissions? I do not understand. I not done this before
- "from Git"
- Not. I just only installed box 1.29.0 from here https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.0.tar.gz Aka sektor (talk) 07:04, 29 July 2017 (UTC)
- I am assuming that you are running MediaWiki on Linux.
- If you have access to SSH, change your directory (cd) to your Wiki directory and run the following command:OR, if you have access to a file explorer for your uploaded files, browse to
chmod a+x extensions/SyntaxHighlight_GeSHi/pygments/pygmentize
<WIKI DIRECTORY>/extensions/SyntaxHighlight_GeSHi/pygments/, there should be a pygmentize file inside and a column for file permissions. See what permissions it has been set. AhmadF.Cheema (talk) 08:32, 29 July 2017 (UTC) - Maybe work this Extension:GoToShell
- I try to use your command Aka sektor (talk) 13:49, 29 July 2017 (UTC)
- Checked. Not any effect. Aka sektor (talk) 13:59, 29 July 2017 (UTC)
- Does your hosting provide a file manager for your uploaded files? Can you visually check what permissions have been set for the pygmentize file?
- OR, if that's not possible run the following command:and see what gets written in foo.txt in your Wiki directory. AhmadF.Cheema (talk) 14:15, 29 July 2017 (UTC)
ls -la extensions/SyntaxHighlight_GeSHi/pygments/pygmentize > foo.txt
- Ok, I do it, this writen in the foo.txt:
- -rwxr-xr-x 1 h99724 h99724 842005 Jul 13 22:15 extensions/SyntaxHighlight_GeSHi/pygments/pygmentize
- Of course I have file manager on hosting, but I use FileZilla and FTP access.
- How check that permissions? Open in the Notepad file pygmentize? But Notepad dont understand file syntax.
- I can only read the first line:
- #!/usr/bin/env python Aka sektor (talk) 15:04, 29 July 2017 (UTC)
- The
-rwxr-xr-xpart in foo.txt are describing the permissions for the pygmentize file, which are fine. AhmadF.Cheema (talk) 15:31, 29 July 2017 (UTC) - Yes, your code for lang python is highlighting.
- But my problem with lang "lua". Aka sektor (talk) 15:39, 29 July 2017 (UTC)
- Apologies, I misunderstood, I thought all languages were having problems highlighting. AhmadF.Cheema (talk) 16:01, 29 July 2017 (UTC)
- No more ideas how to fix the problem? Aka sektor (talk) 18:43, 29 July 2017 (UTC)
- Have to wait for the update 1.29.1 Aka sektor (talk) 17:22, 31 July 2017 (UTC)
- Where update? Aka sektor (talk) 00:45, 4 August 2017 (UTC)
- This issue is present for some users in at-least MediaWiki v1.28.2 too. I think a bug report will need to be filed for this.See, How to report a bug. AhmadF.Cheema (talk) 19:45, 4 August 2017 (UTC)
- In 1.28.2 - it's work 100% Aka sektor (talk) 19:48, 4 August 2017 (UTC)
- Why do not they fix it for so long? Where is the update? Aka sektor (talk) 17:55, 11 August 2017 (UTC)
- Have you already reported this bug on phabricator? AhmadF.Cheema (talk) 18:44, 11 August 2017 (UTC)
- https://phabricator.wikimedia.org/T173301
- So? Aka sektor (talk) 10:55, 14 August 2017 (UTC)
- I understand that with Mediaiki 1.29, the language "lua" no longer gets highlighted.
- Although highlighting worked correctly in MW 1.28.2, I think this is not one of the usual cases where highlighting support was present in older versions of MediaWiki (where in fact GeSHi had still been used), but went away in newer ones. According to https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.0.tar.gz, the extension should parse "lua" just fine...
- Maybe there still are some files from older versions of MediaWiki present inside the installation? 91.248.150.85 (talk) 11:50, 15 August 2017 (UTC)
- For example? What files? Folder Extenisions? SyntaxHighlight_GeSHi ?
- No. I did not touch it. Only installed the engine from the archive.
- I repeat: the extension works partially.
- If I did something, it would not work at all Aka sektor (talk) 12:06, 15 August 2017 (UTC)
- I have the same problem.
- Maybe this could be the problem?
| Product | Version |
|---|---|
| MediaWiki | 1.29.0 |
| PHP | 5.6.29 (cgi-fcgi) |
| MariaDB | 10.1.20-MariaDB |
| SyntaxHighlight | 2.0 (f18e070)21:05, 17 May 2017 | GPL-2.0+ | Provides syntax highlighting <syntaxhighlight> using Pygments - Python syntax highlighter
|
Brion Vibber, Tim Starling, Rob Church, Niklas Laxström, Ori Livneh and Ed Sanders |
- No. This 100% mistake of developers MediaWiki. They already admitted this error in versions 1.28.0 & 1.28.1
- Check: https://lists.wikimedia.org/pipermail/mediawiki-announce/2017-April/000209.html
- "Due to a mistake in packaging, the releases 1.27.2 and 1.28.1 did not contain the fix for SyntaxHighlight_GeSHi. This new release does contain that fix."
- Nothing remains, except how to expect the release of the next version 1.29.1 Aka sektor (talk) 11:58, 19 August 2017 (UTC)
- I would now download the MediaWiki tarball again and extract it somewhere on the server. Then I would run diff to compare the newly downloaded files with what is present in the installation. This will show which additional files are there... 2003:72:6D05:7900:EDB3:E480:1C2A:17 (talk) 10:41, 19 August 2017 (UTC)
- It looks like a mistake already known to them: https://phabricator.wikimedia.org/T59159
- My task closed: https://phabricator.wikimedia.org/T173301 Aka sektor (talk) 06:37, 21 August 2017 (UTC)
- The old phabricator task appears to be limited to only when using Extension:Flow, and with all languages. Your issue comes up outside of Extension:Flow and is only related to the Lua language. I do not believe that the two phabricator tasks (bug reports) are the same. AhmadF.Cheema (talk) 10:55, 21 August 2017 (UTC)
Including Recent Changes: more than 1 namespace at once
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello, I just found out I can include Special:RecentChanges and I plan using this feature a lot but I need to include RC from a selection of different namespaces, all at once. Is it possible to specify more than 1 namespace? The alternative is including multiple instances of RC but obviously that would be far from optimal. 91.253.214.2 (talk) 09:43, 29 July 2017 (UTC)
- This is possible in Wikimedia Wikis, through the New filters for edit review beta feature, where filters for namespaces (T159942) have been included.
- Multiple namespaces in transcluded Special:RecentChanges appeared to be working as expected on Wikipedia by separating namespace numbers with semicolons.
- However, I presently don't know how this can be used for third-party Wikis. You will probably need the latest version of MediaWiki core for this. AhmadF.Cheema (talk) 13:30, 29 July 2017 (UTC)
- Good to know, thanks! 91.253.113.109 (talk) 06:37, 30 July 2017 (UTC)
Saraiki as interface language
Saraiki is mostly written with Saraiki alphabet which is extended form of Arabic . But in suggested languages there two languages as سرائیکی . Kindly these both be merged. Because the both are same.
Language code Skr
https://incubator.wikimedia.org/w/index.php?title=Wp/skr/Main_Page Sraiki (talk) 11:19, 29 July 2017 (UTC)
Project:Support desk
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi, I want this same page (project:support desk) on my local installation. Not able to find any information on this. 122.176.183.128 (talk) 11:27, 29 July 2017 (UTC)
- A flow board is run on this page. You can find more information on it at Extension:Flow. AhmadF.Cheema (talk) 11:50, 29 July 2017 (UTC)
- Related to this, couldn't we include somewhere on this page the extension this page is using? I've counted at least five different people who have been asking the same thing and that's just in the past two months. Maybe in the description? │Star-Warden│ 18:32, 29 July 2017 (UTC)
line-height
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello, I'm desperately trying to decrease the "line-height" globally on my mediawiki instance. I've tried in Common.css in "body", "#bodyContent", it does not work (although changing the font-size for example work!), the only way I've been able to change the line-height is by saving the source file locally and adding <div id="bodyContent" style="line-height: 1.1;">, this is so ludicrously frustrating!!!
In summary, how do I change the "line-height" globally please heeeelp thank you!!! 178.12.45.222 (talk) 11:42, 29 July 2017 (UTC)
- In your MediaWiki:Common.css, try:AhmadF.Cheema (talk) 12:42, 29 July 2017 (UTC)
.mw-body-content { line-height: 5; } - Thank you but it does not work, I don't seem to have a "mw-body-content" class in my mediawiki install, probably because I use an older version.
- 1) Could you please tell me why changing font-size in #bodyContent work but changing line-height does not work?
- 2) Could you offer another solution (other than upgrading because upgrading is really not a workable solution for me)?
- Many thanks in advance :) 178.12.45.222 (talk) 12:55, 29 July 2017 (UTC)
- Exactly which MediaWiki version are you using and additionally did you remember to clear browser cache? Maybe try opening the page in another browser to be sure. AhmadF.Cheema (talk) 13:36, 29 July 2017 (UTC)
- I use an older version at the moment, it's all I can say about that here sorry.
- I clear my cache every time I test indeed, font-size was working so it was not a cache problem.
- I've managed to make it work and obtained what I want, I am not too sure why this way of doing works and not just using #bodyContent does not work but anyway, here is the code that works for me, maybe that will be helpful for other people.
- So in MediaWiki:Common.css I added:
- /* line-height code that works for evth except p and br */
- * {
- line-height: 1.20;
- }
- /* line-height code that works for p */
- #bodyContent p {
- line-height: 1.20;
- }
- /* line-height code that works for br */
- #bodyContent br {
- line-height: 0.5;
- }
- That was driving me mad so much, such a relief!
- Anyway thank you for trying to help, very appreciated, have a nice day :) 178.12.45.222 (talk) 14:17, 29 July 2017 (UTC)
Error creating thumbnail, but only for SVG files, and only on sub-wiki's
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have a site like Wikimedia Commons (let's call it myCommons) that hosts files for other wiki's (myWiki). Everything works as expected for all file types (jpg, png, etc.). However, if I upload an SVG file to myCommons and try and render a thumbnail on myWiki, it gives the following error:
Error creating thumbnail: convert.im6: unable to open image `/tmp/svg_746a145a131552f62fa01450/Category.svg': No such file or directory @ error/blob.c/OpenBlob/2641.
convert.im6: no images defined `PNG:/tmp/transform_1cbe4b65bbc4.png' @ error/convert.c/ConvertImageCommand/3044.
Thumbnail generation on myCommons works as expected. Subsequently, that thumbnail can be referenced on myWiki without a problem. I could use some help in trying to troubleshoot this issue. T0lk (talk) 03:01, 30 July 2017 (UTC)
- Do you have rsvg binaries installed? Ciencia Al Poder (talk) 09:09, 1 August 2017 (UTC)
- No I don't think I do. I've been using ImageMagick for everything. T0lk (talk) 10:30, 1 August 2017 (UTC)
- I installed rsvg and set $wgSVGConverter and $wgSVGConverters appropriately but there was no change. T0lk (talk) 22:30, 1 August 2017 (UTC)
- See how to enable a debug log in Manual:How to debug and open a page that has to render a SVG thumbnail, and see if it the debug log provides additional information. It usually prints the exact command being executed for thumbnailing (either imagemagick, rsvg, etc) and what error codes return or other output. Ciencia Al Poder (talk) 09:30, 2 August 2017 (UTC)
- Thank you for your help. I don't think I have the expertise necessary to debug this, and since I have a work-around I'm probably going to let it go. In case someone else comes across this, the only new debug info I got was:
File::transform: Doing stat for mwstore://shared-backend/shared-thumb/a/a3/Category.svg/87px-Category.svg.png[FileOperation] FileBackendStore::getFileStat: File mwstore://shared-backend/shared-thumb/a/a3/Category.svg/87px-Category.svg.png does not exist.T0lk (talk) 16:28, 5 August 2017 (UTC)
How do I find the current logged in user's session ID?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I'm trying to grab the current logged in user's session ID and I can't seem to figure out how to do it. Is there a function or what should I be looking at to get the session ID?
I'm trying to get something along the lines of $sessionID = something_to_get_the_actual_session_ID
I've looked at getSessionById but that doesn't seem to be it (or how do I use it properly?)
There's also WebRequest, but how do I actually grab $webRequest, since it's an undefined variable if I just enter that. Getting session_id() returns nothing.
Thanks. Sessions A (talk) 05:34, 30 July 2017 (UTC)
- There should be no good reason to get a user's session ID. What do you want to achieve? Ciencia Al Poder (talk) 09:08, 1 August 2017 (UTC)
$wgLogo Default
Hi Attempted to change default logo. Made a bit of a mess. Cannot access wiki. Could somebody please give me the setting for the default logo, that is to complete the line:
$wgLogo =
Thanks Ron Barker (talk) 16:55, 30 July 2017 (UTC)
- According to
$wgLogo, that would be"{$wgScriptPath}/resources/assets/wiki.png". —Mainframe98 talk 17:09, 30 July 2017 (UTC)- Thank for the reply. Tried but no luck. Ron Barker (talk) 18:04, 30 July 2017 (UTC)
- Hi,
- if your logo already exist in common/images, try to set you Logo this way :
- $wgLogo = "$wgStylePath/common/images/_your_Logo.png
- hope this helps.
- Regards, 185.66.155.32 (talk) 09:08, 2 August 2017 (UTC)
- Thanks, not sure about 'common/images/. The path is: https://localhost/xampp/htdocs/mediawiki/images/8/89/Logo.SAS.jpg
- Placed at bottom of local settings? Ron Barker (talk) 10:17, 2 August 2017 (UTC)
- If you can no longer access the Wiki, then it probably means that while editing your LocalSettings.php file, you inadvertently made some syntax mistakes (like a missing semicolon or something).
- If I'm not mistaken, you can also simply remove the $wgLogo line from your LocalSettings.php file, for the variable to go back to its default value. AhmadF.Cheema (talk) 17:13, 30 July 2017 (UTC)
- Thanks Ahmad, removing $wgLogo line altogether but still not able access wiki. Ron Barker (talk) 18:07, 30 July 2017 (UTC)
- This is probably a syntax typo. You can check your PHP code syntax from:
- http://infoheap.com/php-lint-online/
- Input your LocalSettings.php code there, which might show any syntax typos if present. AhmadF.Cheema (talk) 18:34, 30 July 2017 (UTC)
- Thank you Ahmad; this is what I have: $wgLogo = "{$wgScriptPath}/resources/assets/wiki.png";
- Reported no syntax errors. I don't think that I made any other changes by mistake to local settings! Ron Barker (talk) 18:56, 30 July 2017 (UTC)
- Thank you for your assistance. Wiki is working. Not sure what went wrong. I will have to do with the default Logo for now. Cheers. Ron Barker (talk) 05:54, 31 July 2017 (UTC)
- Hi I am still having problems with my logo and from the above posts it seems I am not the only one!
- The default logo is [no longer] showing...removed from local settings:
- $wgLogo = "{$wgScriptPath}/resources/assets/wiki.png"; line 38
- I have change upload in local settings to 'true'
- This is what I have placed at the bottom of local settings:
- $wgLogo = https://localhost/xampp/htdocs/mediawiki/images/Logo.SAS.jpg;
- I have placed the 135 x135 logo in the images folder.
| Product | Version |
|---|---|
| MediaWiki | 1.28.2 |
| PHP | 5.6.30 (apache2handler) |
| MariaDB | 10.1.21-MariaDB |
Ron Barker (talk) 08:04, 2 August 2017 (UTC)
- Shouldn't your code lineactually be:
$wgLogo = https://localhost/xampp/htdocs/mediawiki/images/Logo.SAS.jpg;
Not using quotes gives syntax errors. (PHP Code Checker) AhmadF.Cheema (talk) 11:05, 2 August 2017 (UTC)$wgLogo = "https://localhost/xampp/htdocs/mediawiki/images/Logo.SAS.jpg";
- Ahmad
- Yes, sorry. I am using quotation marks in local settings. I copied without quotes from checking online search which brings of error object not found. Ron Barker (talk) 12:31, 2 August 2017 (UTC)
Mark for translation
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.