Closed scottrice10 closed 11 years ago
first, thanks sooo much for putting this together! I don't have a chance to review the code but definitely look forward to bringing it in. Not sure if you would be up for it, but I have a 2.0.0-wip branch that I have put together that has a great amount of testing and changes, and if you would like to work on getting this included it would save me some time.
also looks like a lot of the diffs are showing permissions changes, and seems they were changed to 0777, could you revert them back?
Sure thing - I'll merge the changes with the latest 2.0.0-wip branch and create a new pull request. As long as there are no major glitches, should be able to get it done within the next few days.
And sorry about the permissions - they'll be returned to their normal values in my coming pull request.
I changed the permissions and synced my pull request with the 1.2.4 release, so it should be ready for prime time. Did not get a chance to look too closely at the 2.0.0-wip branch, but will do so in the nest couple days.
Finding some good javascipt facet apps for Elasticsearch. qboxio is a start-up offering hosting for Elasticsearch, and their Github library has a pretty cool app using Google maps, and another that sorts a directory listing. Automattic has put out a library called es-backbone, which includes a pie chart facet. Might work well with Fantastic Elasticsearch.
Thought I could manually update last night, but realized some of the 1.2.4 files were left out. Merging the remote-tracking branch did the trick.
closing as it is for old code
Added a sidebar widget that displays taxonomy facet filters as checkboxes, dropdowns, multi-selects, radios, or sliders, with options to display count dynamically (from Elasticsearch), as unchanging total (from MySQL), or not at all. Also option to submit with ajax. Options for the facet widget are included both in the Fantastic Elasticsearch admin section , as well as on the widget's admin.
Also added to the NHP Options framework so that Elasticsearch can be added to any archive or page. This way, Elasticsearch can power loops and the facet widget on any part of the site (except posts, which could be easily added). Recently, the Lucene-Solr community has mentioned that Lucene-based search engines could function as NoSQL databases. For larger Wordpress installations, enabling Elasticsearch on all parts of the site, and thereby bypassing MySQL, may boost performance?