jpowersdev

Hey all, this should be fixed now.

@ucsendre was correct, the comment wasn’t updated in the primary PHP file.

We use a Github Action to deploy, so the easiest solution was to bump it to 1.7.9 with the correct comment. Please try to update to that latest version now.

Jon

Hi @davidgarcia2022,

Do you see any errors in your browser console when on the Edit Form page? There will likely be a failed network request with some details about what happened.

Jon

Hi @fherewecom,

Could you provide a list of any custom post types and taxonomies on the site, and how you have generated them? You may have some sort of orphaned taxonomy that doesn’t apply to any post types, which is causing the “check which post type this taxonomy belongs to” code to fail.

Jon

Hi @marketing4dct,

Admin-only tabs are not currently a feature of our plugin, but that is certainly an interesting request.

This seems like it would be a good use case for something like Advanced Custom Fields. You can use a plugin such as that (or Pods, MetaBox.io, Carbon Fields, etc.) to add extra meta boxes to the product page that would allow you to store additional admin-only information.

Let me know if that helps,
Jon

Hi @td8000,

Divi must be manually triggering the WooCommerce tabs hook without setting up the global variables correctly. The global $product variable should be defined during this callback as per the WooCommerce docs.

Divi is a paid plugin that I do not have a copy of, so I cannot be sure this will help, but in your custom tabs plugin folder can you make the following change on line 39 of public/class.yikes-woo-tabs-display.php and let me know if it resolves the issue:

Replace global $product; with the following:

$product = wc_get_product();

if ( empty( $product ) ) {
    return $tabs;
}

I’m attempting to grab the current product another way, and failing more gracefully if I’m unable to do so. It is possibly that this will resolve the fatal error without addressing the deeper compatibility issues. Please let me know what you find.

Be sure to take a backup before editing your site files.

Jon

Hi @yosipsverko,

This can happen when making changes to a form on the Mailchimp side. Our plugin won’t necessarily be informed of those changes, and then submissions to Mailchimp will start to fail. One of the most common culprits is fields that are now required in Mailchimp, but were not when building the form. The submission will succeed to our plugin, but fail when sending it to Mailchimp.

The easiest solution here is just to recreate your form in our plugin after making changes to your Mailchimp settings. I’d also recommend clearing the API cache in the plugin settings beforehand, to ensure our plugin has the latest data from your Mailchimp account.

Let me know if that helps,
Jon

Hi @td8000,

Could you use something like https://imgbb.com/ to share the screenshot?

In general though, the compatibility with Divi Builder is not good. You can find several threads on our forums addressing this. Regardless, I’ll do what I can to help.

Thanks,
Jon

Hi @1bachus1,

I’m not familiar with that plugin, but our plugin supports shortcodes in tab content. I know others have used the “build a shortcode” feature of some page builders in the past to combine the two approaches.

Let me know if that helps,
Jon

Hi @marcuslion,

I entered the form and received an email. It looks like you have the double-opt-in strategy active, so it sent me an email asking me to confirm my subscription. I did so.

Can you check and see if an email address from yikesinc was added to your list?

Jon

Hi @aywangsd,

That is indeed very strange. I would have to assume that some sort of identifying bit of information (like the title or something) is shared between lists, and that is causing some sort of confusion.

I’d recommend first clearing the API cache (https://yikesplugins.com/knowledge-base/api-cache-settings/) and if that doesn’t work, delete the form and re-create it. If neither of those work, you can delete the plugin and re-install it. This will wipe all plugin data from your WordPress site that might be interfering with the connection.

Let me know if that helps,
Jon

Hi @gallegoara,

As for your first question – I’m no SEO expert, but the tabs are present in the page markup, and as such I would have to assume that they are relevant for SEO purposes.

As for your second question – this is a fairly complex setup. To achieve “the same tabs on each product, but different content for different products” you will probably want to create a shortcode that is capable of rendering the correct tab content per product, then set up tabs in a particular order that contain those shortcodes. Global and Taxonomy-assigned tabs are features of the pro version of this plugin, but you can accomplish a similar feat (with slightly more legwork) by creating Saved tabs and assigning them to your products individually.

Let me know if that helps,
Jon

Hi Tom,

You’re welcome to open a support thread if you’d like help with this issue. Could you provide a link to the page you are having trouble with?

Thanks,
Jon

Hi @arjunlajpal,

It looks like you’re using Elementor when building your site. Please try enabling page builder compatibility in our plugin settings.

Here is a relevant knowledge base article – https://yikesplugins.com/knowledge-base/page-builder-compatibility/

Let me know if that helps,
Jon

Hi @mstudioil,

Sure- I’d recommend creating a custom shortcode to handle displaying that information. Then you can create a Saved Tab containing the shortcode and assign it to your products as needed.

Let me know if that helps,
Jon

Hi @brnsantos,

Our plugin does work with WPML, but my understanding is that there is no automated way of doing what you’re looking to do. You would need to manually create a matching tab on the different versions of a product.

I’m making some assumptions here (as we aren’t the authors of WPML), but this is my understanding of the problem –

When initially creating a new language version of a product, the full meta is copied to that new product so that it can be translated. All tabs are stored together as a single meta field. When you create a new tab on a product, it’s just updating the existing meta, not creating a new meta field. As a result, WPML can’t just copy that updated meta or it would override the translated meta on the other versions of that product.

Let me know if that helps,
Jon