• Wordpress Version: 5.7 (php 7.3)
    Kadence Blocks – PRO Extension: 1.4.29
    Kadence Blocks: 1.10.7

    Using custom post types with custom taxonomies (‘Content Type’, ‘Audience’, ‘Status’, ‘Topic’).

    Using the Post Grid/Carousel block in the editor:
    Select Posts Type: set to custom post type
    Above Title Taxonomy -> Yes
    Select Taxonomy -> ‘Content Type’

    Editor throws error:

    
    console.js:32 ReferenceError: taxSymbol is not defined
        at blocks.build.js?ver=1.4.29:formatted:69672
        at Array.map (<anonymous>)
        at Wa (blocks.build.js?ver=1.4.29:formatted:69663)
        at blocks.build.js?ver=1.4.29:formatted:70032
        at Array.map (<anonymous>)
        at t.value (blocks.build.js?ver=1.4.29:formatted:70031)
        at Ie (react-dom.min.js?ver=16.13.1:104)
        at rh (react-dom.min.js?ver=16.13.1:103)
        at zj (react-dom.min.js?ver=16.13.1:228)
        at Th (react-dom.min.js?ver=16.13.1:152)
        at tj (react-dom.min.js?ver=16.13.1:152)
        at Te (react-dom.min.js?ver=16.13.1:146)
        at react-dom.min.js?ver=16.13.1:61
        at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
        at Da (react-dom.min.js?ver=16.13.1:60)
        at Pg (react-dom.min.js?ver=16.13.1:61)
        at ha (react-dom.min.js?ver=16.13.1:60)
        at mk.Events.current (react-dom.min.js?ver=16.13.1:236)
        at Ei (react-dom.min.js?ver=16.13.1:41)

    The page actually renders in the preview, but the editor shows the ‘This block has encountered an error’ message and all of the block options disappear.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello,

    Thank you for reaching out and I apologize for the delay.

    I’m not able to replicate this issue currently. After the recent updates and clearing your cache are you still seeing this issue?

    Thanks!

    Chris

    Thread Starter lhmatt

    (@lhmatt)

    No worries! The site we were using it on was for a one-off event, which has now passed.

    We were unable to reproduce it on other installs with the latest updates (though other, different, plugins installed).

    I suspect it was caused by a plugin conflict, but as the code was minified I couldn’t debug it very easily. For future reference, are you able/willing to offer debug builds with unminified JS code?

    Thanks for posting I have found this issue and will have an update out soon.

    Ben

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Custom Post Type: ReferenceError: taxSymbol is not defined’ is closed to new replies.