Anyone had issues on orders where there are no details of the shipment? I can go into the rails console and see the shipment exists, but nothing in the admin view.

Following along with https://guides.solidus.io/advanced-solidus/promotions-system/#implementing-a-new-action, I'm running into

uninitialized constant Spree::PromotionAction

. This code worked in a Rails 6 app, but this one's on Rails 7 so maybe this has to do with Zeitwerk. Seems like any initializer which tries to access anything in

Spree::

throws an error. Tried surrounding with a

to_prepare

and

spree.config

but no luck.

require "./app/models/embold/promotion/actions/free_product.rb"

Rails.application.config.spree.promotions.actions << "Embold::Promotion::Actions::FreeProduct"

and the line of

free_product.rb

that it's complaining about:

module Embold
  module Promotion
    module Actions
      class FreeProduct < ::Spree::PromotionAction

Hi guys, First time using Solidus on a Rails project. Everything is great so far in development, but it’s another thing in production. I can access everything, add my products etc...but nothing is rendered in front. I am using Heroku. If someone has been through this i ll be glad to take some advice 🙂

Hellow, I have a missing scope error ``undefined method `available' for #<ActiveRecord::Relation`` app/lib/spree/core/search/kit.rb25in `get_base_scope'

module Spree::Core::Search
  class Kit
...        
      def get_base_scope
          base_scope = Spree::Kit.display_includes.available
          base_scope = get_kits_conditions_for(base_scope, @properties[:keywords])
          base_scope = add_search_scopes(base_scope)
          base_scope = add_eagerload_scopes(base_scope)
...
  end
end

From the web console the available method (Spree:Kit:Scopes) is working, but Spree:CoreSearch:Kit doesn't seem to find it

Trying to figure out why my test shipping method isn't working and checkout returns

We are unable to calculate shipping rates for the selected items.

when I try to advance to the delivery step. I've searched and saw possible causes could be: - no shipping methods with calculators that match the order's currency - no shipping methods that match the shipping category of the items in the order - no shipping methods available for the order's zone I've checked the shipping method and it's assigned to the "Default" shipping category, it's assigned to the "North America" zone. I've tried both "flat rate" set to $0/"USD" and "flat percent" set to 0 (and doesn't have a currency). Checking the product, it's also assigned to the "Default" shipping category and the address I'm testing with is in North America. I'm at a loss as to what else could be missing. The only thing I can think that's different than any other shop I've worked on is that this one uses dynamic variants. That doesn't need anything else accounted for, does it?

Hello, I'm creating a store with solidus using the starter front-end and I want to use Stripe as a payment method. I tried using solidus_stripe gem but it didn't work and I followed this tutorial to try the implementation: https://github.com/solidusio/solidus_stripe, I followed the readme of master branch. I've tried using the stripe-ruby gem as well, but I'm confused on where to put the additional code using the gem so that the payment and order flow continues to work correctly. I also read this guide for customizing payment methods in an attempt to add the stripe, using the stripe-ruby gem: https://guides.solidus.io/advanced-solidus/payments-and-refunds#customizing-the-payment-system

Hello I am trying to setup my local env to work on the solidus_stripe extension. I’d like a confirmation from one of the devs currently working on it @ Elia or @ waiting_for_dev maybe. I managed to have the app running, I set the env variables. You confirm that in this page, I should have the Stripe checkout form displayed instead of the “loading…” no ?

Question! We have multiple warehouses but we don't want to work with multiple shipments right now (we transport the goods to one warehouse first). I tried setting stock_splitters config but it does not seem to disable it. In the checkout its still visible

