| 开发者 | wpyog |
|---|---|
| 更新时间 | 2026年8月1日 04:00 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[wpyog_fleet] on any WordPress page to give your booking staff a full-featured panel without WordPress admin access. The panel is role-protected: only users with the Booking Staff role (or WordPress administrators) can access it. It includes the dashboard, bookings list and calendar, payments, expenses, WhatsApp/email sharing, vehicles, drivers, companies, and reports — mirroring the admin panel, with a mobile-responsive layout.
Practical WordPress Plugin For Business Workflows
WPYog Fleet is part of the WPYog plugin ecosystem by Poppins Digital. WPYog plugins are built for practical business workflows, helping organizations manage real operational needs directly from WordPress.
Current WPYog plugins include:
User Roles
jtb_admin capability) — full access including hard-delete of payments, expenses, and bookingsjtb_manage capability) — full create/edit/void access; no hard-delete.pot file is included in the languages/ folder. The plugin uses the text domain wpyog-fleet.
Database
The plugin creates its own database tables on activation and runs automatic migrations when the version changes. No existing WordPress data is modified.
/wp-content/plugins/wpyog-fleet/ directory, or install the plugin through the WordPress Plugins screen.[wpyog_fleet] to it, then go to WPYog Fleet → Staff Users and assign the Booking Staff role to any user who should have frontend panel access.WPYog Fleet is primarily designed as an internal booking and operations manager for transport businesses. It helps you manage bookings, drivers, vehicles, payments, and expenses from the WordPress dashboard (or from the optional frontend staff panel).
The current version is focused on admin-side and staff-side booking management. Front-end customer-facing booking forms may be added in a future version.
Yes. WPYog Fleet allows you to maintain vehicle and driver records and assign them to bookings.
Yes. You can record booking amount, advance amount, payment details, and pending balance.
Yes. WPYog Fleet allows you to add expenses related to bookings so you can keep better operational records.
No. It can also be used by cab rental companies, travel agencies, tour operators, tempo traveller operators, and small transport businesses.
No. WPYog Fleet is designed to work independently inside WordPress and does not require WooCommerce.
Bookings and pending payments can be exported to CSV from the admin panel today. Additional export and advanced reporting features may be added in future versions or a Pro version.
Go to WPYog Fleet → Staff Users and click Add Staff User, or assign the Booking Staff role to any user from Users → All Users. Once assigned, the user can log in at the page where you placed the [wpyog_fleet] shortcode.
Yes. Go to WPYog Fleet → Settings and update the Booking Prefix field. For example, a prefix of JT produces booking numbers like JT-2026-0001. Existing booking numbers are not affected.
No. Booking Staff can add, edit, and soft-void (with reason) payments and expenses. Hard-delete is available to WordPress Administrators only. Soft-voided records are preserved in the history for audit purposes.
Yes. All strings are internationalised using the wpyog-fleet text domain and a .pot file is included in the languages/ folder.
poppinsdigital from Contributors (not a valid WordPress.org username — was triggering an import warning); wpyog remains as the sole contributorwp_unslash( $_POST ) passed into a save function, with per-field sanitization happening inside that function) with a new WPYOGFLEET_Input class that sanitizes every field individually and directly at the point it is read from $_POST, using sanitize_text_field()/sanitize_textarea_field() wrapped around each $_POST access. Applied across all 28 form/AJAX save paths for vehicles, drivers, companies, bookings, payments, expenses, and settings. The previous phpcs:ignore-suppressed pattern was correct in that data was genuinely sanitized before use, but reviewers cannot verify sanitization that happens inside a separately-called function — this update makes the sanitization visible and verifiable at the exact line the input is read, which is what WordPress.org requires[wpyog_travels_booking] to [wpyog_fleet]