-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce public subscription view page for cancel
, renew
and mandate
actions
#201
Comments
In internal HelpScout ticket https://secure.helpscout.net/conversation/1637278281/22756?folderId=1425710 we have a customer that doesn't see any payments attached to a subscription. This could indicate an issue in the
CC @rvdsteege |
it is possible that the |
What issues are we running into with these actions? Users use these action URL's in their customer communication, so I'd expect they function properly in a plugin release. |
Received an issue at support with the period dates moving forward on pending/incomplete renewals. This could be improved/resolved with better user subscription management functionality. Internal Help Scout ticket: https://secure.helpscout.net/conversation/2165411530/25264/ |
https://github.com/pronamic/wp-pay-core/blob/5ec06f5d31a3125d6912aecae6934c7f5e221009/src/Subscriptions/SubscriptionsModule.php#L105-L151
Something like: http://pay.local/?subscription=XXX&key=subscr_XXX&view=subscription or should we implement some rewrite rules?
http://pay.local/abonnement-inzien/{secret_40_chars_sha_1_hash}
http://pay.local/abonnement-inzien/9cf95dacd226dcf43da376cdb6cbba7035218921
Tools like Google Drive, Dropbox, Payt (https://factuurinzien.nl/) also use secrets in their public links.
The
$phase->get_created_periods()
and$period->get_payments()
methods currently don't exist.Cancel
Renew
Mandate
Use
wp_hash( $subscription->get_id() )
for an unique hash in a public URL, if users generate new salts (https://api.wordpress.org/secret-key/1.1/salt/) the old public links will also no longer work.The text was updated successfully, but these errors were encountered: