L'utente non può riacquistare un prodotto in abbonamento dopo averlo annullato

amalg · 6 Agosto 2021, 8:49pm

I’ve got an odd problem cropped up here with a subscriber.

They have no active subscriptions in under the Billing section;

In Stripe it shows as cancelled;

yet they cannot resubscribe… says already purchased;

Have I set something up incorrectly?

justin · 7 Agosto 2021, 4:50pm

That looks like you might have your webhook endpoint improperly configured. When the subscription period ends, Stripe sends a webhook which the plugin uses to remove group membership, and remove the user from being an existing customer on that product (which allows the user to purchase again).

You’ll need to make sure this is configured per the OP here: Discourse Subscriptions

One way you to confirm from your server:

./launcher enter app
rails c
u = User.find_by_username(<username>)
c = DiscourseSubscriptions::Customer.where(user_id: u.id)
subscription = DiscourseSubscriptions::Subscription.where(customer_id: c.customer_id)

Be sure to replace <username> with the actual username of the user.

If subscription returns [], there’s another issue going on. But if it returns a value, that likely confirms the missing webhook.

To delete the DiscourseSubscriptions::Subscription entry so the user can purchase the product again:

Make sure subscription has only one value by running subscription.count. If the value returned is greater than 1, you’ll have to do a bit more digging to make sure you’re deleting the correct subscription instance. If you delete the wrong one, your subscriptions data will be in an inconsistent state and likely yield weird behavior.

Once you’ve confirmed there’s only one subscription, then you can run:

subscription.destroy_all

Keep in mind that subscription is the value returned from the initial set of queries we ran in the Rails console.

Hope that helps!

amalg · 9 Agosto 2021, 9:21pm

Thanks @justin

• got to the last line subscription and ran it… returned this;

NoMethodError: undefined method customer_id' for #<DiscourseSubscriptions::Customer::ActiveRecord_Relation:0x000055be473772f0> from /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/relation/delegation.rb:110:in method_missing’

• Checked Stripe webhooks and it’s pointed to https://./s/hooks

• Events sent to webhook;

```
subscription_schedule.updated
```
```
subscription_schedule.expiring
```
```
subscription_schedule.created
```
```
subscription_schedule.canceled
```

• Stripe webhook log has one entry from setup date which looks to be establishing the events supported.

• I have an event entry in Stripe that is a cancellation of a subscription, but… the line entry says (effectively) “[subscription was canceled]” however when I click into the event, it says the event type is customer.subscription.deleted … which I notice is not listed in my webhooks event list.

Could the above be the problem?

justin · 9 Agosto 2021, 9:26pm

Looks like the line should be DiscourseSubscriptions::Subscription instead of ::Customer. Try that and see what you get!

amalg · 9 Agosto 2021, 9:42pm

[2] pry(main)> c = DiscourseSubscriptions::Subscription.where(user_id: u.id)
=> #DiscourseSubscriptions::Subscription::ActiveRecord_Relation:0x8020
[3] pry(main)> subscription = DiscourseSubscriptions::Subscription.where(customer_id: c.customer_id)
NoMethodError: undefined method customer_id' for #<DiscourseSubscriptions::Subscription::ActiveRecord_Relation:0x000055ec51164ca0> from /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/relation/delegation.rb:110:in method_missing’

justin · 9 Agosto 2021, 9:45pm

Sorry, I misunderstood where this was happening.

Try this instead:

./launcher enter app
rails c
u = User.find_by_username(<username>)
c = DiscourseSubscriptions::Customer.find_by(user_id: u.id)
subscription = DiscourseSubscriptions::Subscription.where(customer_id: c[:customer_id])

amalg · 9 Agosto 2021, 10:10pm

Ah…

[3] pry(main)> subscription = DiscourseSubscriptions::Subscription.where(customer_id: c[:customer_id])
=>

amalg · 11 Agosto 2021, 6:41pm

Do you think the lack of subscription data has anything to do with the customer.subscription.deleted event being missing?

Is there anything I should explore next at this point?

