Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Based on your description, it sounds like multiple operations (plugin/theme updates, media uploads, and general site performance) are failing, which often points to a server configuration issue, a plugin/theme conflict, or a fatal PHP error.

    To help narrow down the cause, I’d recommend the following:

    • Enable WP_DEBUG and WP_DEBUG_LOG, then check the /wp-content/debug.log file (or your server’s PHP error log) for any fatal errors.
    • Review Tools → Site Health for any reported issues or failed loopback/REST API requests.
    • Temporarily deactivate all plugins and switch to a default WordPress theme to rule out a conflict.
    • Check your browser’s Developer Tools (Network and Console) while updating plugins or uploading media to see if any requests return errors (e.g. 500, 403, or timeout).
    • Verify your PHP limits (memory_limit, max_execution_time, upload_max_filesize, and post_max_size) with your hosting provider.

    If the issue persists, please share your Site Health information (Tools → Site Health → Info → Copy site info) and any errors from the debug log or PHP error log. That should provide more clues about the root cause.

    From your description, it appears that the Shop page is still displaying an older template instead of the one you’ve recently edited. This is often caused by template assignment, caching, or a theme/page builder configuration issue.

    To help narrow it down, could you please check the following?

    • Which theme and page builder are you using (Elementor, Divi, Bricks, etc.)?
    • If you’re using a custom Product Archive template, confirm that it is published and correctly assigned to the Shop archive/page.
    • Clear all caches (plugin, server, CDN, and browser) and check whether the changes appear.
    • Temporarily switch to a default WordPress theme and deactivate all plugins except WooCommerce to rule out a conflict.
    • Check whether the issue persists after regenerating the page builder’s CSS/data (if your builder provides that option).

    If the problem remains, please share:

    • The active theme and page builder.
    • Whether the Shop page is assigned under WooCommerce → Settings → Products.
    • Any errors shown in the browser console or PHP error log.

    That information should help identify whether the issue is related to the theme, page builder, or WooCommerce template assignment.

    The “critical error” message is only a generic notification and doesn’t indicate the actual cause. To identify the issue, I’d recommend the following:

    • Enable WordPress debugging by setting WP_DEBUG and WP_DEBUG_LOG to true in wp-config.php, then reproduce the issue and review the /wp-content/debug.log file (or your server’s PHP error log).
    • Since you’ve already ruled out plugins, temporarily switch to a default WordPress theme (such as Twenty Twenty-Five) to determine whether the active theme is responsible.
    • Verify that your theme and any custom code are fully compatible with PHP 8.2. If possible, you could also test with PHP 8.1 for comparison.
    • Check your browser’s Developer Tools (Console and Network tabs) for any failed REST API requests or JavaScript errors when opening the editor.

    If you can share the exact fatal error from the debug log or PHP error log, it will be much easier to identify the root cause.

    You login your wp dashboard, then u click Appearnce – Customized – Custom Css and past this css.

    body .wp-site-blocks .wp-block-group[class*=”-background-color”] a:where(:not(.wp-element-button)):where(:not(.elementor *):not([data-elementor-type] *)){
    color: #fff !important;
    }

    Try checking these first:

    1. Clear your site, browser, and any CDN cache.
    2. Inspect the menu element to see which CSS rule with !important is overriding the white color.
    3. If you’re using a caching/optimization plugin, regenerate or purge its CSS files.

    I think one of these should solve the issue. If not, I know a few more ways to track down exactly where the CSS override is coming from.

Viewing 5 replies - 1 through 5 (of 5 total)