solidus

Say I have a gem, how do I get a event/subcriber to work? It does not appear to autoload. Followed the example per the docs. Copying the file to subscribers/xxx_subscriber.rb works

if your gem is not a Solidus extension this might be helpful <https://github.com/solidusio/solidus_support/blob/09bfde4e67496167aca79cf23f05c7d8333031ac/lib/solidus_support/engine_extensions.rb#L34>

It sounds like what “works” in your case is copying the subscriber file out of your gem into {app root}/subscribers/

In a credit card fails and needs to be updated by the customer what flag is set or where what is the simplest way to determine that a user has outdated CC information?

I assume it's to grab the last payment that was attempted and see if it was valid or not

but I guess there's no default callback that sets something on he source that says 'this is invalid'

This would probably be different from one payment method to another, but you would need to look at the payment record itself and based on that determine if the source is bad or not. There are many reasons why a payment could fail and not all mean the customer needs to change their payment source, but that’s probably a business decision based on what the gateway response was. Sometimes it’s just sufficient to retry the payment at a later date (like in the case of NSF).

Thanks <@U03M5C5RX> appreciate the response

No problem! I hope this is helpful, I know some payment providers like Stripe have a way to send you a webhook when a customer updates their card because sometimes even expired cards can be charged successfully if the customer just renewed it, however I’ve never implemented anything like that. The scenario I’ve had to deal with is implementing a retry schedule based on the type of failure.

Got it.. yes I sorta wish that was taken care of but I certainly can understand it being application specific.

What's the default time zone used in Solidus' "Complete date"?

database stores UTC, but it displays in the rails app's configured time zone

Hi guys, I have been reviewing eCommerce solutions for a client for the last month and solidus looks great.

The one problem I am facing for my clients is they sell Fruits and Vegetables by weight.

Many of the eCommerce solutions don't cater for price based on weight.  Does anyone know if solidus supports this or if it would be an easy customization?

Thanks.

Hi <@U02ACS1KB3L> seems to be is possible: <https://stackoverflow.com/questions/31265388/spree-prices-based-on-weight>

Thanks <@U0255G4EU9J>, I have seen the variants used before.  The problem I have is the price is per kilogram.

So a transaction of 1.67kg is not easy to create using variants.

I have tried to create a price per 1gram but the pricing can't usually go past two decimal places.

Ok got it, that was I did (price per 1gram)  long time ago with my point of sale :<http://donmanolo2.sourceforge.net/>

On Magma <@U0ECETZPV> wrote this article: <http://blog.magmalabs.io/2020/10/22/how-pricing-selection-works-in-solidus.html>

Every time I try to install Solidus (through following the installation guide), I get this error message

image.png

When I do `rails app:update:bin` it still doesn't work for some reason. It's also giving me the same error message

I’m not sure what’s going there, but the issue doesn’t look like it has anything to do with Solidus specifically. Something is just messed up with your binstubs. 

What about removing the bin stub and calling that command again?

Yea sorry for the mishap! How would you go and remove the binstubs via cli?

I’d just `rm bin/rails` and then `bundle exec app:update:bin` see if that creates you anew correct binstub

Any reason why running `Spree::Order.where("created_at &lt; ? and state='cart'", 45.days.ago).destroy_all` as a nightly job would be a bad idea? We have some customers coming back after a looong time and then they end up having goofy carts with out-of-stock line items and so on.

Keeping your discussion in mind, it might be a good idea to "expire" a cart and add a before callback on an order's load that if it is expired, it should be checked for it's line_items being up-to-date and then load the order, otherwise expire it (line_item or order whichever works better). It will be alittle code but this will sit well with all parties.

larger shops with an  analytics team they might bark about the hard delete.

ITs interesting data to know waht people added when

but other than that I can't thin of an issue

ahhh yes that is an interesting point. Maybe just otherwise invalidating old orders might be a better move

right looks like we can’t just `cancel!`  from ‘cart’. Probably a new ‘expired_cart’ state that can only transition from cart / address / delivery / confirm

<@U4U807GHH> transitioning to an expired_cart

then you could generate a metric for carts that were eventually purchased vs left to expire

Hi everyone, i have a issue with solidus. Im using active storage and s3 bucket for upload my images, but the images when the signed url of aws expires dosent show again. I read that issue resolved increasing the url_expires_in, but im not sure. Any suggestions?

Any chance the issue is that you're caching those signed URLs? I think they should be regenerate on each request.

Regardless, there's not really benefit to storing your images privately. Make them public and your app won't even have to generate signed URLs; it can just use the regular public URL.

I faced the same issue when I was using an unpaid plan as it was freeing up space after some time and that time is random (can be a few minutes to a few days). I switched to paid plan and it worked.

I am having similar issues. <@U03P8V71Y> I set the bucket permissions on my s3 to be public.  What is strange is that I can copy and URL from the s3 browser utility and they display fine.  Yet after a few minutes inside of my products page, I get a 403, with a specific error of "Access Denied" in the browser console.

Sounds like it's still uploading the files as private and using presigned URLs then. 

You can just look at the URLs to confirm. 

<@U03P8V71Y> thank you for the reply. Looking at the URL on the front end side it is still trying to send a signed URL.  On the admin side, I am getting a clean URL.  I have read through the active storage guide <https://edgeguides.rubyonrails.org/active_storage_overview.html> and my `storage.yml` is specifying `public: true` I have configured my S3 storage on VULTR to be public. I can specify a URL of any image in my bucket and it will display correctly as would be expected. I have rebooted my server and cleared my cache on the browsers I am testing on.

To solve this riddle I ended up deleting all of the images that were uploaded before `public: true` was set in `storage.yml` for my S3 settings.  Once I did this and uploaded the new images on both the admin and front end sides I got a clean URL and the code is no longer trying to set a pre-signed URL.