
內容簡介
WP Swiper 是一款靈活的旋轉木馬區塊外掛,讓使用者能在 WordPress 編輯器中輕鬆建立包含多種內容的幻燈片,無需使用額外的頁面建構器。
【主要功能】
• 使用標準區塊建立幻燈片
• 支援水平或垂直響應式旋轉木馬
• 可配置導航、分頁、自動播放等功能
• 設定響應式斷點、間距及顯示幻燈片數量
• 拖放圖片檔案以創建幻燈片
• 無需 jQuery 的 Swiper 14 運行時
外掛標籤
開發者團隊
原文外掛簡介
WP Swiper adds a flexible carousel block to the WordPress editor. Each slide accepts standard nested blocks, so you can combine images, headings, buttons, video, and other block content without using a separate page builder.
Highlights
Build slides with nested WordPress blocks.
Create horizontal or vertical responsive carousels.
Configure navigation, pagination, autoplay, loop mode, free mode, and transition effects.
Set responsive breakpoints, spacing, offsets, and slides per view.
Add background images, focal points, overlays, thumbnails, and custom navigation icons.
Drag image files into the editor to create slides.
Load frontend assets only when a slider is detected, with an optional global-loading setting for custom setups.
Use the bundled Swiper 14 runtime without a jQuery dependency.
Accessibility
Since version 1.4.6, WP Swiper removes non-visible slides from the accessibility tree and keyboard tab order. Focusable content is restored when its slide becomes visible, including in responsive layouts that display multiple slides.
This behavior addresses one carousel accessibility barrier, but it is not a certification that WP Swiper or a website using it conforms to WCAG. Conformance must be evaluated for the complete published page and depends on the carousel configuration, slide content, theme, and other integrations.
Site authors remain responsible for accessible content and configuration. Provide meaningful image alternatives, logical headings, readable contrast, and clear control labels. If autoplay is enabled, enable the pause/play control so users can stop rotation. Rotation stops when keyboard focus enters the carousel and restarts only after an explicit user request. See the W3C carousel accessibility guidance.
Privacy
WP Swiper does not include analytics, advertising, tracking, or telemetry. Images selected through the editor are handled by the standard WordPress Media Library and REST API.
Support and development
For usage questions, use the WordPress.org support forum. Report reproducible bugs and feature requests on GitHub. Security issues should be reported privately according to the repository security policy.
Development is supported through Buy Me a Coffee.
Developer filter
The wpswiper_frontend_js_register_args filter can change the dependencies and loading arguments used for the plugin’s frontend script.
add_filter( 'wpswiper_frontend_js_register_args', function ( $args ) {
$args['deps'][] = 'jquery';
$args['args'] = array(
'in_footer' => true,
'strategy' => 'defer',
);
return $args;
} );
See the wp_enqueue_script() documentation for supported loading arguments.
Frontend lifecycle
WP Swiper automatically initializes blocks added after page load. Navigation and AJAX integrations can also call window.wpSwiperInit(element), window.wpSwiperDestroy(element), or window.wpSwiperReinit(element) with a .wp-swiper block wrapper.
Runtime configuration corrections dispatch a wp-swiper:warning browser event with a structured diagnostic. Initialization failures dispatch wp-swiper:error, and explicit destruction dispatches wp-swiper:destroy.
Contributing
WP Swiper is developed openly on GitHub, and community contributions are welcome.
Report reproducible bugs through the GitHub issue tracker.
Suggest focused improvements and new features.
Improve documentation, translations, accessibility, or test coverage.
Submit pull requests after reviewing the contribution guide.
Please report security issues privately according to the security policy.
