so visiting them by their public urls works fine?

one issue I've seen is with people caching the signed URLs (which expire)

I'm not actually super familiar with active storage myself, so we may just have run out of my capacity to help you. I'm not sure why activestorage would produce signed URLs for public objects (but maybe that's just how it works, I don't know.) I like to use Shrine which by default only creates signed URLs for private objects.

thanks Jared, that is what I can see in my console when I upload a file. if you follow the link it seems a key error, but I can see the file uploaded in my AWS bucket.

I guess if Shrine needs to be used, the solidus_core needs to have a model concern with this module, that the actual version does not have

you should be able to do this with activestorage. Shrine isn't officially supported by Solidus.

I just like it. 😅

Trying to import the database to hatchbox and keep getting errors like "ERROR: relation "public.active_storage_blobs" does not exist"

[Solidus Events vs Solidus Tracking]

hello, asking here because I guess #C014QFKHR1C has too few members 😄 does any of you have any experience with solidus_product_feed blocking the machine it’s working on?

I saw there’s also solidus_feeds, maybe that one works better? anybody has experience on either?

Setting up a store that uses authorize.net as the payment method and it looks like the solidus_gateway extension ported from spree supported this, but is deprecated. Per the recommendation there, I was attempting to build a gem by referencing some of the existing ones (solidus_affirm and solidus_braintree_paypal) but I am having a lot of trouble understanding the interactions between Solidus, ActiveMerchant, and the Authorize.net ruby SDK. For context, I am very new to Ruby and Rails, so still trying to grasp how all this works. Are there any recommendations or existing solutions already built for authorize.net that I may have missed? Would it be a terrible idea to try adding solidus_gateway to this store and trying to get that working with authorize.net?

Is there an easy way to skip the Delivery and Payment steps during checkout? Trying to turn the checkout into more of a "request for quote" so these steps aren't needed.

Hey, folks - I'm seeing something rather odd that I don't know how to explain. I'm trying to create a new Order using the Order::Importer and assign line items to the order. Whenever I do so, though, I end up getting an ActiveRecord exception:

ActiveRecord::ActiveRecordError: cannot update a new record

It seems to originate from the call in the importer to

order.updater.update

, and specifically from the

update_totals

call within the updater. I'm attempting to trace this further to understand more deeply - but is this... not a supported use case somehow?

It appears to be happening in

update_item_totals

- it looks like there's a new shipment created during the process of adding the line item, and that shipment is new, which triggers this line: https://github.com/solidusio/solidus/blob/master/core/app/models/spree/order_updater.rb#L251

Yeah - it seems like if this line is hit, I don't see how anything can avoid this error if the order actually generates new shipments. https://github.com/solidusio/solidus/blob/master/core/lib/spree/core/importer/order.rb#L34

If anyone is curious, I fixed this locally in my store - but the fix feels kind of like a hack. I added a decorator for Spree::Order and patched the

create_proposed_shipments

method like so:

def create_proposed_shipments
      super.tap { save! }
    end

Quick search makes it look like it's not possible, but just to double check: promotions are one per order, right? To enable multiple per order would require mucking about in the code, yeah? :P

I'm making an assumption based on some code I read a while ago - but I think multiple promotions work, but only one code can be applied. As in - if you have multiple persistent promotions that are applied automatically, I think multiple of those work.

(And I would be very curious to hear if I'm wrong about that! 🙂 )

Yeah, based on my testing from just a few minutes ago it looks like I can have multiple promotions attached to an order, but only one of them is "active" at a time. Unfortunately I've got a client who often makes use of multiple promos on an order on their current site, and I'm trying to give them the same ability in solidus

yeah, only one promo will actually be active (the one that results in the largest discount)

Bleh, ok, I'll see if I can make something work, then. Thanks!

Hi all, I’m new in Solidus development. I’m trying to build an autocomplete textfield like Admin Panel > Products > Taxons. I have checked the default layout(backend > app > views > spree > admin > products > _form.html.erb) and the controller(backend > app > controllers > spree > admin > products_controller.rb). But still not understand how they work and how they to implement this component liked component. Please help.

Another promotion question! I see that spree has the ability to have a promotion automatically add an item to the cart when applied (https://guides.spreecommerce.org/user/promotions/creating_promotions.html#create-line-items), but it that functionality doesn't appear to be in solidus (or I completely missed it). Is that something that I could (hopefully) easily add in if it's not there?

Is there a way to eager load

Product#variants_and_option_values_for

?

Is it possible to calculate shipments without having added an address? The shop I'm building is only serving one country, so I could theoretically calculate shipping costs as soon as a product is added to the cart. Going through the code I think I probably need to build my own

Spree::Stock::Estimator

class and then call

order.create_proposed_shipments

during an orders

:cart

state. Is this the way to go or are there any other preferred ways to achieve this?

Kind of related to the above - but what is the correct way to handle digital-only goods in checkout flow? It seems like the Solidus state machine requires a shipping address to be present before an order can transition into the

:delivery

state. I know that stock locations can be marked as

fulfillable

or not to help support this, but I don't see any exemptions in the checkout state machine looking for that property.

And it would seem odd to me to have to ask the user to provide a shipping address for something that isn't physically shipped.

I know a lot of stores that sell a mix of digital and physical goods just ask for shipping anyway, I'm not sure how much work it would be to allow skipping that.