Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter coleclark

    (@coleclark)

    @ryankienstra Haha, no problem at all 🙂

    I’ve tested on Chrome 80.0.3987.132, and Firefox 73.0.1, on MacOS Mojave (10.14.6).

    Thread Starter coleclark

    (@coleclark)

    @ryankienstra

    Thanks for looking in to this, and for all the info, I really appreciate it.

    1. What type of field is a content field? I looked it up in the Block Labs “All Blocks” tab, found the “WYSIWYG” block, clicked Edit, and apparently the Content block is a “Classic Text” block. I tried changing it to a few other types (Text, TextArea, RichText) but the error still appeared.

    2. Thanks for the link to that bug report, I think it may be the source of our problem. At the very least, if we can’t figure it out it gives me something to point to and say “Wait for a WP update.”

    3. Thanks for the new build! I tried it on our staging server, and unfortunately got the same result as my last update from yesterday. If you’re curious, here’s the error (same as before) captured straight from Dev Tools: https://snipboard.io/TSikMm.jpg

    Unless you can think of something else (I can’t), I think that’s about as far as we can go. Thanks again, Ryan, and if it resolves itself following a WP or BL update, I’ll let you know!

    Best regards,
    Henry

    Thread Starter coleclark

    (@coleclark)

    Just tried updating the plugin. The editor page is now blank except for the headline, and got this error in the console:
    Uncaught TypeError: Cannot set property ServerSideRender of #<Object> which has only a getter with this set of paths:

    at Module.<anonymous> (editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:2043)
    at n (editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:11)
    at editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:71
    at editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:72
    (anonymous) @ editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:2043
    n @ editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:11
    (anonymous) @ editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:71
    (anonymous) @ editor.blocks.js?ver=576e828a2b0106d7910c36aaa487e44c:formatted:72

    The plugin update doesn’t work for us at all, so we’ll be rolling it back to 1.5.0.
    FWIW I believe we’re on WP 5.3.1, though WordPress makes that difficult to determine.

    Thread Starter coleclark

    (@coleclark)

    Hi @ryankienstra, thanks for getting back to me.

    1. Here’s a screenshot of the block editing screen showing the error: https://snipboard.io/EmyhbB.jpg
    2. Here’s a screenshot of the block editor for the individual block, where you can see the offending word (“Subscription”): https://snipboard.io/8TUgQM.jpg
    3. And here is a preview of the page, as you can see it doesn’t appear to block publication of the text: https://snipboard.io/Lfpr9U.jpg
    4. Finally, here’s a pastebin of the theme block template for the block that’s showing the error (may not be useful, but for completeness): https://pastebin.com/HNiwaPyR

    I’ll try the upgrade as soon as I can and report back.

    No worries on any delay, I appreciate your attention. This is a weird one!

Viewing 4 replies - 1 through 4 (of 4 total)