MakeITeasy Popup
Need popups to grab your users’ attention? Marketing call-to-actions that open on scroll, timer, click, matched referer, hover, or exit intent? Multiple popups on one page? This plugin has it all. It provides styling consistent with core block editor blocks plus additional features. Why choose Makeiteasy Popup? ▶️ Unlike some other plugins, Makeiteasy Popup integrates seamlessly with WordPress, feeling like a native, built-in WP block. It’s lightweight and self-sufficient, without the heavy burden of a large blocks library. It relies on a single tiny dependency – micromodal.js – with a combined total of only 10 kB of JavaScript❕ 👆 Try demo – there is a “Live preview” button on the top of this page 👆 ❗ Sometimes “Live preview” does not start due to slower responds of servers with resources. If progress stops with black screen or progress indicator does not advance anymore (loading should be finished at max 30 seconds) – in that case please refresh the page in browser. Key Features 🥇 Feature-Rich and free. 🥈 Fully Open Source: Including the block source code. Fork and adjust as needed. 🥉 Developer friendly: Hooks for modifications and unopinionated starting CSS. ⏲️ Future-Proof Compatibility: Guaranteed compatibility with future WordPress versions. 🆕 Added “open on exit intent” feature. It works only on desktop. When popup is set up to open on exit intent and user moves mouse outside the top border of the browser inner window (screen), popup appears. User can choose when feature is activated (after how many seconds since page was loaded), so popup can’t open too early. ⏱️❗Queue if another popup is opened, popup is placed in queue and opened upon closing the former. Known limitations Currently, opening several modal popups simultaneously is impossible due to the limitations of the Micromodal.js library. Future versions will replace this library with the native Dialog HTML element, including automatic migration for existing popups. Block options The block sidebar provides many options, most of which function similarly to other blocks. Notable options include: – Opening time selector: See the detailed section below. – Layout type: Floating, Fixed, Attached – Popup Enabled: Temporarily hide the popup without deleting it. – Open on interval: Open on given interval in days. – Open on matching referer: Open if the user’s referral URL matches. Layout Types Floating: popup floats above content. Clicking on area outside popup closes it. Fixed: popup is “fixed” to one of sides of screen — top, bottom, right, left Attached: popup is attached to element on screen. When user scrolls, it moves with it. Modality Modal: popup blocks everything else on screen, scrolling is not possible, popup can be closed by clicking outside of popup Modeless: popup is non-blocking, user can scroll, popup can’t be closed by clicking outside of popup Developers Github repository https://github.com/Lovor01/makeiteasy-popup Changing the Close button Using Javascript: import { ReactComponent as CloseIcon } from '../assets/close-x.svg'; addFilter( 'makeiteasy-closeButtonIcon', 'makeiteasy/makeiteasy-popup/close-icon', () => ( ) ); If you customize button this way and you already have posts(or pages) with popup block, on post reopening the message “This block contains unexpected or invalid content.” will be presented. In such case choose “Attempt to repair block” and if it looks good, save post. Using PHP: add_action( 'render_block_makeiteasy/popup', function($content) { $svg = file_get_contents( __DIR__ . '/path_to_file/close-button-dark.svg' ); return preg_replace( '~( ).*( )~m', "$1$svg$2", $content ); } ); Attaching Code to Modal Events Custom events ‘makeiteasy/openModal’ and ‘makeiteasy/closeModal’ are fired on modal open and close. Events fire on modal itself, DOM element with class .wp-block-makeiteasy-popup.
Top keywords
- popup20×3.45%
- open10×1.73%
- block9×1.55%
- makeiteasy5×0.86%
- modal5×0.86%
- screen5×0.86%
- user5×0.86%
- blocks4×0.69%
- content4×0.69%
- outside4×0.69%
- page4×0.69%
- popups4×0.69%
WP Go Maps Block
The easiest to use Google Maps and Open Layers Map Plugin is now available as a standalone map block! Create a custom map block with high-quality markers and add them to your WordPress posts and pages effortlessly. Perfect for contact pages, business locations, event venues, and more! Map blocks are lightweight and deliver optimal performance, ensuring a seamless experience for your WordPress site. They’re easy to customize, allowing you to quickly add and configure maps to suit your needs without compromising site speed or performance. If you need more features like multiple markers, shapes, and a store locator, our full (free) WP Go Maps plugin might be perfect for you. Block Features Add unlimited map blocks to your posts/pages Choose between Google Maps or OpenLayers for each block Edit your marker directly from the block editor Set marker location by free location search, or by right-clicking on the map preview Preview your map in real time, within the block editor Easy to use and customize without any coding experience Control width, height and alignment of your maps From the team that brought you the most popular Google Maps plugin on WordPress Lightweight for optimal performance No database queries or tables Basic info-window for your marker Control zoom level of your map Support for localization Latest Google Maps API Latest OpenLayers API Already using WP Go Maps? You can still use this block for single locations, as it is fully integrated with both our basic and Pro versions! References We make use of a various libraries and 3rd party service providers in order to render maps in your preferred mapping engine. This section will describe each of these in more detail and when they are used. OpenLayers: Served from a local library file (lib/ol.js & lib/ol.css), provided by OpenLayers. We use this library when you set your block to use OpenLayers (default). You can find the source files on the OpenLayers GitHub. OpenStreetMap: When you select the OpenLayers engine, a default map tile server is used, which is provided by OpenStreetMap. This is a 3rd party service provider that we rely on to render your map. They may also make use of MapBox for some of their assets. Google Maps API: If you decide to use Google Maps as your map engine, we will include the Google Maps API as a 3rd party service provider that we rely on to render your maps. In this case, admin map previews are still rendered by OpenLayers and OpenStreetMap. Nominatim (OpenStreetMap): If you perform an address search within the admin area, we will make use of the OpenStreetMap Nominatim to lookup locations and suggest addresses to you. This is a 3rd party service provider that we rely on for address searches.
Top keywords