jpowersdev

Hi @anthonyfroio,

You’re very welcome!

Best,
Jon

Hi @newfootprint,

If you take a look in the network tab in your browser dev tools, you can see the error message that Mailchimp is responding with. Here’s a screenshot.

Looks like your Mailchimp form requires the Phone and Birthday fields to be filled out, but those fields haven’t been added to the form on your website. You can either take a look at your Mailchimp settings and make those fields optional, or you can add the fields to the form on the site.

Let me know if you have any further issues,
Jon

Hi @barrettjason,

This is almost certainly coming from another plugin that’s attempting to style TinyMCE metaboxes. Do you have any plugins enabled that render a wysiwyg on the admin side with a dark background? I assume the background will be dark because the text is white.

If you can’t figure out which plugin is doing this, you can always add your own admin stylesheet that changes the text color. You can use this hook to enqueue admin styles.

Let me know if that helps,
Jon

Hi @13patricia,

Glad you figured out the conflict! Yes, we will most likely have to change some code, but first we need to do some investigation.

Now, since this is a paid theme, I can’t really look at the code to help you out. But I found a demo on their website (https://demo-store.wasabitheme.com/producto/tshirt/). It looks like they’re taking the content that would normally be found in tabs and laying it out in a different way. In other words, they removed the tabs from WooCommerce.

If you want to bring the tabs back, you’ll have to figure out where they did that and undo it. It looks like they are overriding the woocommerce_after_single_product_summary hook to add their own content. You could probably remove the line that is doing that, and it would bring your tabs back.

That being said, if you do remove the override there, it may cause problems with the theme, and it will replace the little description/reviews section underneath the product with tabs.

If you wanted to keep both, you could try adding your own tab solution and just grab the post meta fields that our plugin provides in your php template. Not sure if you want to go that deep, but it’s also an option. I can provide support if you do.

If you need help with any of the above, let me know!

Jon

Hi @elenio,

No worries. You don’t need to wrap it in <script> tags unless you’re adding it to the html of the page. It looks like you’re using a plugin to add the js, so you can just drop the code itself into the plugin’s box.

Let me know if that works,
Jon

Hi @thebrownagency,

Okay, I understand. Our plugin doesn’t add or remove any js, it just registers tabs with WooCommerce. We run the WordPress content filter on the tab content, which allows shortcodes to work. I do see you are using Elementor, could you try enabling Page Builder Compatibility in the settings? You can find that referenced here – https://yikesplugins.com/knowledge-base/page-builder-compatibility/

Let me know if that helps,
Jon

Hi @obedii21,

Sorry, I didn’t see your message at first. I’d recommend making a new thread in the future to make sure we see it quickly.

It looks like your theme has some code that controls the scroll to the element. I’m seeing this in your theme’s custom js file:

$('a[href*="\\#"]').click(function(event){
        var at_offset= $.attr(this, 'href');
        var id = at_offset.substring(1, at_offset.length);
        if ( ! document.getElementById( id ) ) {
            return;
        }
        if( $( at_offset ).offset() ){
            $('html, body').animate({
                scrollTop: $( at_offset ).offset().top-$('.at-navbar').height()
            }, 1000);
        }

    });

The problem with this sort of code and the hidden tabs is that the offset() of a hidden element is 0, which ends up scrolling you to the top of the page.

If this code was specific to the tabs, I’d recommend grabbing the parent element’s offset (as it will be visible). Since this code is applying to all anchor tags, that may not work very well.

If you want that scrolling animation to still work, you’ll want to update the $('a[href*="\\#"]') to ignore tabs, then create another click event for tabs specifically that uses $( at_offset ).parent().offset().

If you just want to fix the broken scroll, you could update the fail condition to exclude tabs, like this:

if ( ! document.getElementById( id ) || id.startsWith('tab') ) {
     return;
}

Let me know if that helps,
Jon