Closed lastobelus closed 4 years ago
I think what is happening here is your 20180723175026_setup_slc_shipping_services.rb migration line 33 is trying to use a record that acts_as_commontator but the commontator tables do not exist yet.
I think I can probably add a guard to acts_as_commontator so it doesn't blow up if the tables don't exist yet...
👍
...also acts_as_commontable
OK I reproduced the issue in my dummy app and... not sure how it should be fixed. If the Commontator tables don't exist yet but you are creating a record that should have a comment thread, then Commontator cannot automatically create the thread record. I could make it skip creating the thread in that case, but then it would be a surprise when some (but not all) records are missing the comment thread... A fix for your app would be to reorder the migrations so Commontator's migrations happen before the failing migration when running from scratch.
Hmm on second thought... the thread is supposed to build automatically anyway. So maybe having it delay thread creation is not so bad.
Fixed in v6.2.0.
it may only be affecting migrations with a
reversible do |change|
block.example trace: