• Resolved luminsol

    (@luminsol)


    Hi,

    Running WordPress 5.6 and Notifications 7.1.1

    All the notifications are working as per normal.

    However, I get the following error/warnings:

    Debug log is active and no notifications will be sent.

    I have debugging off and notifications are being sent.

    Failed to load plugin url: https://example.com/wp-includes/js/tinymce/

    The above is displayed when editing a notification. Editing is not affected. The developer console error shows:

    The resource from “https://example.com/wp-includes/js/tinymce/?wp-mce-49110-20201110” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff)

    Please let me know if you need any more information to debug.

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

    (@kubitomakita)

    Hi @luminsol

    thanks for the notice!

    The “Debug log is active and no notifications will be sent.” is comming from the plugin when you have the logging enabled in Notification -> Settings -> Debugging. Can you confirm you have it?

    The TinyMCE issue is something we’ve been chasing for a while now. Are you able to provide the list of plugins you are using? You can grab this in Tools -> Health Check and send the report to support@bracketspace.com

    Thread Starter luminsol

    (@luminsol)

    I don’t have logging enabled, both are unchecked. Also, notifications are correctly being sent.

    When I try to re-save the settings, I see that the checkbox for “error logging” briefly being checked before becoming unchecked.

    Plugins installed:

    Apollo13 Framework Extensions Version 1.8.7 by Apollo13Themes | Auto-updates disabled
    Contact Form 7 Version 5.3.2 by Takayuki Miyoshi | Auto-updates disabled
    Contact Form 7 Conditional Fields Version 1.9.14 by Jules Colle | Auto-updates disabled
    Elementor Version 3.0.15 by Elementor.com | Auto-updates disabled
    Email Address Encoder Version 1.0.22 by Till Krüss | Auto-updates enabled
    Flamingo Version 2.2.1 by Takayuki Miyoshi | Auto-updates disabled
    Google Analytics for WordPress by MonsterInsights Version 7.14.0 by MonsterInsights | Auto-updates enabled
    LiteSpeed Cache Version 3.6.1 by LiteSpeed Technologies | Auto-updates disabled
    Notification Version 7.1.1 by BracketSpace | Auto-updates disabled
    Redirection Version 4.9.2 by John Godley | Auto-updates disabled
    Redux Version 4.1.24 by Redux.io + Dovy Paukstys | Auto-updates disabled
    Rife Elementor Extensions & Templates Version 1.1.5 by Apollo13Themes | Auto-updates disabled
    Simple Calendar Version 3.1.33 by Simple Calendar | Auto-updates disabled
    Widget Options Version 3.7.6 by Widget Options Team | Auto-updates enabled
    WooCommerce Version 4.8.0 by Automattic | Auto-updates disabled
    WP Cerber Security, Anti-spam & Malware Scan Version 8.7 by Cerber Tech Inc. | Auto-updates disabled
    WP Crontrol Version 1.8.5 by John Blackbourn & crontributors | Auto-updates enabled
    Yoast SEO Version 15.5 by Team Yoast | Auto-updates enabled

    Plugin Author Kuba Mikita

    (@kubitomakita)

    I noticed LiteSpeed Cache plugin. Can you please try to purge the caching? The plugin settings laverage object caching.

    I’m going to replicate your environment and see if I can reproduce the TinyMCE issue, so thanks for the plugin list!

    Thread Starter luminsol

    (@luminsol)

    Purging the cache doesn’t solve the debug log message. Object caching was not being used.

    I have another local test copy of the site without LiteSpeed Cache and there is no debug log warning or the TinyMCE error, so it’s probably some incompatibilities with LiteSpeed Cache.

    Plugin Author Kuba Mikita

    (@kubitomakita)

    Hey @luminsol I managed to resolve both issues!

    I plan to release new version with patches today or this weekend.

    Quick fix for the notice in admin – Go to Debugging settings and uncheck both Debug log and Suppressing checkboxes. There was a glitch when Suppressing was checked and Debug log was not, the notice was displayed.

    Thread Starter luminsol

    (@luminsol)

    All fixed, many thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error messages in 7.1.1’ is closed to new replies.