• Resolved entertio

    (@entertio)


    When trying to replace images in Cover blocks while editing a re-usable block, WordPress spits out this error: “This block has encountered an error and cannot be previewed.”. When I check the console I get this Javascript error:

    “An error occurred while running ‘mapSelect’: Cannot read property ‘_cloudinary_featured_overwrite’ of undefined”

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter entertio

    (@entertio)

    I’ve traced the issue down to this line:

    
    overwrite_featured_transformations: null !== (r = e("core/editor").getEditedPostAttribute("meta")._cloudinary_featured_overwrite) && void 0 !== r && r
    

    and this mod seems to fix it:

    
    overwrite_featured_transformations: null !== (r = e("core/editor")?.getEditedPostAttribute("meta")?._cloudinary_featured_overwrite) && void 0 !== r && r
    

    Anyway we can get this patched soon?

    Hi @entertio ,

    Thank you for reaching out.

    I tried using the Cover block to publish a post and then edit it again. Do not see any see errors on the latest versions – WordPress 5.5.1 and Cloudinary 2.2.0.

    Would you be able to provide step by step instructions on how to reproduce the error?

    Additionally, please provide:
    1. WP and Cloudinary versions
    2. List of other plugins
    3. Themes you are using.
    4. Page builders.

    Once provided, I will take a deeper look into it on our end, trying to reproduce the issue and escalate this error internally as needed.

    In case it will be necessary, will you be willing to provide us with temporary access to a sandbox environment of your site where we can take a look and debug if needed?

    Best regards,
    Jay

    Thread Starter entertio

    (@entertio)

    Hey @jaycloudinary.

    We’re using:

    – WP v5.5
    – Cloudinary Plugin v2.2.0
    – Yoast v14.8.1
    – 2 Custom In-House Block Plugins
    – A Custom Sage Theme
    – No Page Builders

    Unfortunately I cannot provide a sandbox environment.

    Steps to Reproduce:

    1.) Visit your Gutenberg block management page. In my case since I’m using Sage it is: https://wordpress.local/wp/wp-admin/edit.php?post_type=wp_block

    2.) Create a new Cover block with an image.

    3.) Publish the block.

    4.) Refresh the page, and try to replace the image in the Cover block.

    5.) The block breaks and reports: “This block has encountered an error and cannot be previewed.” along with a JS console error: “An error occurred while running ‘mapSelect’: Cannot read property ‘_cloudinary_featured_overwrite’ of undefined

    Getting the same error BUT for me it is happens with custom post-types which have an editor – even a blank editor – and a featured image.

    Steps to rep A
    1. Open page to create new custom post type.
    2. Click a “Set Featured Image” button
    3. Click any image from library
    4. Click on “Set Featured Image” button in library modal
    5. Error: The editor has encountered an unexpected error.

    Steps to rep B
    1. Open page to edit a custom post type which has an editor and featured image
    2. Error: The editor has encountered an unexpected error.

    Removing “editor” from ‘supports’ when registering the custom post type solves the issue.

    Entertio’s solution also does it

    Hi @entertio ,

    Thank you for the information. Internal team is looking into this, I’ll update here when there is some more information on this.

    Best regards,
    Jay

    I am having the same issue as @pire with a custom post type.

    @pire @ajonp @entertio ,

    Team is working on the bug fix and will release a patch very soon.

    I’ll keep you posted here.

    Best regards,
    Jay

    Hi @pire @ajonp @entertio ,

    WordPress Hot-fix was released today in v2.2.1. This should take care of this issue.

    Best regards,
    Jay

    Thank you @jaycloudinary

    Can confirm the hotfix has solved the issue on my side.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Cannot read property ‘_cloudinary_featured_overwrite’ of undefined’ is closed to new replies.