| 开发者 | maradigma |
|---|---|
| 更新时间 | 2026年9月25日 18:26 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/, or install the plugin through the WordPress administration area.Yes. An active Maradigma account and valid API credentials are required for the connected catalog, availability, pricing, and booking features.
Yes. The plugin registers a dedicated boat post type and can create or update synchronized boat pages. Administrators can choose how generated layouts and boat data are updated.
Yes. Add the fleet listing shortcode to a page, post, or compatible builder element:
[maradigma_boats]
The shortcode supports filters, sorting, pagination, configurable filter placement, and editable boat-card templates. A complete shortcode reference is included in docs/MARADIGMA_SHORTCODES.md.
Yes. The plugin provides a full single-boat shortcode and field-specific shortcodes.
Examples:
[maradigma_boat slug="my-boat-slug"]
[maradigma_boat_title]
[maradigma_boat_booking]
The plugin provides native Gutenberg blocks, dedicated Elementor widgets, and WPBakery elements for fleet listings and individual boat content. It also provides editable master layouts that can be propagated to synchronized boat pages.
Yes, when WooCommerce is installed and active. Public WooCommerce products can be linked to Maradigma boats and used as boat-detail pages. The integration does not replace WooCommerce checkout and does not modify WooCommerce system pages such as Cart, Checkout, or My Account.
Yes. The plugin includes compatibility layers for WPML and Polylang and can synchronize language-specific boat pages and metadata according to the active multilingual configuration.
When Yoast SEO is installed and active, the plugin can synchronize or generate boat metadata according to the configured SEO options.
Yes. The boat base slug setting accepts the {{destination}} and {{boat_type}} placeholders. For example, es:{{destination}}/alquiler-{{boat_type}},en:{{destination}}/boat-rental-{{boat_type}} generates localized paths such as /mallorca/alquiler-yate/boat-slug/ and /ibiza/alquiler-lancha/boat-slug/. The values are synchronized from the connected Maradigma account. Re-synchronize existing boats after enabling this route format.
No. The supported frontend libraries distributed with the plugin are bundled locally. Boat media returned by the connected Maradigma account may still be displayed from Maradigma-provided URLs.
destination or boat_base_port in filters_ui_fields (or in the "More filters" drawer) and visitors get a searchable selector. Both lists are built from your own boats — with the number of boats in each place — so they only offer places that return results.md_* parameter it sends, the real default values, the search attributes of the listing (including base port and skipper), and examples that use length, cabins, skipper and online booking. The fields were already there; the documentation buried them.allow_url_filters="1"): the slider took the visitor's own values as its ends, so the range could not be widened again except with "Reset"./wp-json/maradigma/v1/boats/{id}) from answering visitors with internal data. On request it returned the boat owner's record (e-mail, tax id), the accounting data and, on every call, the commission and the private calendar (iCal) address of the boat. It now returns only the customer-facing fields the booking modal needs. The shop cart address also returns only the fields the booking flow reads, and is no longer cached by intermediaries./wp-json/maradigma/v1/booking address, which forwarded the "booking without payment" call of the API.tags="3,7" attribute still filters by tag ID.port="<place name>" attribute of [maradigma_boats] instead of searching the name as text, which returned nothing: use destination="1704" (or port="port:12") to limit a listing to a place.featured="1", and to show featured boats first move them to the top of your fleet order in Maradigma.boat_licence_required="0" are the boats that require a licence), the text search only looks at model, trade name, builder and reference (not places), and the attributes the API ignores are now marked as such.destination shortcode attribute limits a listing to them. Combined with the boat type, it gives one page per boat type in each destination, and it stays applied when visitors filter or paginate./boats/ fallback when routing data is incomplete.{{destination}} and {{boat_type}} placeholders.From, day, and Charter use the bundled gettext translations.MARADIGMA_PLUGIN_DEBUG constant.{{destination}} route placeholder.service_destination to the supported single-boat API expansions.