Subscription end date 2.0.19/2.1.1

[-Rock Lee-]

I am trying to adapt another payment method and I realized when the subscription is manually assigned where the start date is set, for example, April 1, 2022 and the end date is April 1, 2002. It adds it without problems and in most systems what i tried it does not allow this it has a limit of the same day maximum, I suppose for some reason you add a manually user and for some reason it does not run the background tasks, same user would be indefinitely "subscribed". When executing the subscription task, it clearly terminate the subscription having a date of 10 years ago, so I don't think it's a bug in itself, just a detail, but I didn't know whether to comment on it.


Regards!

[Sesquipedalian]

I'm sorry, but I don't really understand what you are trying to describe here.

You seem to be saying that you somehow created a subscription where the end date is earlier than the start date. I don't know how you could have done that, since the user interface for managing subscriptions does not allow that.

[-Rock Lee-]

Excuse me, my Spanish beats my English when explaining and since it's the opposite, misses the point of my explanation. I go slowly again first in 2.0.x it takes me negative values when defining days such as -10 -20 or -30 but it puts correctly the days of the subscription (if I do the same thing in 2.1.x it tells me to put a correct value).

You cannot view this attachment.

You cannot view this attachment.

The problem is being an administrator when you manually create a subscription and define the start/end date, if the background tasks/cronjob is executed, the subscription ends but if for some reason it is not executed, the account remains active indefinitely

You cannot view this attachment.

This also happens in 2.1.x if it is applied manually the subscription can be set to an earlier date and it is valid.


Regards!