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

Front End Users/Authors are able to change plan from dashboard, without paying. #2159

Open
2 tasks
CorstoWebDesign opened this issue Dec 5, 2024 · 0 comments
Open
2 tasks

Comments

@CorstoWebDesign
Copy link

Directorist version

Version 8.0.8

Environment

PHP version: 8.1.30

Bricks Builder Theme

Pricing Plans Addon

Description

When a user creates a listing in our case a free listing, this works as expected.
The user however is able to go into their frontend dashboard and select the "Change Plan" option. They are presented with the pricing plans available and can continue. If they select a plan (say it costs 9.99) and click continue they are then redirected to the order confirmation/Checkout page. This is all correct so far but if the user decides to change their mind at this point and select the "Not Now" button and go back to the dashboard and the selected plan costing 9.99 that you haven't completed a checkout for is now applied to the listing?

Steps to reproduce

When a user creates a listing in our case a free listing, this works as expected.
The user however is able to go into their frontend dashboard and select the "Change Plan" option. They are presented with the pricing plans available and can continue. If they select a plan (say it costs 9.99) and click continue they are then redirected to the order confirmation/Checkout page. This is all correct so far but if the user decides to change their mind at this point and select the "Not Now" button and go back to the dashboard and the selected plan costing 9.99 that you haven't completed a checkout for is now applied to the listing?

Isolating the problem

  • I have reproduced this bug in localhost.
  • This bug happens with a default WordPress theme active (eg. 2021, 2022 etc).
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

1 participant