I’m particularly interested in focusing on why the subscription page shows “purchased” while the active subscriptions section shows no active subs… is there some other place in the database where sub info is stored which might be cleared / empty under the active subs section but somehow a “purchased” boolean is still set to true somewhere … or something like that?

amalg · 23 Agosto 2021, 5:25pm

Is there anything else to try here?

justin · 24 Agosto 2021, 4:42pm

Make sure in Stripe the purchase is fully cancelled and not waiting to be cancelled at the end of the period. You can also look under the Admin → Plugins → Discourse Subscriptions → Subscriptions area and look for this user’s username. If they have a subscription listed there, you can cancel it immediately.

Without further looking into your Discourse instance, I’m not sure how much further I can help.

amalg · 24 Agosto 2021, 8:51pm

yeah it’s not active under subscriptions in the plugin area, and also not on stripe either… the only thing that indicates anything is still active is if the user goes to the subscription page, they see a little green “purchased” checkmark and “go to billing”.

If I go to billing as the user in question, nothing;

So my question is - what in the database triggers that green checkmark and can it be cleared?

justin · 24 Agosto 2021, 10:46pm

github.com

discourse/discourse-subscriptions/blob/6e96f073788212b9c832fa397850e377a3298c47/app/controllers/discourse_subscriptions/subscribe_controller.rb#L161-L168

    
      
          def current_user_products
            return [] if current_user.nil?
          
          
  Customer
              .select(:product_id)
              .where(user_id: current_user.id)
              .map { |c| c.product_id }.compact
          end

If this list includes the Stripe product id as per here:

github.com

discourse/discourse-subscriptions/blob/6e96f073788212b9c832fa397850e377a3298c47/app/controllers/discourse_subscriptions/subscribe_controller.rb#L156

    
      
            end
          end
          
          
private
          
          
def serialize_product(product)
            {
              id: product[:id],
              name: product[:name],
              description: PrettyText.cook(product[:metadata][:description]),
              subscribed: current_user_products.include?(product[:id]),
              repurchaseable: product[:metadata][:repurchaseable]
            }
          end
          
          
def current_user_products
            return [] if current_user.nil?
          
          
  Customer
              .select(:product_id)
              .where(user_id: current_user.id)

Then the front end will display it as purchased. You may need to dig around the console with these queries to find out where it’s located. I almost guarantee there’s a record hanging around there yet.

amalg · 2 Febbraio 2023, 6:36am

Ok, so che sto riportando in vita questa discussione, ma 1) questo continua a non essere risolto e 2) ho trovato del tempo per approfondire di nuovo… si scopre che ero un idiota che non sapeva seguire le istruzioni. Ecco come ho scoperto di essere un imbecille e perché ora sono pronto a risolvere questo problema (con un po’ di aiuto).

Quello che ho finito per fare è stato esportare un CSV da Stripe di tutti gli account cancellati. Mi sono concentrato sullo stesso utente di Discourse a cui si fa riferimento sopra in questa discussione, che era un abbonato, si era cancellato, ma poi non poteva riabbonarsi perché la pagina di abbonamento mostrava “acquistato” anche se la sua pagina degli abbonamenti attivi non mostrava abbonamenti. Nei dati CSV, il suo record mostrava “cancellato” con i seguenti dati;

id (sub_JNWejdDo4qhLG5)
customer_id (cus_JmiMoqZNTzUNxt)
user_id (id utente Discourse 4981)

Poi mi sono collegato al container dell’app, sono entrato nella console Ruby e ho iniziato a curiosare. Per prima cosa ho cercato il suo ID cliente in DiscourseSubscriptions::Customer e l’ho trovato.

[3] pry(main)> DiscourseSubscriptions::Customer.where(customer_id: 'cus_JNWeiIWTs6YOwQ')
=> [#<DiscourseSubscriptions::Customer:0x000055db2d48eb40
  id: 16,
  customer_id: "cus_JNWeiIWTs6YOwQ",
  product_id: "prod_JJbwYnKz0T5Z9h",
  user_id: 3256,
  created_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00,
  updated_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00>]

