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

LifterLMS Block Enrollment Visibility does not save with the Pricing table (access plans) llms block #46

Open
eri-trabiccolo opened this issue Apr 21, 2020 · 10 comments
Labels

Comments

@eri-trabiccolo
Copy link
Contributor

1. Reproduction Steps

  • Edit a course
  • Make sure there's the pricing table block
  • Set its Enrollment Visibility to whatever different from the default one.
  • switch from visual to code editor to check that the change actually "made" something
  • Click on the Update button
  • wait for the page to be fully reloaded
  • Check the block's Enrollment Visibility

2. Expected Behavior

  • I would expect the new Enrollment Visibility setting applied

3. Actual Behavior

  • The new Enrollment Visibility setting isn't applied

4. Error Messages / Logs

  • n/a

5. System Report

LifterLMS: 3.37.19

6. Browser, Device, and Operating System

n/a

Reported on wp.org

https://wordpress.org/support/topic/enrollment-visibility-for-lifterlms-pricing-table-display-to-everyone/

@eri-trabiccolo eri-trabiccolo added the Type: Bug Bugs and errors label Apr 21, 2020
@thomasplevy

This comment has been minimized.

@eri-trabiccolo

This comment has been minimized.

@eri-trabiccolo eri-trabiccolo changed the title LifterLMS Block Enrollment Visibility does not save with Atomic Blocks or Vdo Cipher LifterLMS Block Enrollment Visibility does not save with the Pricing table (access plans) llms block Apr 21, 2020
@toyinogun
Copy link

Also seeing the issue here: HS-136616

@toyinogun
Copy link

Similar issue: HS-159852

@eri-trabiccolo
Copy link
Contributor Author

Interesting... looks like there's a workaround to avoid this. If you switch to the "Code editor" before saving (so this means that you need to do the same every time you save) the issue doesn't occur.
@toyinogunseinde this is not ideal of course but maybe you want to inform the customer anyways (after having verified the workaround works for you too).

@toyinogun

This comment has been minimized.

@thomasplevy

This comment has been minimized.

@eri-trabiccolo

This comment has been minimized.

@toyinogun

This comment has been minimized.

@thomasplevy
Copy link
Contributor

Reopening, I'm pretty sure @toyinogunseinde is talking about a different issue than the one initially reported by @eri-trabiccolo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Awaiting Triage
Development

No branches or pull requests

3 participants