If it's anything like other @Painbaker add-ons, the options are under Appearance >> Styles >> SELECT WHICH STYLE >> then scroll down to the bottom for the add-ons style options.
If it's anything like other @Painbaker add-ons, the options are under Appearance >> Styles >> SELECT WHICH STYLE >> then scroll down to the bottom for the add-ons style options.
I don't have the addon so I can't give specific guidance. Perhaps it might be via a custom CSS in extra.less?I do see that now thanks, but he made one block blue and the others are default, as in to highlight a special.
It's a gamechanger. Snag it if you sell upgrades.I don't have the addon
@Painbaker I addressed it like this:Styling Bug:
The "Label" overlaps/covers the title of the paid registration. Try a long title like Annual Premium Membership. Especially evident with narrow columns like on the Upgrades page.

this add-on currently does not support display styling variations (in account type settings), it was built on XF 2.2 and still retains that support. However style property variations in addin style settings supportedI've added a dark mode version to my site, but the upgrades page doesnt look nice on it.
Are there style properties to add dark mode variant colors for background color, button color and text color?
If not then please add dark mode variants.
Should work since the add-on assigns upgrades to users in the standard wayI'm not sure this XF setting works in this add-on:
Disabled user upgrades:
Disables the selected user upgrades while this upgrade is active. This is helpful if you have tiers of the same upgrade and don't want people to buy multiple levels.
In an upgrade if I disable all others, the user can still click and purchase them (Stripe).
It has nothing related to tihs add-onI have notifications from paypal about failed IPN. Please check your server that handles PayPal Instant Payment Notifications (IPN). IPNs sent to the following URL(s) failed:
https://cafesaxophone.com/payment_callback.php?_xfProvider=paypal
These appear to be Paypal legacy subs, but I have not yet had a chance to check them all. The legacy upgrades are not actively purchase able so not available (I think this was advised when the new Paypal REST api was introduced). They have all been working fine for years, but in Feb it seems this issue started
Is it possible this is related to this addon?
Please consider to add support for dark mode.this add-on currently does not support style variations, it was built on XF 2.2 and still retains that support
please check if there are any duplicate entries for this user in the XF payment logA customer reported to me a strange edge case bug.
Apparently it gets confused if there were ever two subscriptions of the same user upgrade?
- User buys monthly subscription.
- Months later for some reason user subscribes to the same monthly subscription and now they have two subscriptions.
- User notices and cancels the second subscription.
- User eventually tries to cancel the original subscription but it says it has already been cancelled and can't cancel.
EDIT to add that this is all with Stripe.
Please consider to add support for dark mode.
@Alpha1 you can adjust them in the Style Properties for the add-on using variations.However style property variations in addin style settings supported

Also when a user has an active account type, it is removed from the account type page and is shown at the bottom in "Archived purchased upgrades." This is odd because it is active, not archived. Also the whole column is removed that shows the features, and it is simply listed as the title in the archived section.
If you go to the user upgrades page, the column is still there, which is good, and it does not state "Archived" it just lists the expiration date where the payment button is. This seems better than listing it is archived and removing the feature list as some users may need to revisit that.
Nope, your add-on still allows the purchase. I disabled the add-on and the only thing that showed on the upgrade page was the purchased upgrade, all others were hidden. But enabling your add-on shows all of them as purchasable, and they are by clicking the button, the one purchased has the expiration date where the purchase button is, but all others are still there to be purchased.Should work since the add-on assigns upgrades to users in the standard way
Not seeing anything different than the order of things I described.please check if there are any duplicate entries for this user in the XF payment log
Your template still allows users to cancel subscriptions in XF correct? For Stripe and the new PP API. Just wondering since the template is different and I had issues displaying a Notice. Thanks
Where is this managed? I see the expiration date where the purchase button is. Is that supposed to be clickable? Mine is not but maybe that's because it was a test/manual upgrade and not a real purchase?
We use essential cookies to make this site work, and optional cookies to enhance your experience.