Fede Barriola
08/04/2022, 2:14 PMKurtis
08/04/2022, 5:40 PMKurtis
08/04/2022, 5:40 PMKurtis
08/04/2022, 5:42 PMself.brand_filter
but not inside the brand_any scopeJared Norman
Kurtis
08/04/2022, 6:09 PMJared Norman
Kurtis
08/04/2022, 6:13 PMKurtis
08/04/2022, 6:13 PMKurtis
08/04/2022, 6:13 PMKurtis
08/04/2022, 6:13 PMKurtis
08/05/2022, 9:08 AMKurtis
08/05/2022, 9:10 AMKurtis
08/05/2022, 9:14 AM<http://localhost:3000/t/tyres?per_page=&search%5Bprice_range%5D%5B%5D=%C2%A350.00+%E2%80%93+%C2%A3100.00&search%5Bbrand%5D%5B%5D=Yokohama>
This is an example of using Price Range + BrandDenys Medynskyi
08/05/2022, 10:36 AMKurtis
08/05/2022, 12:08 PMKurtis
08/05/2022, 12:09 PMKurtis
08/05/2022, 4:32 PMKurtis
08/05/2022, 4:33 PMKurtis
08/05/2022, 4:33 PMKurtis
08/05/2022, 5:01 PMKurtis
08/05/2022, 5:13 PMKurtis
08/05/2022, 5:29 PMVlad Danciu
08/06/2022, 8:22 AMKurtis
08/06/2022, 9:54 AMAlec van Niekerk
08/06/2022, 10:41 AMKurtis
08/06/2022, 5:24 PMundefined method :applies_from
for solidus_related_products? I am using the solidusio-contrib version. I can see that field isn’t in the schema so perhaps it’s been removed and it’s getting an issue from the relation_type validator? Any help appreciated. ThanksAlec van Niekerk
08/08/2022, 11:52 AMnotification_url
and return_url
2. If the transaction is successful the payment gateway POSTs to notification_url
3. If the payment gateway receives a 200
from above POST it redirects the user to return_url
Solidus provides an easy way to write a custom payment method by allowing - among other things - the developer to add a partial for the custom payment method. This works really well for on site payments or payments that will be captured manually.
In my case I've setup it up like this:
• In the partial I'm overriding the checkout_form_payment
form's action
attribute to point to the payment gateway's site instead of the checkout_controller
• I've added a custom controller which serves as the endpoint for the payment gateway's notification_url
where I capture payment source details and progress the state of the order
like it would have happened in the original checkout_controller
• I return the user to the /checkout/confirm
(since this is the next state) page via the return_url
upon successful transaction
My issues with that workflow are:
• capturing the payment happens before the user has "confirmed" the order, so a scenario can play out where the user successfully completes the transaction on the payment gateway's site, closes their browser, and then the order isn't really "completed"
• I can take another path and simply update the order all the way to "completed" when the payment gateway sends notification of a successful transaction, but then the user doesn't get to "confirm" the order after reviewing it (we skip the /checkout/confirm
page)
Ideally I would like to only redirect to the payment gateway when the user confirms the order. As far as I can tell there is no "neat and tidy" way of overriding the confirmation portion of the checkout workflow like the payment method part. I know I could just override the entire _confirm
partial, but as I would like to add the payment gateway as a gem for others to use, I'm guessing this isn't necessarily the best route to take.
Could anyone shed any advice on a better way to handle this kind of off-site custom payment method?
Thanks!jakemumu
08/08/2022, 4:01 PMNameError: uninitialized constant SolidusRelatedProducts::Product::RSpec
but only during a heroku deploy -- anyone seen such a thing?Kurtis
08/09/2022, 6:14 PMapp/views/spree/api/payments/source_views/_paypal_braintree.json.jbuilder
is still used?