solidusio / solidusio/solidus_auth_devise

When adding solidus_frontend and solidus_auth_devise I am getting an exception

Open
#178 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
56
Forks
124
Avg merge
4h 56m
Merged PRs (30d)
1

Description

When add these two gems together on my Gemfile:

solidus_frontend (~> 2.9.0)
solidus_auth_devise

I am getting the error below when trying to start the server
Before process_action callback :setup_for_current_state has not been defined (ArgumentError)
The only way we found to fix this is by doing this change to this file

lib/controllers/frontend/spree/checkout_controller_decorator.rb

-      base.skip_before_action :setup_for_current_state, only: [:registration, :update_registration]
+      base.skip_before_action :setup_for_current_state, only: [:registration, :update_registration], raise: false

Is this happening to someone else? Am I doing something wrong?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Gemfile combination of solidus_frontend (~> 2.9.0) and solidus_auth_devise, then inspect lib/controllers/frontend/spree/checkout_controller_decorator.rb and reproduce the server-start exception. Verify whether the reported skip_before_action change prevents the error, and confirm that the application starts successfully with both gems enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
authentication, backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.