PHP warnings should not be a cause for concern, nor should your site actively display them on pages. That being said, it probably wouldn’t hurt to write safer code.
going to mark this as resolved unless you find the plugin unusable
Hi I also get this error:
`PHP Warning: Invalid argument supplied for foreach() in /home/benny/onlinegilde/html/wp-content/plugins/fantastic-elasticsearch/lib/nhp/options/options.php on line 257, referer: http://onlinegilde.net/wp-admin/admin.php?page=elastic_search&settings-updated=true
This ends up in a Error 500 and my search isn’t working. So in this case is unusable for me.
I have a vserver with elasticsearch installed locally and php 5.4 and percona 5.5 mysql database.
Maybe you have an idea how to solve this error 🙂
Elasticsearch itself is working because I had before WordPress Xenforo with elasticsearch installed and it worked just fine
Benny
PHP Warnings should not cause 500 errors unless you have it configured that way (through your own exception handler). You sure there isn’t any fatal errors in your apache logs? There is a pull request to remove the warning but I haven’t merged yet.
I have the same problem, some warnings and then it ends in a fatal error, this happened when I tried upgrading from 1.2.3 to 2.1.0 in WP extension page :
PHP Fatal error: require_once() [function.require0]: Failed opening required ‘…/wp-content/plugins/fantastic-elasticsearch/lib/nhp/options/options.php’ in …/wp-content/plugins/fantastic-elasticsearch/elasticsearch.php on line 32
Follow-up in case someone else gets this:
It might be caused by any cache you are using (APC, Memcached, etc). You can try to restart those.
If this doesn’t work, you could try restarting elasticsearch as well
If all that fail to work, you could do a clean install. Remove the fantastic-elasticsearch folder, then go to WP extension page and add it again from there.
