Otter Blocks plugin review and common issues

The Section block background uses CSS background-image property. Issues: (1) the image URL generated by Otter may not be correct — open the block settings in Gutenberg and re-select the background image to regenerate the correct URL; (2) check browser DevTools to see if the background-image CSS is being applied and what URL it references; (3) a caching plugin may serve a cached page without the updated background — clear all caches; (4) the image may need to be re-sized or re-uploaded if the thumbnail dimensions have changed.

Otter’s Form block uses WordPress wp_mail() for sending. Check: (1) configure WP Mail SMTP with a proper SMTP server — Otter form emails (like all WordPress emails) often end up in spam without proper SMTP; (2) in the Form block settings, verify the “Email to” field has a valid recipient email address; (3) verify the From email address in the block settings is a valid address on your domain; (4) check spam folders for the recipient; (5) test WordPress email independently using WP Mail SMTP test email function.

Otter animations use the Intersection Observer API (supported in all modern browsers). Check: (1) in the Gutenberg editor, select a block and go to the Otter → Animation panel in the block inspector — verify an animation type is selected and enabled; (2) Otter loads animation scripts only on pages where animated blocks are present — if scripts are deferred by a performance plugin, animations may not initialize correctly; (3) clear all caches; (4) test in an incognito window without browser extensions.

In the Gutenberg editor, search for “Form” in the block inserter and add the Otter Form block. The block provides a visual form builder: add fields (text, email, phone, textarea, checkbox, select) with label, placeholder, and required/optional configuration. Set the form submission behavior in the Form block settings: the To email address, success message, and whether to redirect after submission. No additional form plugin required — Otter handles form display, validation, and email sending natively within the Gutenberg editor.

Add the Otter Popup block to your page. In the Popup block settings, configure: Trigger Type → “On Scroll” with a scroll percentage of 50. Design the popup content by editing the block’s inner content area (add text, images, buttons, or any Gutenberg block). Configure the popup width, overlay color, and close button appearance. Set whether to show the popup once per session (using a cookie) to avoid repeatedly showing it to the same visitor. Otter Popup works without shortcodes — it is a native Gutenberg block that integrates with WordPress block patterns.

Spectra (Ultimate Addons for Gutenberg) offers more total blocks (40+) than Otter (20+) and has deeper WooCommerce integration in the free version. Otter is preferred for its code quality, lightweight footprint, and ThemeIsle theme integration. For sites built on the Neve or Hestia themes, Otter is the natural complement. For sites needing maximum block variety in a single free plugin, Spectra or Essential Blocks provide more options. For developers who prioritize code quality and lean implementation, Otter’s curated approach is often preferred.

Otter Blocks are Gutenberg blocks that work in the standard post/page editor. For Full Site Editing (FSE) with block themes, Otter blocks are generally usable in template editing contexts, though FSE compatibility for some advanced Otter features (Popup, animations) may vary. Check the ThemeIsle changelog for FSE compatibility updates as the block editor ecosystem continues to evolve.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.