Algolia:initialize not working (rails aborted - don't know how to build task)

M.Anderson · January 30, 2023, 9:54am

Hi,

first of all, this is a copy of my post into official algolia-discourse. As told by Discourse-Support, I can now post it here, therefore this is a copy-message.

I would like to setup our discourse with algolia, but it is not working like described on GitHub. I have newest version: 3.1.0.beta1.

To make first init, I open my discourse-docker with

./launcher enter app

After that, I tried different commands (bundle exec rails or only rails, also rake), but all results into:

root@rbx-communtity-service-app:/var/www/discourse# LOAD_PLUGINS=1 rails algolia:initialize
rails aborted!
Don’t know how to build task ‘algolia:initialize’ (See the list of available tasks with rails --tasks)
Did you mean? algolia:reindex

When I run just algolia:reindex, i get the following:

root@rbx-communtity-service-app:/var/www/discourse# LOAD_PLUGINS=1 rake algolia:reindex
Clearing users from Algolia
Pushing users to Algolia
..
Successfully pushed xxx users to Algolia
Clearing tags from Algolia
Pushing tags to Algolia
..
Successfully pushed xxx tags to Algolia
Clearing posts from Algolia
Pushing posts to Algolia
rake aborted!
NoMethodError: undefined method `id' for nil:NilClass
/var/www/discourse/plugins/discourse-algolia/lib/discourse_algolia/post_indexer.rb:66:in `to_object'
/var/www/discourse/plugins/discourse-algolia/lib/discourse_algolia/indexer.rb:23:in `block in process!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:71:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:71:in `block in find_each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:138:in `block in find_in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:245:in `block in in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:229:in `loop'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:229:in `in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:137:in `find_in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:70:in `find_each'
/var/www/discourse/plugins/discourse-algolia/lib/discourse_algolia/indexer.rb:21:in `process!'
/var/www/discourse/plugins/discourse-algolia/lib/tasks/discourse_algolia.rake:36:in `block in algolia_reindex'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:245:in `block in in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:229:in `loop'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/relation/batches.rb:229:in `in_batches'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-7.0.3.1/lib/active_record/querying.rb:22:in `in_batches'
/var/www/discourse/plugins/discourse-algolia/lib/tasks/discourse_algolia.rake:33:in `algolia_reindex'
/var/www/discourse/plugins/discourse-algolia/lib/tasks/discourse_algolia.rake:7:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:58:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:58:in `kernel_load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:23:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:491:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:34:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/cli.rb:28:in `start'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/exe/bundle:45:in `block in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bundler-2.4.1/exe/bundle:33:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => algolia:reindex
(See full trace by running task with --trace)

Any idea whats the issue here?

Thanks in advance!
M.Anderson

JammyDodger · January 30, 2023, 1:04pm

I have installed this on my test site to give it a run-through and I also see a similar thing. Let me see what I can find out.

zogstrip · January 30, 2023, 1:37pm

Have you set the algolia_discourse_username site setting by any chances?

M.Anderson · January 30, 2023, 1:42pm

It is set to “system”

RGJ · February 14, 2023, 6:45pm

algolia:initialize does not exist any more. See FEATURE: Update to latest algolia gem (#33) · discourse/discourse-algolia@9a1f08f · GitHub

The README.md needs an update.

zogstrip · February 15, 2023, 1:55pm

README updated

M.Anderson · February 24, 2023, 12:50pm

The issue regarding reindex is still existent. I made a complete upgrade of discourse, including algolia. Also, I could not yet found a code-change inside algolia-plugin. Are there any plans on working on this?

Right now, only readme is changed, but function is still not working like initially written by me.

If needed, I can send you fresh logs from console.

Thanks,
M.Anderson

JammyDodger · February 24, 2023, 1:10pm

There was a bug fix earlier today for an issue with reindexing and topic counts:

On the off-chance, could this have solved your issue too?

M.Anderson · February 24, 2023, 2:01pm

Unfortunately no This fix is already inside my discourse-version. Same issue as before.

Pushing posts to Algolia
rake aborted!
NoMethodError: undefined method `id’ for nil:NilClass
    id: post.topic.id,
                  ^^^
/var/www/discourse/plugins/discourse-algolia/lib/discourse_algolia/post_indexer.rb:66:in to_object' /var/www/discourse/plugins/discourse-algolia/lib/discourse_algolia/indexer.rb:23:in block in process!’
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:71:in each' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:71:in block in find_each’
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:138:in block in find_in_batches' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:245:in block in in_batches’
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:229:in loop' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:229:in in_batches’
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:137:in find_in_batches' /var/www/discourse/vendor/bundle/ruby/3.1.0/gems/activerecord-7.0.4.1/lib/active_record/relation/batches.rb:70:in find_each’

JammyDodger · February 25, 2023, 8:05am

I was over optimistically hoping for some ‘magically fixed’

I’ve given it another go on my test site and I also hit the same issue again. However, I have managed to find out some more information. Apparently we’re both experiencing an issue where we have at least one orphaned post that lacks a topic id, which is throwing off the rake task. The advice is to track those down and delete them, and then the rake reindex can run smoothly.

I haven’t put this into practice for finding the problem post(s) yet so haven’t got a step-by-step, but thought I’d give you a heads up in case this is something you’d like to explore before I get to it.

kris.kotlarek · February 28, 2023, 11:06pm

I am debugging it right now.

Did you change default algolia_discourse_username site setting? If yes, please ensure that you are using non-admin user.

JammyDodger · March 1, 2023, 9:58am

I have given this yet another go… And I can confirm that removing ‘system’ from the algolia discourse username setting and running rake algolia:reindex with a dummy user instead worked without error.

I shamefully did not spot the bit in the instructions about:

It is recommended that you create a dummy separate user who can only see content you consider to be public, and change this value to their username.

And only matched my settings per this instruction:

Once all of the settings are turned on and populated, the plugin configuration should look like this:

image2342×1016 234 KB

Personally, (and I may be biased ) I think we could maybe make those instructions a little clearer. I would advocate for a section ‘Create your algolia discourse user’ as part of the configuration flow.

kris.kotlarek · March 2, 2023, 12:08am

Actually, in latest PR I removed that option as it is possibly dangerous. When a user with admin access is used, it can show restricted posts in search.

github.com/discourse/discourse-algolia

FIX: index only public topics

discourse:main ← discourse:remove-username

opened 10:55PM - 01 Mar 23 UTC

lis2

+38 -35

`algolia discourse username` setting was potentially dangerous. When admin is us…ed, topic from restricted categories and private messages can be exposed. Therefore, the setting should be removed and only topics visible to anonymous user should be indexed. In addition, when site requires login, Algolia search should not be visible for anonymous users.

JammyDodger · March 2, 2023, 3:40am

That’s an even better idea.

M.Anderson · March 7, 2023, 8:04am

Hi,
thanks, now it is working My three indices are created and sent to algolia!

system · April 6, 2023, 8:05am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Unable to locate Gemfile when installing Algolia plugin Installation algolia-search	5	459	January 17, 2024
Urgent, can't create new Topics Bug	8	1094	April 3, 2017
Discourse Algolia Search Plugin official , algolia-search	7	22758	September 9, 2024
Algolia plugin broken: undefined method `topic_count' Bug algolia-search	2	595	February 24, 2023
Follow up: Assign Plugin Conflict Support	21	1695	October 1, 2019

Algolia:initialize not working (rails aborted - don't know how to build task)

Related topics