cdub
Well-known member
Is this compatible with Paid Registration add-on?Yes, how soon the reminder is sent before the upgrade expires can be configured per user upgrade.
Is this compatible with Paid Registration add-on?Yes, how soon the reminder is sent before the upgrade expires can be configured per user upgrade.
If they create a normal user upgrade it should work.Is this compatible with Paid Registration add-on?
Yes, users can opt-out individually and it can be configured to only send expires and not soon-to-expire noticesIs it possible to turn the emails off and on individually?
We only have subscriptions and I really I only want emails when a subscription lapses or expires, I don't want to send any reminders leading up to the renewal if everything is in good order with an active subscription.
I see. In this case, would I have to uninstall and re-install the add-on to end the server errors?This isn't related to my add-on, and looks to be an XF bug.
This happens if the user doesn't exist for a user-upgrade. This might have happened if the user was deleted from the database or the user-delete process didn't work correctly.
As payment profiles I am running Paypal , Cryptocurrency and a hollow payment profile for testing purposes. On PayPal I do not want any of the users to receive any notifications but for the others can I set up this add-on to send notifications only to those users that used the Cryptocurrency payment profile?It is per user-upgrade, not per payment profile. Due to limitations of XF user upgrades (and some payment profiles) you may end up a user-upgrade per payment profile.
An example of this is if you want to two recurring services with BrainTree. This requires two seperate payment profiles. No idea why.
Hello Xon,It is per user-upgrade, not per payment profile. Due to limitations of XF user upgrades (and some payment profiles) you may end up a user-upgrade per payment profile.
An example of this is if you want to two recurring services with BrainTree. This requires two seperate payment profiles. No idea why.
Yeah, fair enough. I think adding a few simple additional phrases should make this doable. I'll look into that for the next release.They all end up using the phrase from the Expiring User Upgrades add-on. Can you look into how we can ensure that purchased upgrade alerts and gifted upgrade alerts are not the same message so that our users are not confused?
Yeah, fair enough. I think adding a few simple additional phrases should make this doable. I'll look into that for the next release.
May be quite a few phrases, ugh.
- Require php 7.2+
- Fix recurring upgrades did not send expiry notices >24 hours before they where due to expire
- Shorten various notification alerts
- Improve scalability of notifying large number of users about expiring upgrades
- Improve @NixFifity's Gift Upgrades integration. Titles for gifted upgrades/subscriptions are prefixed with "gifted" (editable phrase).
- Add per-user upgrade "Exclude payment providers from notifications" option to skip user upgrades which have...
[HEADING=2]Stack trace[/HEADING]
#0 src/XF/Mvc/Entity/Entity.php(572): XF\Mvc\Entity\Entity->set('exup_excluded_p...', NULL)
#1 src/addons/SV/ExpiringUserUpgrades/XF/Entity/UserUpgrade.php(156): XF\Mvc\Entity\Entity->__set('exup_excluded_p...', NULL)
#2 src/XF/Mvc/Entity/Entity.php(1272): SV\ExpiringUserUpgrades\XF\Entity\UserUpgrade->_postSave()
#3 src/XF/ControllerPlugin/Toggle.php(43): XF\Mvc\Entity\Entity->save()
#4 src/XF/ControllerPlugin/Toggle.php(11): XF\ControllerPlugin\Toggle->toggle('XF:UserUpgrade', 'can_purchase', Array)
#5 src/XF/Admin/Controller/UserUpgrade.php(145): XF\ControllerPlugin\Toggle->actionToggle('XF:UserUpgrade', 'can_purchase')
#6 src/XF/Mvc/Dispatcher.php(352): XF\Admin\Controller\UserUpgrade->actionToggle(Object(XF\Mvc\ParameterBag))
#7 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:UserUpgrade', 'Toggle', Object(XF\Mvc\RouteMatch), Object(SV\ExpiringUserUpgrades\XF\Admin\Controller\UserUpgrade), NULL)
#8 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(SV\ExpiringUserUpgrades\XF\Admin\Controller\UserUpgrade), NULL)
#9 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#10 src/XF/App.php(2353): XF\Mvc\Dispatcher->run()
#11 src/XF.php(524): XF\App->run()
#12 admin.php(13): XF::runApp('XF\\Admin\\App')
#13 {main}
[HEADING=2]Request state[/HEADING]
array(4) {
["url"] => string(38) "/forums/admin.php?user-upgrades/toggle"
["referrer"] => string(62) "https://www.mysite/forums/admin.php?user-upgrades/"
["_GET"] => array(1) {
["user-upgrades/toggle"] => string(0) ""
}
["_POST"] => array(5) {
["_xfToken"] => string(8) "********"
["can_purchase"] => array(8) {
[2] => string(1) "1"
[1] => string(1) "1"
[34] => string(1) "0"
[35] => string(1) "1"
[30] => string(1) "0"
[32] => string(1) "0"
[31] => string(1) "0"
[33] => string(1) "0"
}
["_xfRequestUri"] => string(32) "/forums/admin.php?user-upgrades/"
["_xfWithData"] => string(1) "1"
["_xfResponseType"] => string(4) "json"
}
}
- Fix "Attempted to set 'exup_excluded_payment_provider_ids' while a save was pending without forceSet" error on disabling a user upgrade
Yeah, fair enough. I think adding a few simple additional phrases should make this doable. I'll look into that for the next release.
May be quite a few phrases, ugh.
We use essential cookies to make this site work, and optional cookies to enhance your experience.