Yeah if you put the tags in the content of the posts they will get indexed and search should find them, keep in mind the body of the posts are searched when you search in "posts" so if you are only searching for titles they wont show up.
[nodebb-plugin-solr] Solr search plugin
-
Solr Search for NodeBB
Solr (pronounced "solar") is an open source enterprise search platform from the Apache Lucene project. Its major features include full-text search, hit highlighting, faceted search, dynamic clustering, database integration, and rich document (e.g., Word, PDF) handling.
This plugin extends NodeBB to utilise an installation of Apache Solr as a search backend.
Configuration
- Install this plugin via npm:
npm install nodebb-plugin-solr
- Activate it in the Plugins page
- Restart NodeBB
- Check that the plugin has successfully connected to the search engine. If not, adjust as necessary.
- Enable indexing and re-index the existing posts in your forum.
Installation
npm install nodebb-plugin-solr
Version History
- v0.1.0 Initial version (search indexing and querying)
- v0.1.1
- Search result caching (repeated searches return cached results)
- Support for Basic HTTP Authentication
- Ability to turn on and off indexing
- Support for inline-topic searching (which relies on a feature in NodeBB Core that hasn't been built yet!)
- Adds notices into the home page of the ACP
- v0.1.4
- Added support for specification of custom fields (if added into Solr's
schema.xml
) instead of using the assumedtitle_t
anddescription_t
- Added support for specification of custom fields (if added into Solr's
Notes
- This plugin requires Solr to be installed separately (either on the same server as your NodeBB, or somewhere else that is publically accessible)
- This plugin conflicts with nodebb-plugin-dbsearch! If Solr detects that dbsearch is active, it will not return search queries (but will continue to index new posts if enabled)
- Install this plugin via npm:
-
@Bin, this plugin works with the latest commits of NodeBB, so it is not compatible with v0.4.3. If you're on the master branch, a
git pull
is sufficient to bring you up to date.Edit: This commit: https://github.com/NodeBB/NodeBB/commit/b2ece27263fffbd603f219a7c3258a06dc329a89#diff-ed75d775004d7f6bf533c07c815c33ab
So if you've pulled within the past 7 days, you're good
-
Have updated Chinese translation. http://nodebb.org.cn/topic/5/nodebb-plugin-solr-solr-search-插件
-
I was thinking about it for long time Solr, Elastic search. Is this forum now using solr ?
-
@julian I want to use this plugin and I have updated lastest NodeBB and Solr, but when I run ./nodebb dev, I got these warns:
warn: [plugins/nodebb-plugin-solr] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
warn: [plugins/nodebb-plugin-solr] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-solr".And when I use this I got some other errors. So what shoud I do to make this work?
-
So we have to install Solr first, correct?
https://www.digitalocean.com/community/tutorials/how-to-install-solr-on-ubuntu-14-04
...then install the plugin?
Can't wait for the inline-topic searching!
-_-
Installation Problem:
When I try accessing the Solr page via ACP, it gives me a 404 error. Any thoughts? -
This post is deleted!
-
@main It is updated to latest.
-
This is the error I'm getting:
warn: Plugin: /home/c/node_modules/nodebb-plugin-solr is corrupted or invalid. Please check plugin.json for errors.
I disabled all plugins @_@
I noticed theres a version difference in NPM and on Github.
-
@a_5mith I can't build index and when I search got this error:
TypeError: Cannot read property 'response' of null at /var/local/swift/node_modules/nodebb-plugin-solr/library.js:173:11 at ClientRequest.<anonymous> (/var/local/swift/node_modules/nodebb-plugin-solr/node_modules/solr-client/lib/solr.js:576:21) at ClientRequest.EventEmitter.emit (events.js:95:17) at Socket.socketErrorListener (http.js:1547:9) at Socket.EventEmitter.emit (events.js:95:17) at net.js:441:14 at process._tickCallback (node.js:415:13)