| 开发者 | kitgenix |
|---|---|
| 更新时间 | 2026年10月14日 01:50 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
[kitgenix_tab] shortcode.[kitgenix_tab slug="warranty-info"]
The shortcode renders enabled saved templates. It is not a dynamic lookup for a product's private per-product tab or a conditional Global Tab.
JSON and CSV Import/Export
JSON is the full-fidelity portability format. It can carry plugin settings, Global Tabs, Templates, targeting conditions and visibility rules and can be used for controlled migration between stores.
CSV is intended for spreadsheet-friendly editing of the core Global Tab or Template fields such as title, nickname, slug, priority, enabled state and content. Targeting and visibility rules are not represented in the CSV format, so JSON should be used when those rules must be preserved.
Upload size is bounded by the plugin to reduce the risk of oversized import requests.
WooCommerce-Native Output
Frontend tabs are inserted with WooCommerce's woocommerce_product_tabs filter. That means the active WooCommerce-compatible theme continues to control the surrounding tab layout and normal product-page behaviour.
The plugin does not need to read or write WooCommerce orders in order to display product tabs. Product-specific tab data is stored against products, while global configuration and templates use plugin options.
Typical Store Uses
/wp-content/plugins/, or install it through Plugins → Add Plugin.Yes. WooCommerce is a required dependency, and activation is prevented if WooCommerce is inactive.
Edit a product, open Product data → Custom Tabs, add the tab title and content, configure any visibility or priority options, and update the product.
Yes. Create a Global Tab and leave its targeting rules empty. You can also narrow a global tab to selected products, categories, tags, or product types.
Yes. Visibility can depend on logged-in/logged-out status, WordPress user roles, stock status, and product purchasability.
Yes. Save it as a Template, insert it into tabs, apply it to selected products using WooCommerce bulk actions, or display the saved template with [kitgenix_tab].
Yes. The admin editor uses a locally bundled Quill editor. WordPress shortcodes in tab content can be processed when Allow Shortcodes is enabled.
Yes. JSON preserves settings, global tabs, templates, targeting, and visibility rules. CSV is available for the basic Global Tabs or Templates fields.
Yes. The plugin declares compatibility with WooCommerce custom order tables and does not depend on WooCommerce order storage for its product tabs.
priority values of neighbouring tabs, ensuring the management table order always matches frontend rendering order.[kitgenix_tab] shortcode for rendering a saved template anywhere WordPress shortcodes are processed, including posts, pages, widgets, and other product tabs.kitgenix_custom_tabs_for_woocommerce_tab_eligible, kitgenix_custom_tabs_for_woocommerce_tab_priority, and kitgenix_custom_tabs_for_woocommerce_tab_content.max_tabs setting, which defaults to 10.alloptions cache on every frontend request.register_setting() autoload argument was introduced.has_term().hidden attribute instead of a CSS class, preventing visible modal state from becoming out of sync with its underlying accessibility state.max_tabs limit rather than its intended 100-template library limit.assets/vendor/quill/ instead of loading executable JavaScript from cdn.jsdelivr.net on product edit and plugin settings screens.Settings::sanitize_tabs_rows() sanitisation used for manually saved tab data, ensuring imported content is never trusted as pre-sanitised.manage_woocommerce or manage_options capability and a matching nonce before processing.custom_order_tables) compatibility declaration. The plugin does not read or modify WooCommerce order data.cdn.jsdelivr.net; the editor library is now included locally with the plugin.enabled, visibility, and target, Portability admin-post actions, the [kitgenix_tab] shortcode, WooCommerce bulk action, and new developer filters.KitgenixCustomTabsForWooCommerce\Core\Tab_Matcher as the shared targeting and visibility engine, including is_eligible(), matches_target(), and is_visible().sanitize_target() and sanitize_visibility() sanitisation methods for the new targeting and visibility configuration structures.Tab_Modal_Fields trait used by both Product_Tabs and Settings_UI, preventing the product-editor and plugin-settings modal implementations from drifting apart.