Question re: the upgrade guide for Solidus 3.4. In the steps listed here (https://guides.solidus.io/upgrading-solidus/v3.4#prlink-descriptionnew-taxon-and-taxonomy-validations-number4851-), it says to enable the new

extra_taxon_validations

preference, run

Spree::Taxon.all.select(&:valid?)

, and ensure you have empty arrays. But... shouldn't you not have an empty array here if all of your taxons are valid? 🙂

Does anyone have experience with Lloydsbank's Cardnet or Windcave as payment gateway?

I'm trying to show the delivery time for each shipping method. I found this guide https://guides.solidus.io/advanced-solidus/stock-and-fulfillment/#shipping-rate-selector, but I not understood the comment that say "This assumes

Spree::ShippingRate

responds to `#delivery_time`", delivery_time its a method that I have to implement? Or have another way to show the delivery time in Delivery step?

hello everyone, i have a problem after updating the taxons' icons with an svg image format it uploads but fails to load the image, is the problem with active storage or solidus image mime type?

hello! I have a question regarding solidus internals and best way to achieve what i have on my mind. Let's say i have a shop in which you can buy a dog leash. Leash have different variants based on size and thickness but - user has an additional set of checkboxes when he wants to add a leash to his cart - he can select if he wants to make leash 2m longer for 5$ or if he wants an extra safe fastener for +4$. These adjustments applies to every possible variant combination so i can't really use variants for that as i would end up with 50 variant combinations per each product. I managed to implement a backend/admin logic for that (defining these adjustments, their prices etc) but i have no idea which internal tool of solidus should i use to actually adjust the line item price. Should i implement custom line item adjustment class? Or shuld i overwrite a calculator? What do you think? 🙂 Thanks in advance for any clues !

Hello, after having integrated the new solidus_stripe v5.0.0.alpha, I had a bit of dificulty to follow the workflow and communication between Stripe, frontend solidus and backend solidus. It has changed during development to support the “confirm” step, and you now follow the 2 steps payments. Do you think it would be woth adding a schema to doc/readme to understand what’s included in the gem by default ? Should I open a ticket ?

Hi there, I'm a little stuck looking for some information, i need to add a button payment for epayco.co, that means that the user is redirected to epayco payments checkout web page. How can I add this button to solidus store?

Hi everyone, when i am testing in production and clicking on "Add to Cart", i have this error : The change you wanted was rejected. Maybe you tried to change something you didn't have access to" ActiveRecord::RecordInvalid (Validation failed: Store can't be blank): app/controllers/cart_line_items_controller.rb12in `create' But everything is ok on Localhost, any idea ?

👋 Hi there! I’m looking into Solidus as an option for setting up a headless ecommerce website. I’m reading through the Stripe integration docs, and this line stood out to me:

When using the Payment Intents API, be aware that the charge flow will be a bit different than when using the old V2 API or Elements. It's advisable that all Payment Intents charges are captured only by using the Solidus backend, as it is the final source of truth in regards of Solidus orders payments.

Am I correct to understand that it’s not recommended to automatically capture payments in Solidus, and that payments should be captured manually? That seemed strange so I figured I’d ask.

I am struggling to understand some of the admin permission model in Solidus, and could use a hand. For some reason, users who hold the default OrderDisplay permission set cannot seem to view the

Cartons

tab of an order - they get an authorization failure. But it is really opaque to me why that is failing, and what permission they would need to be granted in order to actually see that tab. Any pointers here on why that is the case, or how to fix it, would be greatly appreciated!

Users with the OrderMangement permission set seem to be able to view this page just fine - and I can't understand what is causing the authorization failure.

Ah ha - I didn't even realize, but I think the Cartons page itself is a custom view we added. Which means I've probably got the permissions wrong on my side of things! Whoops!

Lol 🙂 btw, didn't realize Blue Apron ran Solidus - cool @Tom Wilson!

Hello! Adding a line item along with an associated subscription line item to cart via API seems to be failing after upgrading solidus to 3.4, solidus_subscriptions to 2.0 and solidus_stripe to 5.0. Our API request is as follows:

POST /orders/${_orderNumber_}/line_items

Request body:

{
  "line_item": {
    "quantity": 1,
    "variant_id": 60
  },
  "subscription_line_item": {
    "quantity": 1,
    "interval_length": "4",
    "interval_units": "week",
    "subscribable_id": 60
  }
}

Response:

{
  "status": 500,
  "error": "Internal Server Error"
}

Stack Trace (from GCP logs):

Completed 500 Internal Server Error in 122ms (ActiveRecord: 66.0ms | Allocations: 19965)
FATAL -- : [45b5cd62-596f-47a7-9791-658e62037f87]
ArgumentError (wrong number of arguments (given 2, expected 1)):
DEFAULT 2023-05-03T21:24:22.395905Z [45b5cd62-596f-47a7-9791-658e62037f87]
solidus_subscriptions (5b4c7052ace3) app/models/solidus_subscriptions/promotion/rules/subscription_creation_order.rb:27:in `eligible?'
solidus_core (3.4.1) app/models/spree/promotion.rb:166:in `block in eligible_rules'
solidus_core (3.4.1) app/models/spree/promotion.rb:173:in `all?'
solidus_core (3.4.1) app/models/spree/promotion.rb:173:in `eligible_rules'
solidus_core (3.4.1) app/models/spree/promotion.rb:156:in `eligible?'
solidus_core (3.4.1) app/models/spree/promotion.rb:222:in `line_item_actionable?'
solidus_core (3.4.1) app/models/spree/promotion/actions/create_item_adjustments.rb:92:in `block in line_items_to_adjust'
activerecord (7.0.4.3) lib/active_record/relation/delegation.rb:88:in `each'
activerecord (7.0.4.3) lib/active_record/relation/delegation.rb:88:in `each'
activerecord (7.0.4.3) lib/active_record/relation/query_methods.rb:310:in `select'
activerecord (7.0.4.3) lib/active_record/relation/query_methods.rb:310:in `select'
solidus_core (3.4.1) app/models/spree/promotion/actions/create_item_adjustments.rb:90:in `line_items_to_adjust'
solidus_core (3.4.1) app/models/spree/promotion/actions/create_item_adjustments.rb:27:in `perform'
solidus_core (3.4.1) app/models/spree/promotion.rb:128:in `block in activate'
activerecord (7.0.4.3) lib/active_record/relation/delegation.rb:88:in `each'
activerecord (7.0.4.3) lib/active_record/relation/delegation.rb:88:in `each'
solidus_core (3.4.1) app/models/spree/promotion.rb:127:in `map'
solidus_core (3.4.1) app/models/spree/promotion.rb:127:in `activate'
solidus_core (3.4.1) app/models/spree/promotion_handler/cart.rb:28:in `block in activate'
solidus_core (3.4.1) app/models/spree/promotion_handler/cart.rb:26:in `each'
solidus_core (3.4.1) app/models/spree/promotion_handler/cart.rb:26:in `activate'
solidus_core (3.4.1) app/models/spree/order_contents.rb:77:in `after_add_or_remove'
solidus_core (3.4.1) app/models/spree/order_contents.rb:24:in `add'
solidus_api (3.4.1) app/controllers/spree/api/line_items_controller.rb:14:in `create'
actionpack (7.0.4.3) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
actionpack (7.0.4.3) lib/abstract_controller/base.rb:215:in `process_action'
actionpack (7.0.4.3) lib/action_controller/metal/rendering.rb:53:in `process_action'
actionpack (7.0.4.3) lib/abstract_controller/callbacks.rb:234:in `block in process_action'
activesupport (7.0.4.3) lib/active_support/callbacks.rb:118:in `block in run_callbacks'
solidus_api (3.4.1) app/controllers/spree/api/base_controller.rb:162:in `block in lock_order'
solidus_core (3.4.1) app/models/spree/order_mutex.rb:29:in `with_lock!'
solidus_api (3.4.1) app/controllers/spree/api/base_controller.rb:162:in `lock_order'

