Tom Wilson
07/31/2023, 3:15 PMsolidus_stripe
gem to the V5 version. Because the two are not compatible at all, it seems like something is slightly wrong in the installer. In order to do this upgrade, I removed the solidus_stripe
gem from our application, and copied over the few classes we relied on. That part seems to work just fine.
But now, when I add back the gem at the new version and attempt to run bundle exec rails generate solidus_stripe:install
, I get strange behavior. It is not generating the migrations, nor is it generating the initializers. I can't quite figure out what is going wrong here. It seems to attempt to install migrations, and it seems like it makes some number of changes to my database schema, but no migration code is actually generated. Is this maybe because I have some migrations in my tree already from the previous version?
tom.wilson:agora (new_stripe_gem *)$ bundle exec rails generate solidus_stripe:install
append vendor/assets/javascripts/spree/frontend/all.js
run bin/rails railties:install:migrations FROM=solidus_stripe from "."
Would you like to run the migrations now? [Y/n] y
run bin/rails db:migrate from "."
tom.wilson:agora (new_stripe_gem *)$ git status
On branch new_stripe_gem
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: Gemfile
modified: Gemfile.lock
modified: db/structure.sql
modified: vendor/assets/javascripts/spree/frontend/all.js
no changes added to commit (use "git add" and/or "git commit -a")
tom.wilson:agora (new_stripe_gem *)$
Does anyone have any suggestions on how to actually execute this upgrade?elia
07/31/2023, 3:59 PMTom Wilson
07/31/2023, 4:00 PMelia
07/31/2023, 4:02 PMelia
07/31/2023, 4:09 PMelia
08/02/2023, 8:49 AM