PHPackages wooletthedevsout/product-admin - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Admin Panels](/categories/admin) 4. / 5. wooletthedevsout/product-admin ActiveLibrary[Admin Panels](/categories/admin) wooletthedevsout/product-admin ============================== WLTDO module for product admin and edit implementations. v1.0.0(4y ago)25MITPHP Since Nov 15Pushed 4y ago1 watchersCompare [ Source](https://github.com/wooletthedevsout/product-admin)[ Packagist](https://packagist.org/packages/wooletthedevsout/product-admin)[ RSS](/packages/wooletthedevsout-product-admin/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (1)DependenciesVersions (2)Used By (0) Woo Let The Devs Out | Product Admin Module =========================================== [](#woo-let-the-devs-out--product-admin-module) To be used either as a standalone module or library, or as part of the WLTDO framework, this module intends to automate and ease the process of customizing WC product edit pages. Initially, classes will take care of everything as you add new tabs and panels to product meta within the edit pages. Additionally, we are developing classes to manage and alter existent tabs and fields. Install ======= [](#install) The easier way of using this package is by requiring it using Composer. Usage ===== [](#usage) In the plugin's main file, use the classes and autoload them with Composer. ``` use Wooletthedevsout\Product\Admin\{Tabs, Panels}; require __DIR__ . '/vendor/autoload.php'; $tabs = new Tabs('New Tab', $fields); ``` The class Tabs needs two parameters: the first is the name (not the slug) of the new tab, and the second an array of fields to be added. The array admits any number of fields, each one of them as a new array. ``` // Once the tab is created, we need to inject the panels dependency, using the method getPanel() $tabs->getPanel(); // Also, a title can be added if you want so $tabs->addTitle('The title'); ``` Ok, what about the fields? -------------------------- [](#ok-what-about-the-fields) Ohh... of course. As shown, the fields and firstly passed to the Tabs instance as an array. For this moment, we cover all field types with native support by Woocommerce: text, number, textarea, checkbox, select, radio (needs a CSS fix, as the WC native function is defective for the product edit area). So, we need an array of arrays. Each element is a field, and for each of these, the first element will be the field type: \*\*\* \[{{FIELD TYPE}}, {{SLUG}}, {{LABEL}}, {{DESCRIPTION}}\] \*\*\* For the select type, an additional element (another array) will include the options to be added. The same happens for the radio field, although for this latter we just cut the description, as it generates a lot of bugs within the backend. So, for the SELECT field and the RADIO field, respectivelly, we need to register like this: \*\*\* \[{{FIELD TYPE}}, {{SLUG}}, {{LABEL}}, {{DESCRIPTION}}, {{ARRAY OF OPTIONS}}\] \*\*\* \*\*\* \[{{FIELD TYPE}}, {{SLUG}}, {{LABEL}}, {{ARRAY OF OPTIONS}}\] \*\*\* Thus, imagine that we want two text fields, one checkbox, one select field and one radio, considering the previous code. The array to be passed would look like this: ``` $forms = [ [ 'text', 'user_message', 'Cool Label', 'Description for the tooltip with question mark.' ], [ 'text', 'capacity', 'Another Label', 'Description for the tooltip with question mark.' ], [ 'checkbox', 'confirm', 'Confirmation', 'Description for the tooltip with question mark.' ], [ 'select', 'choices', 'Select Title', 'Description for the tooltip with question mark.', [ 'Choice 1', 'Choice 2', 'Choice 3' ] ], [ 'radio', 'choices', 'Select Title', [ 'Choice 1', 'Choice 2' ] ]; ``` FAQ === [](#faq) Well, this is one of the first libraries and modules for the new Woo Let The Devs Out framework. So I imagine you guys have a lot of questions. Let's try to answer some of them. ### Do I need to use hooks or further implementation in order to save the meta of these new fields? [](#do-i-need-to-use-hooks-or-further-implementation-in-order-to-save-the-meta-of-these-new-fields) No, the Panels class is already equipped with the methods to do so. ### What about validating fields? [](#what-about-validating-fields) Honestly? We are working at... we are not pretty satisfied with WC's native validation, so we should eventually come up with something more sophisticated. ### Can we expect new field type (especially those not covered by the WC native API, like datetime, image, etc)? [](#can-we-expect-new-field-type-especially-those-not-covered-by-the-wc-native-api-like-datetime-image-etc) Definitely, the point with the WLTDO framework is to provide, ultimately, an easy and OO way of extending Woocommerce. Although some implementations and extensions for WC are really well-developed, like those for payment gateways, when developing complex integrations and entire packages, they require us to be really repetitive. ### Health Score 23 — LowBetter than 27% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity7 Limited adoption so far Community7 Small or concentrated contributor base Maturity50 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 1639d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/5495deeb43e72928608368492d8bfbc3b5af747b3eb842be9ecbe8b27c2a9e53?d=identicon)[wooletthedevsout](/maintainers/wooletthedevsout) --- Top Contributors [![meuppt](https://avatars.githubusercontent.com/u/37983141?v=4)](https://github.com/meuppt "meuppt (6 commits)") ### Embed Badge ![Health badge](/badges/wooletthedevsout-product-admin/health.svg) ``` [![Health](https://phpackages.com/badges/wooletthedevsout-product-admin/health.svg)](https://phpackages.com/packages/wooletthedevsout-product-admin) ``` ### Alternatives [jeroennoten/laravel-adminlte Easy AdminLTE integration with Laravel 4.0k4.8M43](/packages/jeroennoten-laravel-adminlte)[dmstr/yii2-adminlte-asset AdminLTE backend theme asset bundle for Yii 2.0 Framework 1.1k1.8M67](/packages/dmstr-yii2-adminlte-asset)[dwij/laraadmin LaraAdmin is a Open source Laravel Admin Panel / CMS which can be used as Admin Backend, Data Management Tool or CRM boilerplate for Laravel with features like CRUD Generation, Module Manager, Media, Menus, Backups and much more 1.6k68.7k](/packages/dwij-laraadmin)[filament/spatie-laravel-media-library-plugin Filament support for `spatie/laravel-medialibrary`. 1764.8M125](/packages/filament-spatie-laravel-media-library-plugin)[bezhansalleh/filament-exceptions A Simple & Beautiful Pluggable Exception Viewer for FilamentPHP's Admin Panel 193195.9k13](/packages/bezhansalleh-filament-exceptions)[filament/infolists Easily add beautiful read-only infolists to any Livewire component. 1220.8M36](/packages/filament-infolists) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)