Any insight would be greatly appreciated!

Hi everybody. I'm trying to remove the delivery step in order to sell digital products but anything that i have tried works. I have tried https://guides.solidus.io/cookbook/redefining-checkout-steps#removing-checkout-steps . Any help would be appreciated

Wanting to get a little sanity check -- in our app we check customer location via IP and then set a session object which represents the currency we'd like to use for the customer. Is there a way we could set that through some mechanism which already exists inside of solidus? I'm looking at the pricing selector classes -- will that work to set the currency for that user globally?

In the spirit of avoid writing big features and then discovering they already exist in solidus — is there anything for expiring incomplete orders?

Howdy folks! I'm trying to understand this note in the solidus_stripe extension: https://github.com/solidusio/solidus_stripe#upgrading-from-v4 We currently use

solidus_stripe 4.4.0

, and we use it mostly to configure payment methods - so we're using the

Spree::PaymentMethod::StripeCreditCard

from the gem. (We don't use any of the webhooks directly or the frontend integration in our particular setup). Is there any good guidance on how to update the gem from v4 to v5?

It looks like

StripeCreditCard

is removed in the latest version of the gem, so I'm trying to understand how a store is expected to upgrade this dependency.

Hey there 👋 The issue we had with writing a more comprehensive guide for upgrading was that v4 can be configured in many different ways. That said if all your StripeCreditCard payment sources hold references to Stripe PaymentMethods it should be possible to devise a migration to SolidusStripe::PaymentSource.

@Tom Wilson I’d be more than happy to give support in finding ways in which we can document such a process and improve the migration instructions, sourcing them from an real use case would be much better that trying to devise them top-down 🙌