The latest update causes bugs,

  • All is fine with WP 5.4.x. However, when using with WP 5.5 beta3, many of my custom ACF Pro blocks (I have not tested with other block libraries including the core bocks), the blocks display an error message instead:

    “This block has encountered an error and cannot be previewed”.

    By deactivating this plugin, everything works as they should again. Again, this issue happens with WP 5.5 beta3, and not with WP 5.4. Also with beta 3, activating the Gutenberg block does not fix the issue, btw…

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author nK

    (@nko)

    Hey.

    I don’t see any conflict with ACF Pro blocks. AWB plugin will be updated in 1 day, please, re-check it.

    If the problem will still remain, I will need to get a step-by-step guide from you, how can I reproduce this bug locally.

    Regards, nK.

    Thread Starter nick6352683

    (@nick6352683)

    I’ll check again tomorrow, as WP 5.5 will be released. You incorrectly suggested that AWB has ACF Pro issues. The fact is that WP 5.5 betaxxx causes AWB to corrupt ACF Pro blocks.

    I’ll have more one way or another when WP 5.5 is out… BTW, you guys have to study and learn how Getwid successfully incorporates sound with background videos…

    Hi there,

    I can report one issue with WP 5.5, too, sadly.

    With AWB switched active, I can’t edit with the text editor from WP Bakery anymore. The WPBakery editor field

    <textarea class="wpb-textarea visual_composer_tinymce content textarea_html wp-editor-area" rows="20" autocomplete="off" cols="40" name="wpb_tinymce_content" id="wpb_tinymce_content" aria-hidden="false"></textarea>

    just displays nothing, no contents.

    With the browser inspector, unter the tab ‘console’, one JS error is reported:

    Uncaught ReferenceError: wpColorPickerL10n is not defined
    _create ... /wp-content/plugins/advanced-backgrounds/assets/vendor/wp-color-picker-alpha/wp-color-picker-alpha.min.js?ver=2.0.0:11
    e Backbone

    When switching the editor tabs “visual” and “text”, another JS error is reported for TinyMCE and the admin editor JS:

    Uncaught TypeError: r is undefined
    e ... /wp-includes/js/tinymce/tinymce.min.js?ver=49100-20200624:2
    r ... /wp-admin/js/editor.min.js?ver=5.5:2

    Even though I can insert content to the white editor field, it is (luckily) NOT saved when clicking ‘Save’.

    ==> With AWB switched off, everything works fine.

    My quick workaround: when editing contents, I switch off AWB and switch in on again when I’m finished.

    Any help/information is greatly apprechiated!

    Cheers,
    Johannes

    • This reply was modified 4 years, 3 months ago by jbt-csm.

    @jbt-csm

    I am also having a similar issue with saving content while AWB is activated, im currently using the same workaround as you to allow me to save content. I am using the Page Builder by SiteOrigin plugin to make my content and while AWB is activated, any of the widget content cannot be saved (updated) in the post. Hopefully this can be resolved as well.

    Edit: I am also getting the exact same console error as @jbt-csm as well. Hopefully this helps narrow down a fix in that area.

    Great plugin by the way @nko, makes my hope page pretty slick.

    • This reply was modified 4 years, 3 months ago by tartemenko.
    • This reply was modified 4 years, 3 months ago by tartemenko.
    Plugin Author nK

    (@nko)

    Hey @nick6352683 @jbt-csm @tartemenko

    Could you try the latest plugin update v1.6.7?

    There was a conflict in the Color Picker script in WPBakery shortcode and WP 5.5.

    Regards, nK.

    @nk and ALL:

    I can confirm that this conflict was successfully solved by the master! ??

    Thank you very kindly! That was really quick!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘The latest update causes bugs,’ is closed to new replies.