It would be easier to help you if you have shared your site’s link that has the issue. That could be a bug in the theme. Disabling the banner on the settings should not show the banner anymore.

I have looked at the demo of woodmart theme to understand your case. Can you try adding the following CSS? Let me know if that works. You should contact support or the author of the theme to get this sorted out.

.whb-row.whb-top-bar.whb-not-sticky-row.whb-without-bg.whb-without-border.whb-color-dark.whb-col-1 {
     display: none;
}

You may use CSS to disable it. However, if you wish to disable Divi AI on both the frontend and backend, you may use the following code to be added to your “mu-plugin” folder.

To implement your custom plugin as a Must Use plugin (mu-plugin) in WordPress, you need to follow these steps:

• Access your WordPress files. You can do this using FTP or your hosting control panel’s file manager.
• Navigate to the wp-content directory. If the mu-plugins directory does not exist, create one.
• Create a new PHP file inside the mu-plugins directory. You can name it something related to your plugin, such as disable-divi-ai-function.php.
• Paste your plugin code into this new PHP file and save it.

Here is your code for reference:

/*

<?php
/**
 * Plugin Name: Disable Divi AI
 * Plugin URI: https://aldinlapinig.com/
 * Description: Plugin to disable Divi AI on the frontend and backend.
 * Author: Aldin Lapinig
 * Author URI: https://aldinlapinig.com
 * Version: 1.0
 */

function print_custom_css() {
    echo '<style>
    .et-fb-icon.et-fb-icon--divi-ai,
    button.et-fb-button.et-fb-button.et-fb-button--info.et-fb-ai-options-button,
    .et-fb-right-click-menu__item.et-fb-right-click-menu__item--generate_content_with_ai,
    .et-fb-settings-option-ai__button {
    display: none !important;
    }
    </style>';
}

/* Disable Divi AI on the frontend */
function disable_ai() {
    print_custom_css();
}
add_action( 'wp_head', 'disable_ai' );

/* Disable Divi AI on the backend */
function disable_backend_ai() {
    print_custom_css();
}
add_action( 'admin_head', 'disable_backend_ai' );
?>

*/

Let me know if this works.

I agree with Brett. I’ve experienced the same port conflict when I was using XAMPP or MAMP.

There are two (2) workarounds that solved the issue.

OPTION 1: Set Router Mode to Localhost. This will allow Local to  automatically find available port on your computer. Downside, your local site installation will use localhost as domain name instead of your site domain. But it shouldn’t matter in the development. See short clip and instruction below:

• • Go to Menu >> Preferences >> Advanced
  • Set Router Mode from the default “Site Domains” to “localhost”
  • Click Apply
  • Exit menu by click x button on the upper right.
  • It will prompt a warning to fix domain, just click fix it and it should automatically reconfigure your site installation domain setup.

OPTION 2: Stop HTTP function on Windows (I’m not sure how to do it on Mac or Linux).

• • Open CMD with Admin privilege – right click CMD icon, go to more and select Run as Administrator.
  • Type net stop http and press enter.
  • It’ll prompt you with ” Do you want to continue this operation (Y/N)”. Just press Y and hit enter.
  • Wait for it to finish terminating several services.
  • Run Local again and make sure Router Mode is in “Site Domains” mode

There can be several factors causing this kind of error. In my experience, this is usually due to plugins or theme conflicts that may happen after updating theme.

To troubleshoot for possible plugin conflict, you need to access your site data via cPanel File Manager or FTP or equivalent tool depending on your hosting or system.

Note: Create a backup of your site before doing the following.

1. Check for plugin conflict.
   • Via cPanel File Manager or FTP, go to YourWebsite/wp-content/
   • Rename the folder “plugins” to anything like “plugins_bkp”
   • Try refreshing the site if that solves the issue.
   • If the error is gone, this means the issue is caused by the plugin. Otherwise, go to number 2. Check for theme conflict.
   • To figure out the conflicting plugin, create a new folder with the name “plugins”
   • Individually copy each folder content in “plugins_bkp” to the new “plugins” folder you created.
   • Keep refreshing the site after each plugin copied to check if that specific plugin is causing the issue.
   • Once you find the problematic plugin, delete that and access your WP Dashboard to install a fresh copy of that plugin.
2. Check for theme conflict
   1. Via cPanel File Manager or FTP, go to YourWebsite/wp-content/themes/
   2. Delete the theme folder you are using for your site.
   3. Try refreshing the site if that solves the issue.
   4. If the error is gone, access your WP Dashboard to install a fresh copy of your theme.

If after installing fresh copies of your plugin or theme and the issue is not solved, contact support for the item.

I hope that helps.