• Resolved danidada

    (@danidada)


    Hello! I’m back again!

    This time I don’t know if it’s just a setting but if I have this plugin active the custom field Editor WYSIWYG doesn’t appear in “Visual Editor” mode but only on “Text” mode.
    If I switch between the two tabs Visual/Text then the console shows this error: “Uncaught TypeError: can’t access property “setBaseAndExtent”, n is null”

    If I disable Premium blocks for gutenberg the content shows up correctly in both mode.
    Let me know if I can give you more details: there are no other plugins (only Yoast, SCF and your plugin) on an FSE enabled template. All up to date.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello and welcome back!

    First of all, we apologize for the inconvenience you’re experiencing. Thank you for your detailed report and for keeping everything updated—it’s greatly appreciated.

    To help us investigate this further, could you please provide the exact steps you follow to encounter the issue? Specifically which specific FSE theme, blocks, or settings are you using when the issue occurs?

    Thank you again for your cooperation. We’re committed to resolving this as quickly as possible, and your input is invaluable.

    Best regards

    Thread Starter danidada

    (@danidada)

    Sure!

    I have added unuseful details probably cause I think it’s not related to the theme but it’s between the SFC (https://it.ww.wp.xz.cn/plugins/secure-custom-fields/) plugin, when on a page there is a field type Editor WYSIWYG (attached photo) and the plugin Premium Blocks for Gutenberg is active (without placing any blocks and enable/disable settings doesn’t make any difference) than in the page editor that field type is not editable in Visual mode but only on Text mode. If you edit it on Text mode and than switch back to Visual mode it’s white empty and the console shows that error.

    Attached screenshots, hope this helps.

    Hello,
    Thank you for your detailed feedback and patience.

    After Investigation, The issue persists in Firefox even with Premium Blocks deactivated, but not in Chrome when it’s active. This points to the core WordPress issue.

    Could you confirm if you’re using Firefox or a different browser?
    Our team is investigating this further and we’ll keep you updated.

    Best regards

    Thread Starter danidada

    (@danidada)

    Hello again,

    thanks for the update. I’m on Firefox and it works deactivating Premium Blocks.
    I checked the issue you have linked and from what users says could be related to a delay (https://core.trac.ww.wp.xz.cn/ticket/62450#comment:6) maybe just due to the resources loaded by the plugin and not a specific conflict.

    And from what I read I could try to rollback wp version at 6.6.2 but before doing that I’ll wait if you or the guys on the issue thread reply.

    Thread Starter danidada

    (@danidada)

    I found a workaround that fix the problem:

    enabling the delay initialization and forcing visual mode only it loads it as code and on click inside the area display it properly with editing fully working.

    Sorry to have open this as a conflict of Premium Blocks plugin when it was not the culprit because it’s a wp bug.

    ps. can I ask something that’s not related to this issue? For the Icon Block can the standard icons be replaced with a filter to load only custom icons?

    • This reply was modified 7 months, 1 week ago by danidada.

    Thanks for your feedback and sharing your workaround.

    Currently, filtering or fully replacing standard icons (Dashicons / Fontawesome Icons) with custom ones isn’t available. You can disable FontAwesome icons from the dashboard settings. For custom icons, the current workaround is to manually upload SVGs or images in each Icon Block.

    We appreciate your suggestion and will brainstorm internally about improving custom icon flexibility in future updates.

    Let us know if you have any other questions or ideas!

    Thread Starter danidada

    (@danidada)

    Thanks, I think it’s a feature a user wouldn’t care for, but for a developer like me who designs a custom theme with customized styling letting who’ll manage the website be able to select only the “brand icons” would be a plus. But, anyway, I like to use your plugin because it’s light, doesn’t add too much (like templates, patterns…) and has some really nice features so… thumps up! Also, I appreciate the fast and full support.

    Thank you for your feedback and kind words!

    We appreciate your perspective as a developer working on custom themes, and your suggestion about brand icon selection is very helpful. We’re glad you enjoy the plugin’s lightweight approach and will keep your idea in mind for future updates.

    We’d also be truly grateful if you could please do us a BIG favor by rating Premium Blocks for Gutenberg, as your feedback truly makes a difference.

    If you have any further questions, feel free to reach out!

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

The topic ‘Conflict with SCF plugin’ is closed to new replies.