Cart in Navbar Menu Won't Work

[btabor23]

I’m trying to enable and customize the shopping cart preview on my navigation but I cannot make any changes via customizer. Is this a common issue or is it isolated?

[Joao]

Hi There,

Are you on PRO? If you are using the header builder the Customizer settings won´t work.

Please let us know.

Thanks

[btabor23]

My license has been upgraded to PRO but I do not have the PRO theme installed.

[Joao]

Hey There,

Would you mind providing us with login credentials so we can take a closer look? Please provide following information:

Set it as Secure Note

• Link to your site
• WordPress Admin username / password

All the best!

[btabor23]

Thank you for your help. The secure note is above.

[Joao]

Hi There,

You don´t have WooCommerce active on your navbar, so those commands won´t affect the cart you have added using shortcode to your topbar.

If you want to add WooC cart to your navbar, go to Customizer > WooCommerce and set it to On.

Hope it helps

[btabor23]

I don’t have WooCommerce active in the navbar because I cannot change it’s appearance with any of the options.

Attached is a screenshot of the cart in the menu. This is how it looks no matter what styling options I choose.

[alexander]

Are you using any object cacheing? I checked and noticed you have an object-cache.php drop-in file: https://bpresentstudio.com/wp-admin/plugins.php?plugin_status=dropins

I don’t however see a cacheing plugin installed. Sometimes cacheing plugins add files like this, as it’s where WordPress looks as an entry point for object cacheing, but the plugin is still needed to configure the settings for that cache. Without the cacheing plugin active, having object-cache.php in place could lead to numerous problems with settings not updating, including what you are experiencing with the cart settings.

I’d recommend trying to remove that file then see if the issue persists.

[btabor23]

I removed the files and the issue still exists. Any other ideas?

[christopher]

Hi there,

Thank you for deleting the file. I checked your website and managed to change the color of the cart icon, so it is working now.

But I used the X > Launch > Options > Woocommerce section to change the cart color and not the customizer.

It is recommended that you use that menu as it will be the main section to customize the theme. The customizer will be phased out during the course of time.

Thank you.

[btabor23]

Christopher,

I see that the cart in the nav bar is working and appreciate your advice about moving away from the Customizer. When using X >Launch > Options, I continually get this error message:

The preview could not load due to the iframe response being incomplete. This is most often related to a plugin conflict, or customizations introducing a PHP error.

Origin URL: https://bpresentstudio.com
Preview URL: https://bpresentstudio.com

I’ve added the following code to my wp-config.php file and the issue still persists. Do you you have any solutions for this?

define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

[kory]

@btabor23,

Thanks for writing in. I see that you’re using a child theme on your website, to what extent are you using that child theme? Are you including CSS updates there, or have you gone further by introducing any sort of custom functionality in the functions.php file or overwritten any of our templates? Are you using any hooks or filters to modify content in any way? I’m wondering if something going on there is causing a potential conflict as the memory limits you have set should be more than enough on a good hosting environment.

If you do happen to have any more involved customizations present on your website, you may want to try auditing those one by one by commenting them out, or returning any modified templates to “stock” to see which alteration could be causing a conflict as mentioned in the warning message. Additionally, any plugins you’re using that could be doing any sort of odd content filtering or adjustments, you may want to try disabling those one by one to see if any of them are causing problems with the preview as mentioned by the message.

Once you’ve done that, we’ll you should either be able to locate the source of the issue or help provide us with a little more context from that, which will give us more to go on.