El usuario no puede volver a comprar un producto de suscripción después de cancelarlo

amalg · 6 Agosto, 2021 20:49

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 16:50

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 21:21

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 21:26

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

amalg · 9 Agosto, 2021 21:42

[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 21:45

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 22:10

Ah…

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

amalg · 11 Agosto, 2021 18:41

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 17:25

Is there anything else to try here?

justin · 24 Agosto, 2021 16:42

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 20:51

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 22:46

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 Febrero, 2023 06:36

Ok, sé que estoy reviviendo este hilo, pero 1) esto sigue sin resolverse y 2) encontré tiempo para investigar esto de nuevo… resulta que era un imbécil que no sabía seguir instrucciones. Así es como descubrí que soy un tonto y por qué ahora estoy listo para resolver esto (con algo de ayuda).

Lo que terminé haciendo fue exportar un CSV de Stripe de todas las cuentas canceladas. Me centré en el mismo usuario de Discourse al que se hace referencia anteriormente en este hilo, que era suscriptor, se había cancelado, pero luego no pudo volver a suscribirse porque la página de suscripción aparecía como “comprada” a pesar de que su página de suscripciones activas no mostraba ninguna suscripción. En los datos del CSV, su registro aparecía como “cancelado” con los siguientes datos:

id (sub_JNWejdDo4qhLG5)
customer_id (cus_JmiMoqZNTzUNxt)
user_id (id de usuario de Discourse 4981)

Luego me adjunté al contenedor de la aplicación, entré en la consola de Ruby y comencé a investigar. Primero busqué su ID de cliente en DiscourseSubscriptions::Customer y lo encontré.

[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>]

A continuación, busqué en DiscourseSubscriptions::Subscription para ver si este usuario tenía alguna suscripción y resulta que sí, sí la tenía;

[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>]

Entonces, parece que simplemente puedo eliminar este registro de suscripción y arreglar todo… para este usuario. El hecho es que cada usuario cancelado que revisé en mi exportación CSV todavía tenía suscripciones restantes en el sistema. Obviamente, hay una desconexión de alguna manera / en algún lugar entre el webhook de Stripe y el plugin de suscripción… simplemente no sé dónde / cómo.

Primero; ¿cómo elimino de forma segura el registro de suscripción de un usuario en particular? Explícamelo como si tuviera 5 años. Estoy en el prompt de la consola de Ruby… ¿cómo me aseguro de que solo se eliminen los datos de suscripción del usuario objetivo y no se borren los datos de suscripción de todos?
Segundo, ¿cómo soluciono el mecanismo del webhook de cancelación de suscripción?

¡Toda tu ayuda es muy apreciada!

ACTUALIZACIÓN:

Ok, avancé un poco más… logré averiguar cómo usar .delete_by para eliminar solo los datos de suscripción del usuario objetivo;

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

Sin embargo, el registro del cliente todavía tiene un product_id asociado;

[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>]

Esto significa que todavía ven la marca verde y no pueden volver a suscribirse… así que apliqué el “destroy_all” al objeto Customer… ¡y funcionó! Pero solo para ese usuario, por supuesto…

[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>]

Así que ahora solo queda diagnosticar por qué el webhook de Stripe para suscripciones canceladas no está funcionando.

Tema		Respuestas	Vistas
Can't cancel a subscription for Discourse Bug subscriptions , fixed	3	97	16 Julio 2024
Subscription update problem Bug subscriptions	11	176	13 Diciembre 2024
Discourse Subscriptions - user not removed from group when subscription cancelled Support subscriptions	4	789	22 Diciembre 2022
Subscriptions: Deleted data in Stripe, now plugin errors Support subscriptions	5	856	9 Febrero 2021
Discourse Subscriptions Plugin Plugin official , subscriptions , payments , included-in-core	46	49346	7 Noviembre 2025

El usuario no puede volver a comprar un producto de suscripción después de cancelarlo

Temas relacionados