Skip to content
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

Feature Request: check out for the Addon Package for the user's level if user logs in from the checkout page. #51

Open
ipokkel opened this issue Aug 25, 2021 · 4 comments

Comments

@ipokkel
Copy link
Member

ipokkel commented Aug 25, 2021

When a logged-out user logs in on the checkout page to purchase an Addon Package the login redirects returns the user to checkout with the level that the checkout was set for before login despite the user belonging to a higher level (that is checked for the page in Require Membership).

Should we consider checking in cases like these if the user is logged in and on the checkout page if they already belong to a membership level that may purchase the Addon Package and set checkout for the level the member belongs to?

How to recreate:

  1. Create a free level, (ID 1), and a paid level (ID 2)
  2. Install and activate Addon Packages
  3. Create a new page, check both levels in Require Membership checkbox, and add $5 in Addon Package cost.
  4. Check out for the paid level (ID 2) and log out.
  5. Go to the page created and click on the checkout button, on the checkout page note that the level is the free level (ID 1).
  6. Click on the log-in link, fill in user details and log in.
  7. Note that the login redirects to checkout for the free level (ID 1) + the Addon Package
@Sun121232
Copy link

Hi,
Is this possible for non Member when non member will click purchase for $5 it will automatically redirect checkout and there paid level(id 2) + addon package

@MaryOJob
Copy link

MaryOJob commented Feb 4, 2022

Similar request
Moderators only: #399568

@sensemonster
Copy link

The current state of the add-on doesn't represent what is shown in the documentation and the accompanying video.
There are quire a few issues with the way it actually works and maybe it is best to withdraw it and rework the whole thing.

@kimcoleman
Copy link
Member

This is related to #64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants