• I disabled almost all plugins, but nothing changed.

    Here is how it looks …

    What is wrong?

    This is WP 6.3 with TwentyTwentyThree 1.2 (today actualized)

    PS: The Website condition report looks good. The site produces no errors.

    • This topic was modified 1 year, 7 months ago by Frank Spade.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Caio Ferreira

    (@caiohferreiradev)

    Hi Frank Spade,

    It’s unfortunate that you’re facing issues with the website editor. It’s essential to have a working editor to make changes to your site seamlessly. Given the details you’ve provided, here’s a structured approach to diagnose and hopefully fix the issue:

    1. Theme Issue: Even though you’ve updated to TwentyTwentyThree 1.2, there’s still a possibility that the theme might have a conflict with WP 6.3. As a test, switch to a previous default theme (like TwentyTwentyTwo or TwentyTwentyOne) and see if the editor loads properly. If it does, the issue might be with the theme itself.
    2. JavaScript Console Errors: Sometimes, the issue is related to JavaScript. Open your browser’s developer tools (usually F12 or right-click on the page and select “Inspect”), switch to the ‘Console’ tab, and check for any errors. These errors can provide clues about what’s causing the issue.
    3. Script Minification/Concatenation: If you’re using any caching or optimization plugins that minify or concatenate JavaScript or CSS files, try clearing the cache or temporarily deactivating them. Sometimes, minification or concatenation can cause conflicts, especially after updates.
    4. Browser Cache and Cookies: Clear your browser cache and cookies. Old cached data might interfere with the latest updates.
    5. Test in a Different Browser: There’s a chance it might be a browser-specific issue. Test the editor in another browser to see if it loads correctly.
    6. Server-side Cache: Some hosting providers have server-side caching in place. It might be a good idea to clear that cache (if applicable). Check your hosting panel or contact your hosting provider for guidance.
    7. PHP Version: Ensure you’re running a recommended PHP version for WP 6.3. Typically, a newer version of PHP (e.g., 7.4 or 8.x) offers better performance and compatibility.
    8. Rest API Issue: WordPress editor often communicates with the server using the REST API. If there’s an issue or blockage (e.g., from security plugins) with the REST API, it might affect the editor’s functionality. You can use plugins like “REST API Log” to diagnose any issues.
    9. Manual Debugging: As a more technical step, you can enable WordPress debugging by adding the following lines to your wp-config.php:
    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);
    1. After adding these, check your site and then look for a debug.log file within the wp-content directory. This file can provide more detailed information on any errors.
    2. Seek Expert Help: If all else fails and the issue persists, it might be a good idea to contact a WordPress expert or developer to take a closer look.

    Lastly, when you mentioned “Here is how it looks …”, I assume there was an image or a detailed description that I can’t see here. Providing such visuals can be very beneficial for troubleshooting, so ensure to attach or describe the issue in detail.

    Hope one of these steps helps, and do let us know how it goes.

    Warm regards,

    Caio Ferreira

    Thread Starter Frank Spade

    (@spade)

    Thank you for your helpful reply.

    My wp-config.php contains these line:
    define(‘WP_DEBUG’,’/wp-content/logs/wp-errors.log’);
    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, true);

    The folder /wp-content/logs is set to 775.

    Because I didn’t get a log-file created, I made a small file with this content:
    <?php error_log(‘Hello World!’); and set it to 751.

    Still no log file to find.

    What am I doing wrong?

    Thread Starter Frank Spade

    (@spade)

    I just checked the Server-logfile and found the “Hello world!” there, but also multiple messages like this:
    PHP Warning: Constant WP_DEBUG already defined in /is/htdocs/wp1174125_Y2HN1MV9U4/www/patientensorge/test/wp-config.php on line 109

    I can’t see, what is causing that, since I only know of the one in wp-config.php

    Caio Ferreira

    (@caiohferreiradev)

    Hello again Frank,

    Thanks for your reply!

    I can see that you’ve defined WP_DEBUG twice in your wp-config.php. Try updating it to:

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', true);

    After making that, ensure the /wp-content/logs directory is writable. Contact your hosting provider if unsure, and remember to clear cache if you do use one.

    Sorry that I didn’t mention earlier, could you please try some simple steps below to see if you can get the problem solved?

    1. Default WordPress Theme: Temporarily switch to a default theme, like “Twenty Twenty Three.” If issues resolve, your theme might be the cause.
    2. Check .htaccess: Rename your .htaccess to .htaccess_old. Then, in WordPress, go to Settings > Permalinks and click “Save Changes” to create a new one.
    3. Increase PHP Memory: Edit your wp-config.php and add:
    define('WP_MEMORY_LIMIT', '256M');

    4. Update All Components: Ensure WordPress, themes, and plugins are up-to-date.

    Could you please let us know how it goes now?

    Best,

    Caio Ferreira

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘website-editor not loading’ is closed to new replies.