At least, it worked for the first test I did. The second test (same user, same subscription) failed in the same way - subscription not expiring with the cron job (or with clicking on the URL the cron invokes).
Something on frontend is interfering with the CRON URL. As it's a frontend URL it could be caching, a 3rd party extension, etc.. I've set your expiration to expire from CRON and/or admin backend. I then navigated to CBSubs payment center and the user expired fine. Unfortunately I've no idea what on frontend is conflicting with the CRON usage.
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.
krileon
