| 开发者 | yourgeek |
|---|---|
| 更新时间 | 2026年9月25日 15:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-content/plugins/carrentory/templates/search/form.php
to:
wp-content/themes/your-child-theme/carrentory/search/form.php
Keep the same relative path inside the theme's carrentory directory. Keep business logic in plugin services and hooks, not templates.
Developer extension points
Developers can adjust template data and template locations without editing core files. Useful extension points include:
carrentory_get_template_argscarrentory_locate_templatecarrentory_before_templatecarrentory_after_templatecarrentory_frontend_view_dataNo. CarRentory provides its own fleet, availability, search, booking, and administration workflow.
Yes. Free is a standalone booking plugin with fleet management, availability, offline payments, admin bookings, and a basic calendar. Pro is an optional add-on.
Pay on arrival and bank transfer are included. Stripe Checkout is available in CarRentory Pro and is not part of Free.
CarRentory is translation-ready and has prepared translations for English, German, Greek, Spanish, French, Italian, and Dutch.
WPML is not supported. CarRentory's built-in multilingual runtime and normal WordPress translation system do not require it. The plugin includes Polylang-aware page and locale handling but does not claim official Polylang certification.
Yes. All customer-facing templates owned by CarRentory Free can be copied to a carrentory directory in a theme or child theme and customized there.
Templates control presentation. Keep business rules in plugin services or hooks so pricing stays consistent across previews, saved bookings, emails, and admin views.
Booking and customer details are stored in the site's WordPress database and managed through the CarRentory admin screens.
CarRentory uses a necessary first-party booking cookie lasting up to 24 hours to prevent duplicate submissions. Anonymous booking attempts are also limited using short-lived, keyed identifiers derived from the booking context, email address, and direct network address. The protection records contain no raw cookie tokens, email addresses, or IP addresses. They expire within 24 hours and are cleaned during booking traffic and scheduled WordPress cleanup while the plugin is active. No CAPTCHA, analytics tracking, or external protection service is used. Booking pages must be excluded from full-page caching, and custom booking forms must retain the supplied hidden security fields.