Successivamente ho cercato in DiscourseSubscriptions::Subscription per vedere se questo utente avesse abbonamenti e si scopre che sì, li aveva;

[1] pry(main)> DiscourseSubscriptions::Subscription.where(external_id: 'sub_JNWejdDo4qhLG5')
=> [#<DiscourseSubscriptions::Subscription:0x000055854e1e1620
  id: 16,
  customer_id: 16,
  external_id: "sub_JNWejdDo4qhLG5",
  created_at: Tue, 27 Apr 2021 07:45:07.459681000 UTC +00:00,
  updated_at: Tue, 27 Apr 2021 07:45:07.459681000 UTC +00:00>]

Quindi, sembra che possa semplicemente rimuovere questo record di abbonamento e risolvere tutto… per questo utente. Il fatto è che ogni utente cancellato che ho controllato nel mio export CSV aveva ancora abbonamenti rimanenti nel sistema. Ovviamente c’è una disconnessione in qualche modo / da qualche parte tra il webhook di Stripe e il plugin di abbonamento… solo che non so dove / come.

Primo; come rimuovo in sicurezza i dati del record di abbonamento per un particolare utente? Spiegamelo come se avessi 5 anni. Sono al prompt della console Ruby, come faccio a garantire che vengano rimossi solo i dati di abbonamento dell’utente di destinazione e che non cancelli i dati di abbonamento di tutti?
Secondo, come posso risolvere il meccanismo del webhook di cancellazione dell’abbonamento?

Tutto il vostro aiuto è molto apprezzato!

AGGIORNAMENTO:

Ok, sono andato un po’ più avanti… sono riuscito a capire come usare .delete_by per rimuovere solo i dati di abbonamento per l’utente di destinazione;

[1] pry(main)> DiscourseSubscriptions::Subscription.delete_by(external_id: 'sub_JNWejdDo4qhLG5')
[2] pry(main)> DiscourseSubscriptions::Subscription.where(external_id: 'sub_JNWejdDo4qhLG5')
=> []

Tuttavia, il record del cliente ha ancora un product_id associato;

[3] pry(main)> DiscourseSubscriptions::Customer.where(customer_id: 'cus_JNWeiIWTs6YOwQ')
=> [#<DiscourseSubscriptions::Customer:0x0000560ec18e4948
  id: 16,
  customer_id: "cus_JNWeiIWTs6YOwQ",
  product_id: "prod_JJbwYnKz0T5Z9h",
  user_id: 3256,
  created_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00,
  updated_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00>]

Ciò significa che vedono ancora il segno di spunta verde e non possono riabbonarsi… quindi ho applicato il “destroy_all” all’oggetto Customer… e ha funzionato! Ma solo per quell’utente, ovviamente…

[4] pry(main)> DiscourseSubscriptions::Customer.where(customer_id: 'cus_JNWeiIWTs6YOwQ').destroy_all
=> [#<DiscourseSubscriptions::Customer:0x0000560ec19770e0
  id: 16,
  customer_id: "cus_JNWeiIWTs6YOwQ",
  product_id: "prod_JJbwYnKz0T5Z9h",
  user_id: 3256,
  created_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00,
  updated_at: Tue, 27 Apr 2021 07:45:07.455275000 UTC +00:00>]

Quindi ora si tratta solo di diagnosticare perché il webhook di Stripe per gli abbonamenti cancellati non funziona.

Argomento		Risposte	Visualizzazioni
Can't cancel a subscription for Discourse Bug subscriptions , fixed	3	97	Luglio 16, 2024
Subscription update problem Bug subscriptions	11	177	Dicembre 13, 2024
Discourse Subscriptions - user not removed from group when subscription cancelled Support subscriptions	4	789	Dicembre 22, 2022
Subscriptions: Deleted data in Stripe, now plugin errors Support subscriptions	5	856	Febbraio 9, 2021
Discourse Subscriptions Plugin Plugin official , subscriptions , payments , included-in-core	46	49429	Novembre 7, 2025

L'utente non può riacquistare un prodotto in abbonamento dopo averlo annullato

Argomenti correlati