• Resolved Sayontan Sinha

    (@sayontan)


    Hello,
    Thank you for this plugin. I had been using the Classic Editor plugin all these days, but I decided to give this a spin recently and I really like what I am seeing.

    I do believe I have hit a hiccup, however. Here is my scenario:

    1. I have 4 pages on my site where I use blocks. Nothing else uses blocks.
    2. In the plugin options I have put the 4 page ids under the “Whitelist Post IDs” setting. This enables Gutenberg for those posts (pages, actually), but keeps it disabled for everything else. So far, so good.
    3. Unfortunately though, when I go to the front-end, the block library CSS file doesn’t load for those. If I go to the settings again and select “Enable Frontend” the CSS shows up, but on all the pages. So I am stuck either loading the CSS on all pages in the front-end, or having the front-end not render correctly.

    Ideally I would have expected the CSS (if disabled) to show up only for the whitelisted options, but that doesn’t seem to be the case. Is there something I am missing here?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jeff Starr

    (@specialk)

    Hi Sayontan, thanks for reporting this. It sounds like a bug, so definitely will investigate and try to resolve for the next plugin update. Let me know if you discover any further related infos, thank you.

    Thread Starter Sayontan Sinha

    (@sayontan)

    Thank you.

    For now I have addressed this by plugging in a few lines of code in my child theme to enqueue the scripts on the front-end for those page ids, but once you can confirm that you have made the fix here I will pull out my change.

    Plugin Author Jeff Starr

    (@specialk)

    Just to follow up, this issue is resolved in the next plugin update (due out later today). As of version 1.8 block styles are not disabled on whitelisted posts/pages.

    Thread Starter Sayontan Sinha

    (@sayontan)

    Thanks – this does seem to be working as expected!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Enable Frontend + Whitelist’ is closed to new replies.