This used to work. If I renew a member's subscription in the back-end, it doesn't update the last_renewed_date in the #__cbsubs_subscriptions table, although it does set status and expiry_date correctly.
This is a problem for us, as we key off last_renewed_date to do some processing on recently renewed subscriptions, which could be done in either the front-end or the back-end. If there's a better way to do this, please advise.
TIA.
Last edit: 8 years 7 months ago by krileon. Reason: Added [SOLVED] tag to subject
Was the plan already expired or was it a renewal of an already active subscription?
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Looking closer at it, I think this is an edge case. I hadn't noticed in my testing that the user already had an active subscription of a different type. When I renewed the second subscription, it didn't set the date_last_renewed.
krileon
