octave
05/09/2022, 8:38 PM2.11.15
with the latest solidus_paypal_braintree
extension. I’m getting this error when submitting payment: StateMachines::InvalidTransition: Cannot transition state via :invalidate from :checkout (Reason(s): Payment method can't be blank)
Only in production, it works fine in development/sandbox. Did something change?Oleksandr Pozniak
05/10/2022, 9:30 AMYoussef
05/10/2022, 12:51 PMshipment_state: "pending",
payment_state: "balance_due",
order.payments.any? { |payment| payment.payment_method.type == "Spree::PaymentMethod::Check" }
Tyler Pulse
05/10/2022, 4:24 PMOleksandr Pozniak
05/11/2022, 1:32 PMStephen Dicks
05/11/2022, 2:48 PMTyler Pulse
05/11/2022, 7:00 PMdefault
and admin
- the former having access to customer related endpoints and with the latter containing the obvious. Regardless of what authentication and security layers you decide on post-user login, how can a user register in the client safely while using token
that is tied to admin
permissions? Is storing it in-memory our best bet? Even if you set up user-auth correctly, the idea of putting a bearer token
in your front end is scary. You are quite literally talking about the keys to the kingdom with regards to all your user's data. Has anyone tackled this?Tyler Pulse
05/11/2022, 7:02 PMAndre Schweighofer
05/12/2022, 3:21 PM*** ActiveRecord::SubclassNotFound Exception: The single-table inheritance mechanism failed to locate the subclass: 'Spree::Calculator::DefaultTax'. [...]
I can fix this by manually requiring "spree/calculator/default_tax"
but obviously I think this shouldn’t be needed. Is there anything I’m missing?Tyler Kocheff
05/12/2022, 6:34 PMPlease check your server that handles PayPal Instant Payment Notifications (IPN). IPNs sent to the following URL(s) are failing:
example.com/index.php/paypal/ipn/index/
Tyler Pulse
05/13/2022, 7:31 PMApplicationControllerDecorator
and renaming the file in snack case like so application_controller_decorator.rb
Felipe Passos
05/17/2022, 5:12 PMFetching gem metadata from <https://rubygems.org/>..........
Resolving dependencies.......
Bundler could not find compatible versions for gem "activerecord":
In snapshot (Gemfile.lock):
activerecord (= 7.0.3)
In Gemfile:
rails (~> 7.0.3) was resolved to 7.0.3, which depends on
activerecord (= 7.0.3)
solidus was resolved to 2.5.0.beta1, which depends on
solidus_core (= 2.5.0.beta1) was resolved to 2.5.0.beta1, which depends on
activerecord (~> 5.1.0)
Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Bundler could not find compatible versions for gem "rails":
In snapshot (Gemfile.lock):
rails (= 7.0.3)
In Gemfile:
rails (~> 7.0.3)
solidus was resolved to 1.0.0.pre, which depends on
solidus_core (= 1.0.0.pre) was resolved to 1.0.0.pre, which depends on
rails (~> 4.2.0)
Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Felipe Passos
05/17/2022, 5:12 PMGiven Reed
05/17/2022, 6:59 PM[1m[36mSpree::Variant Load (4.8ms)[0m [1m[34mSELECT "spree_variants".* FROM "spree_variants" WHERE "spree_variants"."deleted_at" IS NULL AND "spree_variants"."product_id" = $1 AND "spree_variants"."is_master" = $2 ORDER BY "spree_variants"."position" ASC[0m [["product_id", 3340], ["is_master", false]]
In fact, the 2 products that I'm having problems with don't have any variants. So they're set as the master.
I didn't see a flag or setting to relax that in the promo setup, and I haven't done any tweaking or adjusting to the rule, so it should just be the stock vanilla product rule. Or am I barking up the wrong tree completely and being the master is unrelated and it's something else all together?Felipe Passos
05/17/2022, 9:54 PMJose Coelho
05/17/2022, 10:24 PMIsmael Camara
05/21/2022, 9:59 PMTyler Kocheff
05/23/2022, 7:03 PMLocon
05/27/2022, 5:40 PMSpree::PaymentCreate
has the build_source
method that links the user payment_source with the order user, which is fine.
- If I skip this user linking using a flag, it doesn't save the credit card to the user's wallet.
2. Also, the Spree::Order
model has a method add_payment_sources_to_wallet
that uses the add_payment_sources_to_wallet_class
to add the payment source to the user's wallet. And this is executed during the order transition to complete (after_transition to: :complete, do: :add_payment_sources_to_wallet
)
- If I skip this step using a flag, it doesn't save the credit card to the user's wallet.
What I'm trying to find is a way where I can skip the 1st point that I mentioned above, because it's ok to link the payment source to the user.
But linking the payment source to the user is still adding the payment source to the user's wallet and I want to avoid that.
I'm sure that I'm skipping some step during the checkout process, and that step is marking as default the payment source and adding to the wallet.
Thanks in advance!Zachary Jones
05/27/2022, 11:01 PMjakemumu
05/30/2022, 1:27 AMreturn _success_response_.table.result.table.id
Utsav Khadka
06/04/2022, 3:37 PMLilly
06/10/2022, 3:13 AMWesley974
06/13/2022, 5:09 PMWesley974
06/13/2022, 5:09 PMpeter
06/13/2022, 5:12 PMWesley974
06/13/2022, 5:15 PMRasmus Styrk
06/14/2022, 6:35 PMbenmorganio
06/14/2022, 8:37 PMbenmorganio
06/14/2022, 8:37 PM/Users/ben/.asdf/installs/ruby/3.1.2/lib/ruby/gems/3.1.0/gems/ruby-vips-2.1.4/lib/vips.rb:162: warning: already initialized constant GObject::GOBJECT_TYPE
/Users/ben/.asdf/installs/ruby/3.1.2/lib/ruby/gems/3.1.0/gems/ruby-vips-2.1.4/lib/vips.rb:162: warning: previous definition of GOBJECT_TYPE was here