Hey, am I wrong or should the login of a guest user automatically trigger a cart recalculation?

Hi all! I´m maintaining a couple of stores (Spree 4.2). Already late I tried to upgrade the first one and this blows my mind. I have always been interested in the Solidus project, and always thought a change would be too complicated. But now I think it´s time to do it! This can´t be more complicated than upgrading Spree. E.g. here: https://github.com/spree/spree/issues/12231

...sorry for the premature sending. To be continued...

I see a couple of people @m b @Fabian V. Thobe who also use Spree and may want to migrate. Maybe someone have done this in the past? Did you have a good strategy to do the job?

Hi, I'm having a strange problem in alchemy_cms + solidus. The client updated the product price a couple of months back. Many orders have bought the product at new price. But all of a sudden there is a customer that buys the product with the old price. This has been reported twice now. What could be the issue here? Are old prices stored somewhere in the application or is it something to do with client specific caching who maybe loaded the product before the price change? Thanks for any pointers

We are currently working out user groups to segment users out and we figured out that the process to create a user from frontend is not the same as from backend. Is there any particular reason for that or could they be merged knowing that for frontend requests conditionally a session would need to be created?

I’m working on a website that uses Solidus core as the data store/state machines for the order process. I want to use Stripe Checkout for payments, which is a redirect-based payment method: at the end of the checkout process the user is redirected to Stripe’s website, where they enter their details, and Stripe calls a webhook to notify me of success/failure. I know people have integrated Stripe Checkout with their Solidus stores, but I’d love some more details about the best way to do this under the hood. In particular: • Does a redirect-based method fit into the method outlined in the “Customising the payment system” docs? Should I create my own Payment Gateway for this? I think maybe the

authorize

step maps to Stripe’s “create a Checkout Session”, and the Stripe success webhook maps to “capture”. • Alternatively, I could avoid this customisation. Instead: my

CheckoutController

would check whether my

Spree::Order

is in the

payment

state, and redirect to the Stripe Checkout if so. Separately, my webhook handler marks the order as

complete

on success. But I guess then I’d miss out on “transaction history” – how many times a user attempted to pay, and when. I’d love any advice from people more familiar with Solidus’ payment code about which approach seems better.

If I need to filter my products by multiple options, is

has_option

(qv) supposed to be chainable? eg:

Spree::Product.find_by(slug: "metal-framed-poster").variants
    .has_option("frame_colour", "copper")
    .has_option("paper_type", "matte")

I’m finding this generates an inner join that will never work; it requires

spree_option_types.name = 'frame_colour' AND spree_option_types.name = 'paper_type'

.

Hello, I'm using

gem 'solidus', github: 'solidusio/solidus'

and i want to replace my views completely on frontend side and some tweaks on admin side. What is the best option to update these views?

Hi there, our client has a request to implement a credit card processing fee. What would be the general path for this? From the docs it sounds like an adjustment is the right way but I'm not sure how to fit it into an "adjustment source". Any guidance?

This message was deleted.

I’m a little unclear on if this is a Solidus bug, or elsewhere. I figured I’d describe it here, and I can write it up on Github if this is something fixable within the Solidus project. Basically: when using Solidus core in your Rails app, Rails’ mailer previews break. My app’s custom mailers appear fine after first boot, but on any change they disappear. Restarting the Rails server brings them back. The cause of this is basically the same as this Devise-centric Reddit post. Rail’s

ActionMailer::Preview

will load your previews if the class’ descendants are empty, but Solidus’ previews are still present:

[Spree::MailerPreviews::ReimbursementPreview, Spree::MailerPreviews::OrderPreview, Spree::MailerPreviews::CartonPreview]

. I’ve worked around this by monkeypatching ActionMailer::Preview.all to always call

load_preview

, but it was tricky to track down the root cause! It’d be nice if this wasn’t necessary.

Hello, I have a question related to solidus_paypal_commerce_platform gem, specifically about this part of README file I am unclear about:

By using this extension, you are giving back to Solidus. PayPal will pay a fee to the maintainers (Nebulab) for each order made through the payment gateway.

Is this referral fee covered fully by PayPal or is it deducted from merchants revenue?

Hello, i have a question related to acts_as_nested_set, got an error. Any guidance to fix this error or anyone encounter it I have ruby 3.1.4 and solidus 2.11.4

