Jump to content

Topic on Extension talk:UserExport/Flow

Kghbln (talkcontribs)

Hello, I have upgraded from MW 1.17 to 1.19. With 1.17, no pb, extension works fine. But with 1.19, I get this fatal error: Fatal error: Call to undefined method Xml::hidden() in /homez.504(...)/extensions/userexport/userexport.body.php on line 46 Any ideas? Many thanks.

Kghbln (talkcontribs)

Hi, I believe the fastest way get help it to contact the coder of this extension on Github and/or to open an issue there. Cheers

Kghbln (talkcontribs)

I would try changing Xml::hidden to Html::hidden on lines 46 and 47.

This post was posted by Kghbln, but signed as Krenair.

86.214.41.65 (talkcontribs)

Many thanks, it works fine with these changes.

Stefahn (talkcontribs)

I changed Xml to Html on lines 46 and 47 as suggested. I can download the csv file. However it doesn't contain user information but a set of error messages. The first one says:

<b>Warning</b>:  tempnam() [<a href='function.tempnam'>function.tempnam</a>]: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/var/www/web1234/html/:/var/www/web1234/phptmp/:/var/www/web1234/files/:/var/www/web1234/atd/:/usr/share/php/) in <b>/var/www/web1234/html/mediawiki_test/mediawiki/extensions/UserExport/userexport.body.php</b> on line <b>59</b><br />

Anyone knows how to fix this? Thanks.

Kghbln (talkcontribs)

Your problem is cause by the "open_basedir" setting in you php.ini so you will have to fiddle around with this setting on your server.

Stefahn (talkcontribs)

Just for the record:
I couldn't change the open_basedir setting (since I am on a shared hosting).
But I got it working by inserting one of the paths (shown in open_basedir) instead of "sys_get_temp_dir()" :)

Stefahn (talkcontribs)

Just for the record:
In current versions (Extension: 9th commit in Github, Core: MW 1.23.1) I still had to replace "sys_get_temp_dir()" with a path given in the error message. Might be a problem that is only related to my hosting...

The xml/html issue is fixed in the code though. Thanks for that!

Kghbln (talkcontribs)

According to pages found by Google it seems to be a hoster specific configuration problem.