Forum Replies Created

Viewing 15 replies - 1 through 15 (of 129 total)
  • Thread Starter Nico

    (@gooloode)

    Hi Daan, do you have an Update? πŸ™‚

    Thread Starter Nico

    (@gooloode)

    I use a custom PHP Snippet since i’m not paying money for hosting to get bombarded by plugin ads and notices that no one needs. πŸ˜€

    // ── Notices: PHP-Hooks entfernen (außer auf Divi-Seiten) ──────────────────
    add_action( 'admin_init', function() {
    // Divi-Seiten vollstΓ€ndig auslassen
    $screen = get_current_screen();
    if ( $screen ) {
    $is_divi = (
    $screen->post_type === 'et_pb_layout'
    || strpos( $screen->id, 'et_' ) !== false
    || strpos( $screen->id, 'divi' ) !== false
    );
    if ( $is_divi ) {
    return;
    }
    }

    // Alle Notice-Hooks entfernen – sicher, da wir hier NICHT auf Divi-Seiten sind
    remove_all_actions( 'admin_notices' );
    remove_all_actions( 'all_admin_notices' );
    remove_all_actions( 'network_admin_notices' );
    remove_all_actions( 'user_admin_notices' );
    }, 20 ); // PrioritΓ€t 20: nach Plugin-Registrierungen, vor der Ausgabe


    // ── CSS-Fallback: alle verbleibenden Notices auf ALLEN Seiten ausblenden ──
    // (außer Divi – doppelte Absicherung per Screen-Check)
    add_action( 'admin_head', function() {
    $screen = get_current_screen();
    if ( $screen ) {
    $is_divi = (
    $screen->post_type === 'et_pb_layout'
    || strpos( $screen->id, 'et_' ) !== false
    || strpos( $screen->id, 'divi' ) !== false
    );
    if ( $is_divi ) {
    return;
    }
    }

    echo '<style>
    /* Alle Standard-Notice-Klassen */
    .notice,
    .notice-warning,
    .notice-info,
    .notice-success,
    .notice-error,
    .notice.is-dismissible,
    .updated,
    .update-nag,
    div.error,
    div.updated,
    #message,
    .update-message,
    .updated-message,
    /* Plugin-spezifische Wrapper */
    .plugin-update-tr .update-message,
    /* Inline-Notices mancher Plugins */
    [class*="notice-"],
    [id*="-notice"],
    [id*="-message"] {
    display: none !important;
    }
    </style>';
    }, 9999 );


    // ── Admin-Footer-Text entfernen ────────────────────────────────────────────
    function remove_footer_admin() {
    return '';
    }
    add_filter( 'admin_footer_text', 'remove_footer_admin' );
    add_filter( 'update_footer', 'remove_footer_admin' );
    Thread Starter Nico

    (@gooloode)

    Hi, i used the ZIP you provided, but it still doesn’t find it:

    Thread Starter Nico

    (@gooloode)

    Okay, thank you! :))

    Thread Starter Nico

    (@gooloode)

    Yes, i’m hiding the Admin Bar with the White Label CMS Plugin (https://de.wordpress.org/plugins/white-label-cms/)

    I don’t see anything that appears to have “status” in the Network Tab. I only see fairly “normal” links to scripts, fonts, etc.

    Thread Starter Nico

    (@gooloode)

    Hi Daan, i actually don’t even know what that means. πŸ˜€ Here’s my browser console on the link i gave you in the first post:

    Thread Starter Nico

    (@gooloode)

    Hi, no OMGF hasn’t found it, so i think a Pro Upgrade will be necessary. I will contact WideAccess regarding this.

    Thread Starter Nico

    (@gooloode)

    Hi, i have temporarily disabled all features. πŸ™‚

    Thread Starter Nico

    (@gooloode)

    Hi,

    i’ve talked to my host and it is caused by BunnyCDN’s Optimizer. This affects not only this plugin, but also Complianz Cookies. Maybe you could work on an fix? Temporarily disabling it, purging the cache and then coming back to the edit page fixes the issue.

    Thread Starter Nico

    (@gooloode)

    I was not able to find a conflicting plugin or theme. Here’s my list of plugins:

    Plugin Name Version
    301 Redirects Pro 6.27
    Action Scheduler Daily Cleanup 1.0.0
    Advanced Editor Tools 5.9.2
    ALTCHA Spam Protection 1.26.3
    Auto Bluesky Poster 2.0
    Basic User Avatars 1.0.9
    Block List Updater 1.0.2
    Code Snippets 3.9.5
    Complianz | GDPR/CCPA Cookie Consent 7.4.4.2
    Delete Me 3.2
    Flying Scripts 1.2.4
    Forminator 1.50.3
    GDPR Data Request Form 1.7
    Glossary 2.3.10
    gooloo.de Review Bar Plugin Enhanced 4.0.14
    Helpful 1.14
    Hide Posts Toggle System 1.6.1
    Index WP MySQL For Speed 1.5.6
    Ivory Search 5.5.14
    Koko Analytics 2.2.1
    Leira Letter Avatar 1.3.13
    Lightweight Accordion 1.6.0
    LiteSpeed Cache 7.7
    Loco Translate 2.8.1
    MailPoet 5.21.1
    Nextend Social Login 3.1.22
    OMGF 6.1.1
    OneSignal Push Notifications 3.8.0
    Paid Memberships Pro 3.6.4
    Paid Memberships Pro - Add Name to Checkout 0.7.1
    Paid Memberships Pro - Add PayPal Express Add On 0.7.1
    Paid Memberships Pro - Email Confirmation Add On 0.8
    Paid Memberships Pro - Failed Payment Limit Add On .3
    Paid Memberships Pro - Social Login Add On 1.1
    Paid Memberships Pro - Update Manager 1.0.1
    Pods - Custom Content Types and Fields 3.3.4
    Post Feedback Collector 1.2.0
    Send Users Email 1.6.2
    Smart Slider 3 3.5.1.32
    SQLite Object Cache 1.6.1
    The SEO Framework 5.1.4
    The SEO Framework - Extension Manager 2.7.2
    White Label CMS 2.7.8
    WP-PageNavi 2.94.5
    WP-Sweep 1.1.8
    WP 2FA - Two-factor authentication for WordPress 3.1.0
    WP Auto Updater 1.7.3
    wpDiscuz 7.6.46
    WP Grid Builder 2.3.0
    WP Instant Indexing 1.3.3
    WP to Buffer 4.0.7
    Thread Starter Nico

    (@gooloode)

    And the following is with Script Debug:

    Uncaught ReferenceError: module is not defined
    at eval (runtime.js:4:3)
    at ./node_modules/react-refresh/runtime.js (react-refresh-runtime.js?ver=8f1acdfb845f670b0ef2:665:156)
    at t (react-refresh-runtime.js?ver=8f1acdfb845f670b0ef2:672:165)
    at react-refresh-runtime.js?ver=8f1acdfb845f670b0ef2:672:194
    at react-refresh-runtime.js?ver=8f1acdfb845f670b0ef2:672:269Fehler nachvollziehen
    ReactRefreshEntry.js:4 Uncaught ReferenceError: webpack_require is not defined
    at eval (ReactRefreshEntry.js:4:20)
    at ./node_modules/@pmmmwh/react-refresh-webpack-plugin/client/ReactRefreshEntry.js (react-refresh-entry.js?ver=a100113810d2b7fe3a75:117:139)
    at e (react-refresh-entry.js?ver=a100113810d2b7fe3a75:983:255)
    at react-refresh-entry.js?ver=a100113810d2b7fe3a75:983:470
    at react-refresh-entry.js?ver=a100113810d2b7fe3a75:983:556Fehler nachvollziehen
    react-dom.js?ver=18.3.1.1:122 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
    jsx-runtime.js:4 Uncaught ReferenceError: module is not defined
    at eval (jsx-runtime.js:4:3)
    at ./node_modules/react/jsx-runtime.js (react-jsx-runtime.js?ver=18.3.1:1342:140)
    at t (react-jsx-runtime.js?ver=18.3.1:1349:188)
    at react-jsx-runtime.js?ver=18.3.1:1349:217
    at react-jsx-runtime.js?ver=18.3.1:1349:284Fehler nachvollziehen
    components.js?ver=316cf67f025fcb3e30cc:38 Uncaught TypeError: Cannot read properties of undefined (reading 'jsx')
    at components.js?ver=316cf67f025fcb3e30cc:38:114767
    at components.js?ver=316cf67f025fcb3e30cc:186:85496
    at components.js?ver=316cf67f025fcb3e30cc:186:85539Fehler nachvollziehen
    commands.js?ver=dc36b1bd84586300bf60:45 Uncaught TypeError: Cannot read properties of undefined (reading 'jsx')
    at commands.js?ver=dc36b1bd84586300bf60:45:11996
    at commands.js?ver=dc36b1bd84586300bf60:45:19030Fehler nachvollziehen
    preferences.js?ver=82e07780e2bc6c33ac54:1 Uncaught TypeError: Cannot read properties of undefined (reading 'jsx')
    at preferences.js?ver=82e07780e2bc6c33ac54:1:806
    at preferences.js?ver=82e07780e2bc6c33ac54:1:7046Fehler nachvollziehen
    wp-preferences-js-after:2633 Uncaught TypeError: Cannot read properties of undefined (reading 'store')
    at wp-preferences-js-after:6:43
    at wp-preferences-js-after:8:8Fehler nachvollziehen
    block-editor.js?ver=eae9c1c1fdbcd744c9d5:32 Uncaught TypeError: Cannot read properties of undefined (reading 'jsx')
    at block-editor.js?ver=eae9c1c1fdbcd744c9d5:32:57421
    at block-editor.js?ver=eae9c1c1fdbcd744c9d5:251:6659
    at block-editor.js?ver=eae9c1c1fdbcd744c9d5:251:6703Fehler nachvollziehen
    core-commands.js?ver=2aa6475e85b024c6a8d7:1 Uncaught TypeError: Cannot read properties of undefined (reading 'jsx')
    at core-commands.js?ver=2aa6475e85b024c6a8d7:1:608
    at core-commands.js?ver=2aa6475e85b024c6a8d7:1:10644Fehler nachvollziehen
    wp-core-commands-js-after:2669 Uncaught TypeError: Cannot read properties of undefined (reading 'initializeCommandPalette')
    at wp-core-commands-js-after:2:17Fehler nachvollziehen
    form-scripts.js?ver=1.50.3:21 Uncaught TypeError: Object prototype may only be an Object or null: undefined
    at Object.setPrototypeOf ()
    at new e (form-scripts.js?ver=1.50.3:21:22730)
    at r (form-scripts.js?ver=1.50.3:21:23779)
    at middleware (form-scripts.js?ver=1.50.3:411:28911)
    at G4 (form-scripts.js?ver=1.50.3:21:24039)
    at form-scripts.js?ver=1.50.3:411:28882
    at form-scripts.js?ver=1.50.3:411:28934
    at form-scripts.js?ver=1.50.3:411:29380
    at form-scripts.js?ver=1.50.3:411:29383Fehler nachvollziehen
    index.global.js:231 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
    index.global.js:232 URL
    index.global.js:232 URL
    index.global.js:232 URL
    remote:1 Failed to load resource: the server responded with a status of 404 ()Fehler nachvollziehen
    jquery-migrate.js?ver=3.4.1:4 JQMIGRATE: Migrate is installed with logging active, version 3.4.1
    remote:608 Uncaught SyntaxError: Unexpected token '='Fehler nachvollziehen
    OneSignalSDK.page.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTFehler nachvollziehen
    jquery-migrate.js?ver=3.4.1:4 JQMIGRATE: jQuery.fn.keyup() event shorthand is deprecated
    n @ jquery-migrate.js?ver=3.4.1:4Diese Warnung nachvollziehen
    jquery-migrate.js?ver=3.4.1:4 console.trace
    n @ jquery-migrate.js?ver=3.4.1:4
    t. @ jquery-migrate.js?ver=3.4.1:4
    (anonym) @ ivory-search.min.js?ver=5.5.14:1
    (anonym) @ ivory-search.min.js?ver=5.5.14:1
    jquery-migrate.js?ver=3.4.1:4 JQMIGRATE: jQuery.fn.click() event shorthand is deprecated
    n @ jquery-migrate.js?ver=3.4.1:4Diese Warnung nachvollziehen
    jquery-migrate.js?ver=3.4.1:4 console.trace
    n @ jquery-migrate.js?ver=3.4.1:4
    t. @ jquery-migrate.js?ver=3.4.1:4
    (anonym) @ ivory-search.min.js?ver=5.5.14:1
    (anonym) @ ivory-search.min.js?ver=5.5.14:1
    complianz.js?ver=1767615021:2 opt-in
    jquery-migrate.js?ver=3.4.1:4 JQMIGRATE: jQuery.fn.resize() event shorthand is deprecated
    n @ jquery-migrate.js?ver=3.4.1:4Diese Warnung nachvollziehen
    jquery-migrate.js?ver=3.4.1:4 console.trace
    n @ jquery-migrate.js?ver=3.4.1:4
    t. @ jquery-migrate.js?ver=3.4.1:4
    (anonym) @ ivory-search.min.js?ver=5.5.14:1
    dispatch @ jquery.js?ver=3.7.1:11
    f.handle @ jquery.js?ver=3.7.1:11
    remote:2413 [LiteSpeed] Start Lazy Load
    Thread Starter Nico

    (@gooloode)

    Hi, the following errors appear:

    Thread Starter Nico

    (@gooloode)

    I found a fix:

    Go to wp-config.php and remove the “//WP Safe Mode” Line. Move all files from /wp-content/wp-safe-mode/ (except for the WP Safe Mode Files) directly to /wp-content/mu-plugins. Afterwards, delete the “wp-safe-mode” folder entirely. Now everything works again as usual and plugins are loaded from /wp-content/mu-plugins directly, instead of the WP Safe Mode Folder.

    Maybe this should be fixed in the future.

    Thread Starter Nico

    (@gooloode)

    Here’s a message from the FDP Developer:

    wp_delete_file( WPMU_PLUGIN_DIR . ‘/eos-deactivate-plugins.php’ );

    It uses the WordPress core function wp_delete_file and the WordPress constant WPMU_PLUGIN_DIR, without hardcoding the folder name.Because of this, the conflict with WP Safe Mode can’t be solved by FDP. It has to be addressed by the authors of WP Safe Mode.

    There is no way for FDP to know that WP Safe Mode changes the folder name and doesn’t use WordPress standards to reference the new mu-plugins directory.

    I also believe WP Safe Mode can cause conflicts with many other plugins that use the mu-plugins folder.

    URL: https://wordpress.org/support/topic/mu-plugin-isnt-deleted/#post-18792588

    Thread Starter Nico

    (@gooloode)

    Hi Jose, i used this in the past, but it’s removed. My hoster found the file and now removed it for me; it was actually saved in /wp-safe-mode/. Now everything is “clean” again. I will contact the WP Safe Mode Devs why the folder still exists. Thank you so much for your help!

    Oh, and yes, i would probably benefit from it, but i’m on BunnyCDN with all premium features through my hoster, so i’m not that concerned about speed, as i’m happy with them. For me personally, your plugin is too complex as a starter, so i will keep it “as-is” for now. πŸ™‚

Viewing 15 replies - 1 through 15 (of 129 total)