nickdunn / elasticsearch Goto Github PK

See http://symphony-cms.com/discuss/thread/85237/2/#position-23

Could be that fields need to be instantiated properly first?

Hi Nick,

I've tried to install ElasticSearch plugin for Symphony. When I add the configurations in the System Preferences form I get the following error in the log file.

07/25/2012 11:35 pm > UNKNOWN: GenericExceptionHandler 0 - ElasticSearch client: Couldnt resolve host in file /Library/WebServer/Documents/elasticsearchdemo/extensions/elasticsearch/lib/class.elasticsearch.php on line 45

I don't know the cause behind it. It might be something I'm doing wrong but I have followed all the steps in the installation tutorial.

Causing the following error;

Symphony Fatal Error: TypeMissingException[[#####] type[######] missing]

In the first line of lib/class.elasticsearch.php the php is missing from the start tag: <?

This stops my Apache installation from parsing the php and spitting it out in pure text, breaking the backend. Can send a pull request if you want.

Fatal error: Call to undefined method General::generatePassword() in /Users/brendanabbott/Sites/example.com/extensions/elasticsearch/content/content.sessions.php on line 261

Oops, due to the last minute removal for security reasons attempting to view this page now throws an error.

If I click on the Sessions Logs (under the ElasticSearch menu), I get the following error…

Fatal error: Call to undefined function _() in /Sites/elasticsearch-surfin-shakespeare/extensions/elasticsearch/content/content.sessions.php on line 242

and when I click on Query Logs (under the ElasticSearch menu), I get the following error

Fatal error: Call to undefined function _() in /Sites/elasticsearch-surfin-shakespeare/extensions/elasticsearch/content/content.queries.php on line 241

@brendo pointed out to me in the Symphony CMS forum, this can be fixed by…

The errors for Session/Query log should be easily fixed by adding another _ , so the function call is __('Text here').

Hey Nick,

I can't seem to get any highlights coming back for any of my searches. I'm using 0.3.1 but looking at the commit history I can't see any specific commits that may affect his behaviour so I thought I'd ask.

I had a poke around and found this line odd. Going by the comment, I think this should be if(!$properties->symphony_highlight) continue;.

My mapping file is setup like this one and the config file has the default settings for highlight-fragment-size and highlight-per-field.

Where else should I be looking to try and find the problem?

$ sudo ln -s readlink -f /usr/local/share/elasticsearch/bin/service/elasticsearch /usr/local/bin/rcelasticsearch
readlink: illegal option -- f
usage: readlink [-n] [file ...]

What exactly does readlink -f option do?

• Connection details (as existing System > Preferences page)
• Rebuilding the index (_open, put, _close)
• Synonyms
• Stop words list
• Analyser options, checkboxes for: ASCII folding, stopwords, stemming (choose stemmer?), html_strip

When rebuilding the index, the index.json should be read and then built upon using these options. Perhaps the JSON file needs %s placeholders where these are added.

Issue discovered by @creativedutchmen.

http://symphony-cms.com/discuss/thread/85237/1/#position-19

Probably due to instantiating ElasticSearch::init(), can't remember why I pass true/false to the constructor. If true (no argument) then an index is created without the config. Weird. To investigate.