Support

Open Products → Tabs Tools & Health → System report and press Copy to clipboard. Paste it into your message.

It lists the WordPress, WooCommerce, PHP and plugin versions, your theme, your active plugins, the plugin's settings, whether your theme overrides the WooCommerce tabs template, every callback attached to the product tabs filter with the file it comes from, your max_input_vars value, and the last fifty entries of the activity log. That is most of what anyone would otherwise have to ask you for.

Before writing, it is worth checking the Health tab on the same screen and the troubleshooting page. They cover the common cases, including tabs not appearing with a particular theme and the truncated-save message.

The forum is the main channel for the free plugin, and the best one for anything another shop might hit as well, because the answer stays public.

Open the support forum

A forum thread needs a WordPress.org account, which is free. Do not paste licence keys, passwords or customer data into a public thread.

For anything you would rather not post in public — a site URL, a staging login, an export of your tabs — write to [email protected].

This is a small operation. Email is answered as fast as it can be, without a promised response time attached to the free plugin. Guaranteed response times are one of the things intended for the paid tier, which is not available yet.

What helps most, in order:

1. What you did, what you expected, and what happened instead.
2. Whether it happens with a default theme such as Storefront or Twenty Twenty-Five, and with other plugins deactivated.
3. The system report.
4. A screenshot of the tab strip or of the admin screen involved.

If you believe you have found a security issue, please report it privately by email rather than in the public forum, and give us time to ship a fix before describing it anywhere else.

• Bugs in the plugin, and questions about how it works.
• Migrations from the tab plugins it reads: Custom Product Tabs for WooCommerce (YIKES), Barn2 and WB.
• Working out whether a rendering problem comes from the plugin, the theme or another plugin.

It does not cover writing your theme's CSS, custom development, or problems in other plugins. When a conflict turns out to belong to another plugin, we will say so and point at the evidence rather than leave the thread open.