Difference between revisions of "Wikispooks talk:Site Status"
(Software bug) |
(Clarify reporting protocol) |
||
Line 1: | Line 1: | ||
==Site Issues== | ==Site Issues== | ||
− | Wikispooks has some known issues (a.k.a. bugs). This is the place for reporting those which the site management should fix. | + | Wikispooks has some known issues (a.k.a. bugs). This is the place for reporting those which the site management should fix. ''Please include the date in the title, and put the newest at the top, so if you've found an issue which is not in the list below, it belongs just below this text.'' |
===No thumbnailing (2014-06-12)=== | ===No thumbnailing (2014-06-12)=== |
Revision as of 16:07, 12 June 2014
Contents
Site Issues
Wikispooks has some known issues (a.k.a. bugs). This is the place for reporting those which the site management should fix. Please include the date in the title, and put the newest at the top, so if you've found an issue which is not in the list below, it belongs just below this text.
No thumbnailing (2014-06-12)
Something has broken the image thumbnailing system. So new thumbnails are not created correctly, e.g Aamer Anwar. IIRC, there are at least two ways of thumbnailing, and a PHP variable switches between the two. Robin (talk) 16:58, 12 June 2014 (IST)
Special:ReplaceText (2014-03-18)
- Special:ReplaceText pretends to work, but the changes don't happen. This is slowing down the SMW rollout, since it is needed to tidy the object parameters. Robin (talk) 16:56, 18 March 2014 (GMT)
"Publish to {{SITENAME}}" (2014-03-18)
That is the headline of the modal dialog box on pages after clicking the top right "Publish" button. Robin (talk) 16:56, 18 March 2014 (GMT)
Scribunto and SMW data errors (2014-02-12)
The are two distinct issue that show when rebuilding Semantic Data:
1. a php Notice
that objects to the variable assigned to SERVER_NAME
. This now affects just one record. The error message is:
PHP Notice: Undefined index: SERVER_NAME in /wikipath/includes/GolbalFunctions.php on line 1743
- and Yes, the mis-spelling of 'GlobalFunctions.php' IS the actual message generated.
This is probably related to edits done on the new server before the DNS records were changed and LocalSettings.php
contained the IP address rather than the host and domain names - With just 1 affected record I'm not too bothered about it.
2. A fatal php error that halts the SMW_refreshDate.php
script at each affected record (there are 17 of them). This is more serious because it halts the automatic jobs queue updating with unpredictable results. With $wgShowExceptionDetails= true;
, this is the full exception report on each record ID number:
(0) Processing ID 7778 ...
[059acad5] [no req] Exception from line 322 of /wikipath/includes/content/ContentHandler.php: No handler for model 'Scribunto' registered in $wgContentHandlers
Backtrace:
0 /wikipath/includes/content/ContentHandler.php(262): ContentHandler::getForModelID(string)
1 /wikipath/includes/Title.php(4823): ContentHandler::getForTitle(Title)
2 /wikipath/includes/parser/Parser.php(837): Title->getPageLanguage()
3 /wikipath/includes/parser/Parser.php(844): Parser->getTargetLanguage()
4 /wikipath/includes/parser/Parser.php(3362): Parser->getConverterLanguage()
5 /wikipath/includes/parser/Preprocessor_DOM.php(1114): Parser->braceSubstitution(array, PPFrame_DOM)
6 /wikipath/includes/parser/Parser.php(3149): PPFrame_DOM->expand(PPNode_DOM, integer)
7 /wikipath/includes/parser/Parser.php(1212): Parser->replaceVariables(string)
8 /wikipath/includes/parser/Parser.php(395): Parser->internalParse(string)
9 /wikipath/includes/content/WikitextContent.php(300): Parser->parse(string, Title, ParserOptions, boolean, boolean, integer)
10 /wikipath/extensions/SemanticMediaWiki/includes/ContentParser.php(155): WikitextContent->getParserOutput(Title, integer, NULL, boolean)
11 /wikipath/extensions/SemanticMediaWiki/includes/ContentParser.php(112): SMW\ContentParser->fetchFromContent()
12 /wikipath/extensions/SemanticMediaWiki/includes/jobs/UpdateJob.php(102): SMW\ContentParser->parse()
13 /wikipath/extensions/SemanticMediaWiki/includes/jobs/UpdateJob.php(79): SMW\UpdateJob->runContentParser()
14 /wikipath/extensions/SemanticMediaWiki/includes/jobs/UpdateJob.php(52): SMW\UpdateJob->runUpdate()
15 /wikipath/extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_S QLStore3_SetupHandlers.php(401): SMW\UpdateJob->run()
16 /wikipath/extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_SQLStore3.php(410): SMWSQLStore3SetupHandlers->refreshData(integer, integer, boolean, boolean)
17 /wikipath/extensions/SemanticMediaWiki/maintenance/SMW_refreshData.php(148): SMWSQLStore3->refreshData(integer, integer, boolean, boolean)
18 {main}
Posted here for the record and to assist with resolving the issue
These 19 records return the errors with both Scribunto and the php cache (APC) disabled, so the records themselves contain Scribunto-related information that the script cannot deal with.
My initial problem is that I do not know what exactly the 'Record ID' refers to because there is NOT a 1:1 relationship between it and individual pages. - ALL FI --Peter P (talk) 10:17, 12 February 2014 (GMT)
- No specific ideas on this. Does http://trog.qgl.org/20110815/setting-up-infobox-templates-in-mediawiki/comment-page-1 this] help at all? Robin (talk) 14:51, 12 February 2014 (GMT)
More on Scribunto
I am now certain that the red 'script error' messages that appear here and there - especially in cite reference lists - are the result of this server have Perl Compiled Regular Expression Library (PCRE) V 7.8, whereas the extension spec calls for >=8.1. The only way to upgrade PCRE on this server OS is to move to php V 5.5.xxx. This can be done but there are potential issues and, since php/MySQL are absolutly fundamental to the entire site, they need sorting out first. The most problematic is that there are core Mediawiki scripts which still contain calls to deprecated functions. With the version we are running this only generates a warning which can be (and is) suppressed but, in php V 5.5 they may have been dropped altogether. If so, an upgrade would break the site and I need to be certain about these things before proceeding. So, summary: Let's live with those script errors for now because at some time in the future, hopefully sooner rather than later, they will fix themselves. --Peter P (talk) 19:26, 16 February 2014 (GMT)