I’m working on a Solidus app which is using Solidus core as its “backend” for all the order processing and data models, but is implementing a custom storefront/frontend. Is there a recommended way of how I should display prices? I see in the starter frontend that we end up calling `money` on the prices, which provides a `to_html` method, but I don’t think that

#money

is automatically available to me? (At least, when I call

#money

on my

Spree::ProductVariant#price

I get “undefined method ‘money’ for instance of BigDecimal.“)

Why i am always getting this error even i already setup a shipping and tax for the product Solidus 3.0.0 Ruby 3.1.4

Order R557038528 halted transition on event next state address: We are unable to calculate shipping rates for the selected items.
Failed to transition to next state. Errors: We are unable to calculate shipping rates for the selected items.

I'm integrating solidus subscriptions with solidus stripe and have a question about what is setup and when. In the scenario where an order has a single subscribable line item and we have auto capture turned on, when the user goes through the checkout flow the first time, that order will not be directly related to a subscription. Is this correct? It is only future orders that will have the subscription attached as they are created in the background?

This message was deleted.

Hi everyone, what is the most compatible payment platform right now? Is it paypal or stripe? Seems like some events were missing when I set up a stripe sandbox and tried to do mock payments. You write in the docs that paypal has a wizard, how to I use the wizard? Install a package and then run a cli-command? Thank you for developing Solidus, it' awesome! 🙂

Hi everyone, I’m trying to figure out the best way to allow admins to edit and save additional custom attributes on line items within the Solidus admin order interface. These are not core fields like quantity or variant ID, but extra fields specific to our use case. I’ve tried rendering them as inputs inside the line item edit view and also experimented with injecting values into the line item model via JavaScript, but none of these approaches seem to persist the data. It seems the Ember admin only tracks a limited set of fields and ignores anything outside of that scope. Is there an established way to handle this in Solidus, or is the only practical solution to build a custom admin interface outside of the Ember cart UI? I’d really appreciate any advice or examples from others who have needed to store custom data per line item.

I want to set up my product catalogue in one environment, and later on “promote” it to production (ie. move it from one DB to another). Is there a recommended process (or common gem) for this?

Hi everyone, I’m encountering what seems to be a core Solidus issue related to payment creation and order confirmation in the admin interface. When I attempt to confirm an order from the admin (via a custom controller action that creates a payment using @order.payments.create!) or even update a payment using the default admin payment form, I consistently receive a SystemStackError: stack level too deep. This occurs even with simple test orders and regardless of whether Stripe or any third-party gateway is involved. I’ve traced the issue to cascading state updates triggered by the payment creation. The order’s state machine seems to recursively call update!, update_payment_state, or other callbacks that re-trigger the same logic, leading to an infinite loop. I tried guarding my code with instance variables (e.g. @ensure_payment_guarded) and even removed custom logic entirely, but the issue persists.

Crossposting

I’m using Solidus as the ecommerce backend for my own custom checkout process. As part of my checkout, once I have a customer’s delivery address I make an API call to a third party print-on-demand (POD) supplier. This gets me the shipping rates for the order. I store that POD quote, and ensure that I have a

Spree::ShippingMethod

for the shipping providers in the quote, and add it to the customer’s

Spree::Zone

if necessary. I also have a custom

ShippingCalculator

that uses the POD quote to check for availability and cost. I’m seeing some odd behaviour when I’m off the “happy path”, though, such as when the line items change in an order, or a customer revives an older order. My “choose delivery” page displays all the

current_order.shipments.last.shipping_rates

, but these aren’t lining up with the data in my POD quote. I think this is because they’re remnants from a previous quote. I can call

#refresh_rates

on my shipment whenever I’m on the delivery page, and that gets me part of the way there. (It adds missing `ShippingMethod`s, but doesn’t remove obsolete ones. And I don’t think it adjusts the cost either). But I suspect there’s a more idiomatic/more comprehensive way of achieving this. Does anyone have any pointers?

Hey! Is there any up to date solidus extension providing a feature like this one? https://github.com/QuintinAdam/spree_flexi_variants

I think i could install this ext long time ago on solidus.. Did u try it?

nope 😉 no updates in 8 years

Yup that was exactly 8 years ago

Wat i wud do is reverse engineering.. I believe u csn clone it fit solidus model structure

that's my plan basically but i was hoping there is already such extension available