Support » Plugin: All in One SEO » wplink scripts related errors

  • ResolvedModerator Bet Hannon

    (@bethannon1)


    Support Team Volunteer Coordinator

    After updating to WP 5.4 on April 1, we noticed some client sites were throwing an error in the page/post block editor. The error is that when using Gutenberg, trying to open a new paragraph block results in an error message: “This block has encountered an error and cannot be previewed.” Other blocks seem to be okay.

    After much testing, we determined that this was only happening on our sites running AIOSEO and Toolset Types. We submitted a support ticket with Types, and their dev team was able to tell us:

    This issue is caused by the All In One SEO Pack Plugin which deregisters the wplink scripts. These are native WordPress Core scripts that are often used by other software to add or manipulate the editor experience.

    This means, any plugin relying on the script will fail to function if All In One SEO Pack is active.

    Is this something that you have made a development choice about, or an error? Will it be something that you are fixing?

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Support arnaudbroes

    (@arnaudbroes)

    Hey @bethannon1,

    Thank you for reporting this.

    I’ve reached out to Toolset Types so we can get a version of their plugin and investigate this issue on our end. In either case, this is definitely something we want to fix.

    In the latest update we added some extra features to the link format in Gutenberg. In order to achieve this, we had to deregister the core script and reregister it along with our modifications. There currently isn’t an API for this.

    I’m going to see if we can fix the conflict by reregistering the format with the same name, or else we’ll need to prevent our code from running if we detect that plugin.

    – Arnaud

    Moderator Bet Hannon

    (@bethannon1)

    Support Team Volunteer Coordinator

    This will be a problem for any plugin that depends on those core scripts, not just Toolset. Wouldn’t it be better not to deregister core scripts?

    SuperStu

    (@omgstu)

    The same issue for me, see the link to related support ticket with Toolset team
    https://toolset.com/forums/topic/all-in-one-seo-and-toolset-confilct/#post-1583963

    Thanks

    Plugin Support arnaudbroes

    (@arnaudbroes)

    @bethannon1 I think we can fix any conflicts by simply re-registering the format under the same name (core/link), but we first need to get our hands on a copy of their plugin so we can confirm whether or not that actually fixes it.

    SuperStu

    (@omgstu)

    @bethannon1 I can give you access to a test site if you wish to test…

    Beda

    (@bedas)

    Hi @arnaudbroes, I work with Toolset Support

    You could reach me at the email composed of my username beda.s (@) our domain onthegosystems.com

    Or, if you have an email I can reach you, in order to collaborate on the issue’s resolution, please let me know!

    Thanks!

    Plugin Support arnaudbroes

    (@arnaudbroes)

    @bethannon1 @omgstu thank you both for your co-operation.

    I’ve been able to reproduce the issue and have confirmed that we already have a fix for this in our upcoming release, which will be out soon. If you’d like for me to send you a beta version, then please contact me via Slack or contact us here and ask for me specifically.

    @bedas thank you for reaching out, we’re all good for now! 🙂

    Beda

    (@bedas)

    Great, thank you @arnaudbroes, we’ll update all the tickets in our Forum so the users know.

    Thanks again!

    CoreyFF

    (@coreyff)

    @arnaudbroes I’m having the exact same issue and would love to try out the beta, but don’t have a license for support (using the free version). Would you mind emailing me a copy to test out?

    Plugin Support wpsmort

    (@wpsmort)

    @coreyff Please contact us here to get a copy – https://semperplugins.com/contact/

    Choose Plugin Support and paste the URL of this forum thread in the License Key field.

    CoreyFF

    (@coreyff)

    @wpsmort Thanks so much. Will do!

    Plugin Support wpsmort

    (@wpsmort)

    @coreyff I responded to your email but got a delivery failure back from your email server.

    CoreyFF

    (@coreyff)

    @wpsmort Hmm I’m receiving other emails fine. Maybe I typed it wrong? It should be corey at facefirstcreative.com or you could try coreypaige at gmail.com

    I appreciate it!

    Plugin Support wpsmort

    (@wpsmort)

    @coreyff I’ve sent it to both accounts. It’s a ZIP file so I wonder if that’s the problem, I know that Google blocks ZIP file attachments.

    CoreyFF

    (@coreyff)

    @wpsmort Perfect, thanks. This one came through. I’ll let you know how it works for me as soon as possible.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘wplink scripts related errors’ is closed to new replies.