rails g solidus_razorpay:install /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0/gems/solidus_razorpay-1.1.0/lib/solidus_razorpay/engine.rb21in 'block in <class:Engine>': uninitialized constant SolidusRazorpay::RazorpayGateway (NameError) app.config.spree.payment_methods << SolidusRazorpay::RazorpayGateway ^^^^^^^^^^^^^^^^^ from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0/gems/railties-8.0.2/lib/rails/initializable.rb32in 'BasicObject#instance_exec' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0/gems/railties-8.0.2/lib/rails/initializable.rb32in 'Rails:Initializable:Initializer#run' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0/gems/railties-8.0.2/lib/rails/initializable.rb61in 'block in Rails::Initializable#run_initializers' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/3.4.0/tsort.rb231in 'block in TSort.tsort_each' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/3.4.0/tsort.rb353in 'block (2 levels) in TSort.each_strongly_connected_component' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/3.4.0/tsort.rb434in 'TSort.each_strongly_connected_component_from' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/3.4.0/tsort.rb352in 'block in TSort.each_strongly_connected_component' from /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/3.4.0/tsort.rb350in 'Rails:Initializable:Collection#each'

I am not able to fix the following error

rails g solidus_razorpay:install /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0/gems/solidus_razorpay-1.1.0/lib/solidus_razorpay/engine.rb21in 'block in <class:Engine>': uninitialized constant SolidusRazorpay::RazorpayGateway (NameError) app.config.spree.payment_methods << SolidusRazorpay::RazorpayGateway ^^^^^^^^^^^^^^^^^

recomend me compatible payment gateway is solidus_razorpay will work for me ? solidus (4.5.1) Author: Solidus Team Homepage: http://solidus.io License: BSD-3-Clause Installed at: /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0 Full-stack e-commerce framework for Ruby on Rails.

guide me to install solidus_razorpay in to my app using solidus (4.5.1) Author: Solidus Team Homepage: http://solidus.io License: BSD-3-Clause Installed at: /home/dhana/.local/share/mise/installs/ruby/3.4.2/lib/ruby/gems/3.4.0

Morning all, whats the best way to add management reports to Solidus. Ive had a look at the solidusio-contrib/solidus_reports.git but that seems to be incompatible with the current version

I'm wondering if anyone has guidance on configuring a pretty complex store. Our client currently has 200+ products/variants. The variants generally don't follow any discernible rules. For example, they have these 4 products/variants that should be all under a single master product: • AviClear Acne (Package of 3 Sessions + Kit Post Care) - $10 • AviClear Acne Plus & Scarring Protocol - $11 • AviClear Acne Plus Protocol - $9 • AviClear Subsequent Session - $7 All 4 of these should show up under the AviClear product as different options/variants. (Note prices are made up but the important point is that the prices are all different too) Other products might have 10-15 variants like this where like this, I don't see any way to use option types to get to the list of variants that we have Any ideas?

Hi, @Doug DeBold Which e-commerce platform are they using?

Morning all, got a bit of a weird one. When I go to page 2 of promotions im getting an error:

The single-table inheritance mechanism failed to locate the subclass: 'Spree::Promotion::Actions::CreateLineItems'. This error is raised because the column 'type' is reserved for storing the class in case of inheritance. Please rename this column if you didn't intend it to be used for storing the inheritance class or overwrite Spree::PromotionAction.inheritance_column to use another column for that information. If you wish to disable single-table inheritance for Spree::PromotionAction set Spree::PromotionAction.inheritance_column to nil

This system was originally Spree so I am guessing it could be a difference between Spree & Solidus. I'm not seeing anything in the issues list for it, a similar one I found was here: https://github.com/solidusio/solidus/issues/3119 Any ideas? Im wondering if the type field is redundant now or whether I need to disable the STI

solidus 4.5.1

solidus 4.5.1 error message ImageProcessing::Error in Home#index Showing _/home/sairamsu/public_html/app/views/products/_featured_product_card.html.erb_ where line #3 raised:

either width or height must be specified

Extracted source (around line #15):

13
14
15
16
17
18
              
  def call
    if image
      image_tag image.url(size), default_options.merge(options)
    else
      content_tag :div, nil, class: ['image-placeholder', size].join(' ')
    end

how to fix it

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! 🙂