Topic on Project:Support desk

Hello,

I have read several pages about Info box's and it was working on my last install of MediaWiki and had to be removed due to a MASSIVE spambot attack.

I have imported Template:Infobox from Wikipedia, and all I get is: I tried to install Lua/Scribunto and all I got was several errors.

The theme Template is: http://wiki.myfallen.net/index.php?title=Template:Infobox

The pages having the issue is: http://wiki.myfallen.net/index.php?title=Community_Managers and many.. many more.

We are using MediaWiki 1.21.1

Thanks for your potential help.

Kris.

I just added your wiki to WikiApiary: http://wikiapiary.com/wiki/MyFallen_Wiki

Are there any errors in your error log? I haven't worked with Scribunto yet, but I wonder if turning on the debug log would help.

Error log completely clean it just comes up with in a red box "Execution Error"

From Scribunto: [6d3bfde6] 2013-06-13 13:48:15: Fatal exception of type ScribuntoException

You want to import a few modules that can be exported out of wikipedia.

• Module:Infobox
• Module:InfoboxImage
• Module:HtmlBuilder
• Other Module:Infobox[whatever] modules you might need.

You'll also need to change all instances of "text/plain" to "CONTENT_FORMAT_TEXT" in the exported file for some reason.

And that should do it!

Any update on this error? I seem to have the same. Followed the export/import of all templates, changed the two text/plain occurances, added extension scribunto, and get the fatal exception of type ScribuntoException error, similar as described above.

Clicking on the error should give you a message. What do you see?

Hmmm, can't seem to click on it (Scibunto v 1.21), MediaWiki 1.21.1. Screen only shows: "Internal Error" [180e4cd3] 2013-07-23 12:06:39: Fatal exception of type ScribuntoException

Is your wiki public? Could you provide a URL?

Also, try adding the following two lines to your LocalSettings.php file:

 error_reporting = E_ALL | E_STRICT
 display_errors = On

That may give you a better hint.

Using my site as a startup site for non-encyclopedic salinity related information: wiki.agwaterconsult.com. A first attempt to add the two suggested lines to the LocalSetting.php file results in an internal server error. I'll try to find out what I did wrong.

Update: found the debug options on Manual:How_to_debug. I used the error_reporting( -1 ); ini_set( 'display_errors', 1 ); commands in the LocalSetting file. Wiki pages load without additional error messages. Infobox template still shows an error on the page.

Then tried to use the three debugging options (ShowExceptionDetails etc) mentioned in the the same Manual section. Result an "internal server error" and no loading of wiki page. I'll have to review the server settings - will get back on this.

sorry, my fault. I copy-pasted the wrong lines from How to Debug. Glad you found the fix.

Do you have "$wgShowExceptionDetails = true;" at the end of your LocalSettings.php? That should show plenty of errors, I think.

Hmmm, reason that the LocalSettings debug options not worked was that I forgot the semi-colon at the end of the sentence. It helps to be awake when doing this.

Now I have an output with a long list of backtrace and php steps. I prefer not to post the whole error list here, but some lines of interest are:

top of the page, within the wiki form:

 Lua error: Internal error: The interpreter exited with status 126.

Followed by a backtrace, of which the first lines are

1. 0 [*server name*]//engines/LuaStandalone/LuaStandaloneEngine.php(454): ScribuntoEngineBase->newException('scribunto-luast...', Array)
2. 1 [*server name*]/[*folder*]/engines/LuaStandalone/LuaStandaloneEngine.php(324): Scribunto_LuaStandaloneInterpreter->checkStatus()
3. 2 [*server name*]/[*folder*]/engines/LuaStandalone/LuaStandaloneEngine.php(287): Scribunto_LuaStandaloneInterpreter->receiveMessage()
4. 3 [*server name*]/[*folder*]/engines/LuaStandalone/LuaStandaloneEngine.php(213): Scribunto_LuaStandaloneInterpreter->dispatch(Array)
5. 4 [*server name*]/[*folder*]/engines/LuaCommon/LuaCommon.php(114): Scribunto_LuaStandaloneInterpreter->registerLibrary('mw_interface', Array)
6. 5 [*server name*]/[*folder*]/engines/LuaCommon/LuaCommon.php(89): Scribunto_LuaEngine->registerInterface('mw.lua', Array, Array)
7. 6 [*server name*]/[*folder*]/engines/LuaStandalone/LuaStandaloneEngine.php(8): Scribunto_LuaEngine->load()

[*folder*] above is [wiki/mediawiki-1.21.1/extensions/Scribunto]

then, in the php steps,

[...]
Unstubbing $wgAuth on call of $wgAuth::getCanonicalName from User::getCanonicalName
User: cache miss for user 1
[...]
SpecialPage::getContext called and $mContext is null. Return RequestContext::getMain(); for sanity
Title::getRestrictionTypes: applicable restrictions to User:*Xxxxx* are {edit,move}
Class PEAR_Error not found; skipped loading
[...]

Would the problem be described by the 'getContext called and $mContext is null' ? Or is the missing 'PEAR_Error not found; skipped loading' the main issue ?

Update 1: 'PEAR_Error not found' also appears in the debug list on a page where no infobox is called. Is probably unrelated to the Scribunto error.

Update 2: Also copied the Template:Reflist to my wiki (using export/import functions), while Scribunto extension was disabled in the LocalSettings.php. Import of the xml file was incomplete, with a message "Import failed: No handler for model 'Scribunto' registered in $wgContentHandlers" at the bottom of the template import list. This may be a different issue altogether, and one of the search hits refered to this bug. When Scribunto extension is enabled, I am having the same error message as for the Template:infobox issue.

This looks like the same problem in this thread. Make sure the lua binaries are marked as executable. If you still have problems post a follow up here.

Thanks for the help so far. I was getting excited about the relatively simple solution to make the lua binaries executable. Changed the mod for lua5_1_5_linux_32_generic/lua from 0644 to 0755 (as well as for linux_64_generic), but that did not solve the problem. Checked the folder settings, all 0755. Server is hosted by ipower, runs Debian. Is contacting the provider the next step?

P.S. I noticed the Apiary visiting in the access log. Thanks for that - I updated the info there, and footered it in.

I got frustrated yesterday with a the lack of feedback from Scribunto yesterday and filed a few bugs. One of the things I noticed was that the error output of lua was completely dropped.

In your LocalSettings, after the bit to include Scribunto, put the following:

$wgScribuntoEngineConf['luastandalone']['errorFile'] = '/tmp/lua-error.log'

and try again. See if anything is recorded in /tmp/lua-error.log.

I had to use a double quote around the filename for it to work properly. Error messages for page calls where scribunto/lua is called end up with a "permission denied" (using the linux-32 version of Lua). That would be the same as the error 126 issue. I'll check with the server host to see if there are settings that I am overlooking.

I read the exchange on the bug-report. Clearly a difference of opinion on error-logging. I'll remain neutral - I can't criticize people's hard work either way, I'll just appreciate it all.

Will report back here about progress on the server host response.