
Carousel Slider Block’s styles zero out block margins with a high level of specificity. However, with the way the CSS is written in the plugin, it was likely an issue in previous versions. The theme I am testing uses the new “block gap” feature in WordPress 5.9 to handle vertical spacing. As shown in the following screenshot, the Heading, Paragraph, and Buttons blocks have no space between them: No spacing between blocks. The biggest problem I ran into with the plugin was that it overwrote block margins within the slides. Users can manually set the breakpoint or leave it to the default of 768px.

The block has a separate panel for controlling the number of slides on smaller screens. However, the slides are shown in reverse order on the front end.

Switching it on did not seem to make any changes in the editor. There is an RTL mode, which was not immediately clear was working correctly. It includes toggles to loop back around at the end of the carousel and an auto-play option. Users can control the number of shown slides, how many to show on scroll, and the animation speed. The block’s options are the baseline controls expected from such a plugin. The plugin allows users to toggle both on and off. I would love to see that replaced with the previous/next arrows and dots navigation in the editor view if either of them is enabled. Once a few slides are added, it appears below the outer Slider Carousel block: Slider Carousel with simple image slides. The primary difference between the editor and front end is the horizontal scrollbar shown on the post-editing screen, used for navigating the carousel. And it does not have a dizzying array of configuration settings. The slides do not all stack atop one another, looking nothing like their final output on the front end. There is no management via a separate custom post type screen. I added a screenshot of this default setup to show that the plugin feels almost native to WordPress. From there, users can add any other block within each: Initial carousel insertion. The UI is similar to the core Row block when inserting slides - click the “+” icon. Users merely need to insert the Carousel Slider block in the editor to create a new carousel.
WORDPRESS IMAGE CAROUSEL FULL
Overall, creating a carousel full of slides was straightforward. There is one fixable problem, which I will get to. It also does not complicate the experience more than it has to. What makes Block Slider Carousel a solid plugin is that it is, mostly, WYSIWYG. The TLDR version is it handles far better than others I have seen. The question I needed to answer was whether this was a solid implementation.

However, I know a lot of people like them. I tolerate them on some sites if used to tidy inconsequential content. Or, they begin to automatically slide before users finish reading the first panel. They are often used to hide away content, forcing site visitors to take additional action to find it. I should preface this review by saying that I have a general dislike of sliders and carousels. Like so many others, I ask myself, Could this be one of those diamonds in the rough? I am always optimistic enough to hold out the tiniest sliver of hope. More often than not, the projects are fundamentally broken or are a bit too spammy for my taste. It has slowly garnered more than 5,000 active installs since its release.
WORDPRESS IMAGE CAROUSEL CODE
The majority of Jetpack sites do not have this enabled since it currently requires some custom code that toggles the jetpack_enable_carousel_stats option.Over the weekend, Virgiliu Diaconu asked me to check out his Carousel Slider Block plugin, a project he has maintained for three years. * Image views are only recorded if the site owner has enabled image view stats tracking for this feature, which is disabled by default. We sync a single option that identifies whether or not the feature is activated. We also track when, and which, configuration settings are modified. We track when, and by which user, the feature is activated and deactivated. The usage of this feature may expose photo-related information, such as EXIF data, GEO data, and camera information.Additionally, for activity tracking (detailed below): IP address, user ID, username, -connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.įor image view tracking * (detailed below): IP address, user ID (if logged in), username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. If you ever need to deactivate it, you can toggle the Display images and galleries in a gorgeous, full-screen browsing experience setting from the Media section at Jetpack → Settings → Writing.
