If I have a membership expiration of June 30 (today) and a member goes in to renew, I noticed that the "Subscription" option (Stripe) is no longer visible.

It was showing up as late as yesterday.

Is this by design since the person is renewing on the expiration date?  Or is there a setting I should be looking at to allow this payment option?

 

Thanks. 
 

Duration: 1 year. (Set up annually per calendar year, July 1 - June 30)

- The subscription option was visible as late as yesterday (June 29th)
- I had people subscribe last year without issue. (as far as I can tell they are set to renew automatically tonight) - Though I need to check my Stripe account to see for sure.
- I also set it so that if people renew 1 month before June 30th, the membership would expire 1 year + 1month later.

Was there a recent update? (I think I may have updated last night)

Thanks!
 

--- 1 ----
I've checked the history logs and saw the note below:

stripe Invalid plan initial duration. Error: Stripe: Trying to subscribe 367 days. Maximum supported is 365 days (1 year).

all trace: called in class cbpaidHistory::logError() on line 571 in file cbpaidPayHandler.php
called in class cbpaidPayHandler::_setLogErrorMSG() on line 429 in file cbpaidsubscriptions.stripe.php
called in class cbpaidstripeoem::getPaymentBasketProcess() on line 178 in file cbpaidControllerPaychoices.php
called in class cbpaidControllerPaychoices::getPaymentMethodsParams() on line 391 in file cbpaidControllerPaychoices.php
called in class cbpaidControllerPaychoices::getPaymentBasketPaymentForm() on line 251 in file cbpaidControllerOrder.php
called in class cbpaidControllerOrder::showBasketForPayment() on line 258 in file cbpaidControllerCBTab.php
called in class cbpaidControllerCBTab::getTabComponent() on line 1155 in file cbpaidsubscriptions.php
called in class getcbpaidsubscriptionsTab::getTabComponent() on line 92 in file cbpaidControllerCBComponent.php
called in class CBplug_cbpaidsubscriptions::getCBpluginComponent() on line 880 in file cbPluginHandler.php
called in class cbPluginHandler::call() on line 1611 in file cbTabs.php called in class cbTabs::_callTabPlugin() on line 1725 in file cbTabs.php
called in class cbTabs::tabClassPluginTabs() on line 733 in file comprofiler.php

However, this appeared for a user who selected the single billing option and the payment went through okay.

My guess is since I had a single billing and recurring setup, I gather it generated this error by default.

Would this be the reason why the "Subscription button was not appearing as an option?

What I am confused about is that the subscription is not 367 days as the current subscription was set to expire on June 30 when the new membership term started.

Users are simply paying a few days in advance.    The subscription option seems to be a false error preventing users from choosing it.

 

--- 2 ---

I also had a user sign up on June 6th who paid using single billing (even though both single and recurring was enabled) but there was no such error that appeared for them.   

I have the plan set up such that anyone signing up on Jun 1 has the membership extended to June 30, 2024 (i.e. bonus time of 1 month).

I believe I recently updated Joomlapolis and all plugins a couple of days ago so it may be related to a recent change maybe?

--- 3 ---

Last year I had 2 customers successfully choose the recurring billing option. They paid on June 29th, but according to Stripe, the next payment is scheduled to be processed today (June 30, renewal date).  

There were no error messages in the logs regarding these users.   I will wait to see what happens when the subscription is set to expire tonight (June 30) to see if Stripe does process the payment.

They paid on June 29th, 2022, but recurring payment takes place at the renewal date - Is this the expected behaviour?

 

--- 4 ---

Also, another issue I've discovered since March 2023 is Stripe had no problem adding the user's name in the Customer section to align with the users on the website. Now they are coming through as "Guest", which will make it more difficult to monitor.

Has something changed with the Stripe plugin or have I overlooked new configuration settings since it was updated?