Post Carousel for Elementor, Responsive Posts, Products and Taxonomy Slider vs WP Swiper

WebCodingPlace Post Carousel for Elementor adds a single, deeply configurable carousel widget that lets you slide any post type, including WooCommerce products, portfolios, events, custom post types and taxonomy terms through ready-made templates. Pick a heading source from any post field or meta key, trim it to a word count, swap the read-more text and target, choose your image size, lazy-load thumbnails, enable social sharing and apply your own CSS, all from the Elementor editor. Quick Links Live Demos. More Details. Highlights Choose source: Post Type or Taxonomy Multi-select posts or terms, plus exclude-by-ID Heading & description from any built-in field or custom meta key Word-count trimming with custom suffix Optional shortcode / HTML rendering inside the description Read-more text, classes and link target Slick-powered slider with full responsive column control, autoplay, dots, arrows, RTL, vertical mode and adaptive height Pluggable template registry — add your own styles via the dpce_styles filter and drop a PHP template in your theme Per-style appearance controls auto-generated from the styles array Social sharing buttons, placeholder image and “hide current post” support External services This plugin generates outbound share URLs for the optional Social Sharing feature in the carousel widget. When the Enable Social Sharing setting is turned on (it is OFF by default), the carousel renders a row of links that point to the share endpoints listed below. No data is sent automatically. Data is only transmitted to a third party when an end-user clicks one of those share links in their browser, and the only data appended to the URL is the post’s public permalink and post title. Facebook Used to let visitors share a post on Facebook. Endpoint: https://www.facebook.com/sharer/sharer.php Data sent on click: post URL. Terms of service: https://www.facebook.com/legal/terms Privacy policy: https://www.facebook.com/privacy/policy X (Twitter) Used to let visitors share a post on X. Endpoint: https://twitter.com/intent/tweet Data sent on click: post URL, post title. Terms of service: https://twitter.com/en/tos Privacy policy: https://twitter.com/en/privacy LinkedIn Used to let visitors share a post on LinkedIn. Endpoint: https://www.linkedin.com/sharing/share-offsite/ Data sent on click: post URL. Terms of service: https://www.linkedin.com/legal/user-agreement Privacy policy: https://www.linkedin.com/legal/privacy-policy WhatsApp Used to let visitors share a post on WhatsApp. Endpoint: https://api.whatsapp.com/send Data sent on click: post URL, post title. Terms of service: https://www.whatsapp.com/legal/terms-of-service Privacy policy: https://www.whatsapp.com/legal/privacy-policy Pinterest Used to let visitors pin a post on Pinterest. Endpoint: https://pinterest.com/pin/create/button/ Data sent on click: post URL, post title. Terms of service: https://policy.pinterest.com/en/terms-of-service Privacy policy: https://policy.pinterest.com/en/privacy-policy The Email option uses a standard mailto: link handled by the visitor’s local email client and does not contact any third-party server. Third-party libraries This plugin bundles Slick Carousel (https://kenwheeler.github.io/slick/) by Ken Wheeler, distributed under the MIT license. Files are loaded locally from assets/vendor/slick/ and no remote requests are made.

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. Choose from seven editable in-block starter templates without adding extra block types. 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.