Extension talk:WikiFarm

Previous page history was archived for backup purposes at Extension talk:WikiFarm/LQT Archive 1 on 2015-07-10.

I have MW 1.22.6 and I have encountered this problem.
I do not understand how to solve it. I commented the line 7 in WikiFarm_body.php, but the problem persists. What is wrong?

These functions must be commented in the 6-7 classes, so probably the error message changed a bit and is something like /extensions/WikiFarm/WikiFarmStatistics/WikiFarmStatistics_body.php.

This extension needs updating in order to work with Mediawiki versions 1.21+ and with newer versions of php/mysql. Lots of errors are received about deprecated function calls (if you can even get that far).

I have discussed some of the issues with the developer by email, but hit more once I get past those initial ones (Fatal call to wfLoadExtensionMessages mentioned already).

I just also tested, first with MW 1.28 and 1.25 with PHP7.0 but it didn’t work at all. Then with MW 1.20 with PHP5.6, and it worked with some changes:

• commented the 6-7 occurences of wfLoadExtensionMessages, as said in other comments
• added a comma (,) in the penultimate argument in WikiFarm_config.php (else blank page)
• and MediaWiki had an issue probably with PHP5.6 in includes/MagicWords.php, I changed (?P<{$i}_{$name}> to (?P<i{$i}_{$name}> in getBaseRegex()

I explore the world of wiki farms (I created an extension to manage wiki farm configurations) and I find this extension quite useful (спасибо), but some work is needed to update it. If I can find some time, I can help in updating it.

I keep getting a blank page when I try to see my managed wikis. Is there an English setup page likw the Russian one?

Try new version. If it does not work, write me e-mail (I'm a seldom visitor here) with more information, attach config file (witout passwords) Pavel Malakhov ^(talk) (talk) 04:42, 24 October 2012 (UTC)

Good job~ Let me try it. By the way, i think an extension package usually contains a directory instead of separate files, which makes it easier to deploy.

Hm... I thought I made it in a directory. See v1.0 I've tested it: it's all in one directory and every module is in it's own subdirectory.