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

We have a client who is asking for "membership" pricing. E.g. A product is $450 normally but if you have already purchased a membership, lets say, $20/mo, then your price is $400 for the same product. This feels like a somewhat normal feature but I haven't figured out how to implement.

This message was deleted.

I’m implementing a custom payment system, and am trying to write a test for my webhook controller. I receive a webhook that notifies me of a successful payment, which should mark my Solidus

Order

as complete. In my test I’m constructing an order_ready_to_complete, and I’ve checked that my mock webhook payment is for more than the order total. And yet! Calling

order.complete

in my controller isn’t marking the order as `complete`;

order.can_complete?

returns

false

. How can I find out what’s preventing completion of this order?

Hi, is there any information about shop statistics in solidus. Is there something integrated that admins can view? Thank you for any information

I am a long ways down the path of re-implementing the checkout flow in react native + stripe. I have the majority of it all figured out but one thing that I'm struggling with is the difference between the update order api (

spree.api_order_path

), and the update checkout path (

spree.api_checkout_path

). It seems that the checkout API has some limitations like if the order is on the payment step, you can't change the address and I haven't found a nice way to move the order backwards through the state machine. What is the recommended use of these APIs in a checkout flow?

I noticed that solidus active_storage png variants are left with sRGB colors and large file sizes. Setting colors 256 in imagemagick cuts the file size to 1/4. Anyone optimized this? Also i'm not sure how to regenerate my previously created variants after changing variant logic.. Any tips appreciated

Hi is anyone using solidus_graphql_api? I am having this issue:

(store):19:in '<main>': Attach interfaces using `implements(GraphQL::Types::Relay::Node)`, not `include(GraphQL::Types::Relay::Node)` (RuntimeError)

This is my current setup:

* solidus (4.6.0)
  * solidus_admin (0.4.0)
  * solidus_api (4.6.0)
  * solidus_auth_devise (2.5.9)
  * solidus_backend (4.6.0)
  * solidus_core (4.6.0)
  * solidus_graphql_api (0.3.1)
  * solidus_legacy_promotions (4.6.0)
  * solidus_sample (4.6.0)
  * solidus_support (0.14.1)

  * RUBY_VERSION=3.4.5
  * RAILS_VERSION=8.0.3

Is anyone using the solidus_affirm_v2 gem? I'm getting an error that the transaction id can't be found at one point during checkout. The issue seems to be that we're trying to get a transaction but passing in a checkout token. This seems like it would just mean the gem doesn't work at all though so I wonder if I'm mistaken and someone could provide context?

@Melissa C. S. joined #support. They’re also new to Solidus.

is anyone familiar with this issue while setting up a fresh install of Solidus (Rails 8.0.3)? I followed the setup guide in README, just

$rails new my_project
$bundle add solidus
$bin/rails g solidus:install

~/.local/share/gem/ruby/gems/bundler-4.0.7/lib/bundler/runtime.rb:71:in 'block (2 levels) in Bundler::Runtime#require': There was an error while trying to load the gem 'solidus'. (Bundler::GemRequireError)
Gem Load Error is: Could not open library '/home/idk/.local/share/gem/ruby/gems/sassc-2.4.0/ext/libsass.so': /home/idk/.local/share/gem/ruby/gems/sassc-2.4.0/ext/libsass.so: cannot open shared object file: No such file or directory.

I have tried changing Rails versions and installing

libsass

and its dev package to my machine and refreshing the

sassc

gem. The error happens on

bin/rails g solidus:install

.

I'm a bit unclear on what I need data-wise for a fresh production app. Do I run the seeds? As that also creates the default admin user i'm not sure.

Hi, is

canonical-rails

still a dependency of Solidus? I’m trying to upgrade my application from Rails 7.1.3 to Rails 8.1 (and Solidus v4.7), but Bundler cannot resolve dependencies because

canonical-rails

0.2.17 depends on

actionview < 8.1

. Is there a recommended upgrade path for Solidus applications targeting Rails 8.1, or is support for a newer version of

canonical-rails

planned?

Sorry for asking agian, but maybe this will help you as well... I'm trying to create new store basen on solidus, step by step via your guide and I'm getting an error (see below). The internet tells me that Solidus still requires sprockets, which are no longer available in Rails 8 (by default), but I don't know if that's a correct conclusion. I can see the hint as well, but should the hint appear if Solidus 4.7 supports Rails 8.1? Since Solidus supports 8.1, should I really create a manifest file? Would any of you like to take a look at this?

bundle add solidus
IT WAS OK

rails generate solidus:install --help
/Users/adrian/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/sprockets-rails-3.5.2/lib/sprockets/railtie.rb:106:in 'block in <class:Railtie>': Expected to find a manifest file in `app/assets/config/manifest.js` (Sprockets::Railtie::ManifestNeededError)
But did not, please create this file and use it to link any assets that need
to be rendered by your app:

Example:
  //= link_tree ../images
  //= link_directory ../javascripts .js
  //= link_directory ../stylesheets .css
and restart your server

For more information see: <https://github.com/rails/sprockets/blob/070fc01947c111d35bb4c836e9bb71962a8e0595/UPGRADING.md#manifestjs>
	from /Users/adrian/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/railties-8.1.3/lib/rails/initializable.rb:24:in 'BasicObject#instance_exec'
	from /Users/adrian/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/railties-8.1.3/lib/rails/initializable.rb:24:in 'Rails::Initializable::Initializer#run'
	from /Users/adrian/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/railties-8.1.3/lib/rails/initializable.rb:103:in 'block in Rails::Initializable#run_initializers'

After fresh installation with frontend-starter all tests should pass and there is a problem with my project (I did something wrong) or is this expected? After adding

config.assets.css_compressor = nil

in

test.rb

file...

321 examples, 81 failures, 1 pending

Surprise after surprise. Is it possible that

solidus_importer

still requires Ruby 2.5? I can see relatively fresh code updates in this gem from 9 months ago, so I was expecting it to be compatible with newer Ruby versions. Running:

bundle install
Fetching gem metadata from <https://rubygems.org/>........
Resolving dependencies...
Could not find compatible versions

Because every version of solidus_importer depends on Ruby ~> 2.5
  and Gemfile depends on solidus_importer >= 0,
  Ruby ~> 2.5 is required.
So, because current Ruby version is = 4.0.1,
  version solving has failed.

Is this expected, or am I missing something? I appreciate the work that goes into maintaining open-source projects — I'm just trying to understand the current compatibility requirements and whether I'm missing something. EDIT!! Ok, using

gem 'solidus_importer', github: 'solidusio-contrib/solidus_importer'

did the job, thanks (but I'm not sure why)

It has been a while since anyone has a cut a release of Solidus Importer. It is actively in use by many stores though. Everyone is just pointing at the git remote.

I was wondering, how can I use Bootstrap instead of Tailwind for Solidus ?