Invalid argument supplied for foreach() in C:\xampp\htdocs\PslZend SearchLuceneIndexer.php on line 421

Jump to: navigation, search

Thank you so much for your reply. But the database dump was successful and internal_current.xml file was successfully created too. All other settings are almost exactly according to guide how to install it.

As I understand indexer is independent on LocalSettings.php, so shouldn't matter if I have some misconfiguration there.

Rien Satori23:32, 21 June 2011

Yes indexer is independent on LocalSettings.php.

Steviex217:13, 22 June 2011

Thanks for the reply. I have found that my wiki was dumping XML file with not allowed character at the beginning, after trimming it, indexing was OK.

I have multilingual smw wiki in English and Japanese in single database and on search results in Japanese I get error in Search results:

Warning: preg_replace() [function.preg-replace]: Compilation failed: unrecognized character after (? or (?- at offset 2 in /my/path/extensions/PslZendSearchLucene/PslZendSearchLucene_body.php on line 1525

anyway the Zend Extansion finds correct page but :

  • "Text" is not displayed under the search results for Japanese
  • foreign UTF8 characters (like other languages in English text) are displayed as ?
  • words inside Japanese sentence are not indexed (as there are no spaces between words in Japanese)

$wgPslUtf8DecodeResults just turns Japanese page names to ????

ad Mediawiki MW Search:

  • same result as mentioned upper
  • foreign UTF8 characters are displayed correct in normal MW Search...
  • words inside Japanese sentence are not indexed (default MW Search probably cannot deal with this)

I don't know what of the mentioned is my misconfiguration and what real troubles, just wanted to share overall result from testing by normal Mediawiki user (not a PHP expert).

Rien Satori06:24, 24 June 2011

Hi Satori,


I will try to reply accordingly from developers point of view- for you and following visitors. As I know Semantic MediaWiki (smw) is a complete "other peace of Software", or drastically modified MediaWiki. We never tested ZSL for MediaWiki against this branch. There is another comment describing problems with Japanese language...so we might can say ZSL is currently not ready for Japan ;-). But we recognized many downloads from other countries all over the world (without any bug postings) and use it with UTF8 in german language. So we could say it's a stable ZSL release accordingly to the requirements and test scenarios mentioned at the main page.

Steviex216:28, 24 June 2011

Yes, we have tried this extension in a Japanese environment an failed to used it. You have to consider that when running Apache and Mysql on a real Japanese OS based Windows or Linux environment that this might as well influence in how XML data (especially when you save data on that system) are handled (processed). Assuming that just because it is an UTF-8 enabled extensions does not automatically stand the real test in dealing with Chinese, Korea or Japanese characters, as in in our case we are using SphinxSearch which deals with all sorts of characters.

Just to clarify on the topic Semantic MediaWiki so people that get the wrong impression, it is not a modified MediaWiki, it is an extension (similar to this extensions) that uses standard hooks and parser functions to communicate with the data available from MediaWiki, their are no modifications that influence the standard functionality of MediaWiki nor does it in any away interfere with the database structure.

MWJames18:27, 24 June 2011
 

Thanks for quick responses :-). I just really wanted to try this search extension because it is amazing implementation which can work on hosting without Java or C++ support. Even if I failed for this moment for my specific purposes (and will need to wait for perfect search engine when I get better hosting), for many users this can be good solution, so I appreciate your effort.

Rien Satori15:58, 25 June 2011