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

Premium Content: Block cannot be inserted on Atomic sites when Gutenberg Plugin is deactivated #44160

Closed
kwight opened this issue Jul 14, 2020 · 2 comments · Fixed by #44191
Closed
Assignees
Labels
Premium Content Controlling specific content for paying site visitors. [Pri] High Address as soon as possible after BLOCKER issues [Type] Bug When a feature is broken and / or not performing as intended

Comments

@kwight
Copy link
Contributor

kwight commented Jul 14, 2020

I tried to add a Premium Content block on an Atomic site, and it immediately errors.

Screen Shot 2020-07-14 at 3 38 20 PM

Errors are:

  • The block "premium-content/buttons" must have a registered category.
  • The block "premium-content/login-button" must have a registered category.
  • TypeError: Cannot read property 'attributes' of undefined

See: pbAok1-1ez-p2

@kwight kwight added Atomic Premium Content Controlling specific content for paying site visitors. [Type] Bug When a feature is broken and / or not performing as intended labels Jul 14, 2020
@gwwar gwwar added the [Pri] High Address as soon as possible after BLOCKER issues label Jul 14, 2020
@kwight kwight self-assigned this Jul 15, 2020
@gwwar
Copy link
Contributor

gwwar commented Jul 15, 2020

This might be a testing setup error on our side.

@gwwar gwwar changed the title Premium Content: Block cannot be inserted on Atomic sites. Premium Content: Block cannot be inserted on Atomic sites when Gutenberg Plugin is deactivated Jul 15, 2020
@gwwar
Copy link
Contributor

gwwar commented Jul 15, 2020

  • Premium Content works well with Gutenberg 8.3.0.
  • With Gutenberg Disabled, we get block insertion errors (for buttons and the main block).

Screen Shot 2020-07-15 at 2 28 37 PM

- With Gutenberg latest (8.5.1) we see the following errors in published view:

screen_shot_2020-07-15_at_2 01 13_pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Premium Content Controlling specific content for paying site visitors. [Pri] High Address as soon as possible after BLOCKER issues [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
2 participants