ptrader
-
Posts
140 -
Joined
-
Last visited
Reputation Activity
-
ptrader got a reaction from Haku2 in 4.3: Commerce Subscription Manager
I am so disappointed that a simple feature I've been requesting since IP.Subscriptions/Nexus/Commerce is not included in this upgrade. Again.
IPB has always assumed subscriptions need to be on a rolling calendar basis. I totally understand there are a large number of communities that use that method. However, an equal number of communities would love to have subscriptions expire on a set calendar date, configurable in the package. My membership year is not on a rolling basis and and settinga hard expiration date in each transaction is very time-consuming.
It's one additional setting in the renewal options to set an expiration date for the package. That's it. How hard can this be? What is the rationale for not including it?
-
ptrader got a reaction from Alex914 in 4.3: Commerce Subscription Manager
I am so disappointed that a simple feature I've been requesting since IP.Subscriptions/Nexus/Commerce is not included in this upgrade. Again.
IPB has always assumed subscriptions need to be on a rolling calendar basis. I totally understand there are a large number of communities that use that method. However, an equal number of communities would love to have subscriptions expire on a set calendar date, configurable in the package. My membership year is not on a rolling basis and and settinga hard expiration date in each transaction is very time-consuming.
It's one additional setting in the renewal options to set an expiration date for the package. That's it. How hard can this be? What is the rationale for not including it?
-
ptrader got a reaction from opentype in 4.3: Commerce Subscription Manager
I am so disappointed that a simple feature I've been requesting since IP.Subscriptions/Nexus/Commerce is not included in this upgrade. Again.
IPB has always assumed subscriptions need to be on a rolling calendar basis. I totally understand there are a large number of communities that use that method. However, an equal number of communities would love to have subscriptions expire on a set calendar date, configurable in the package. My membership year is not on a rolling basis and and settinga hard expiration date in each transaction is very time-consuming.
It's one additional setting in the renewal options to set an expiration date for the package. That's it. How hard can this be? What is the rationale for not including it?
