Dynamic Template Parts vs WP Go Maps Block

Transform the way you manage templates on your WordPress site with Dynamic Template Parts. This powerful plugin extends the Full Site Editor, letting you swap headers, footers, and other Template Parts dynamically based on the content you’re editing — say goodbye to managing multiple templates for every layout variation. With Dynamic Template Parts, you gain the freedom to swap Template Parts directly within the block editor, whether it’s for posts, pages, or custom post types. The user-friendly interface allows you to preview changes in real-time, giving you complete control over the look and feel of each piece of content without needing custom code. Key Features: Dynamic Template Part Swapping: Replace headers, footers, sidebars, or any template part within the block editor. Flexible Swapping Options: Define whether to swap within the same type, any type, or curated parts. Template Part Previews: Preview Template Parts before selecting, ensuring your content looks perfect. Supports All Content Types: Works with posts, pages, and custom post types. User-Friendly Interface: Simple setup—no coding required.” Get Started: To implement an alternative Header Template Part using the Full Site Editor, please follow the example workflow below: Create an Alternative Header Template Part: Design and save a new Header Template Part within the Full Site Editor to serve as an alternative to your default header. Edit the Single Posts Template: Navigate to the Single Posts template and select the Header Template Part, and view the block sidebar. Enable the Dynamic Template Part Option: In the Template Part attributes panel, enable the Dynamic Template Part setting. Configure Swapping Preferences (Optional): Adjust your swapping preferences according to your requirements (choose to swap your Template Part with differnt Template Part types, or use a curated list of Template Parts). Edit a Post and Access the Dynamic Template Part Sidebar: Open a post for editing and select the Dynamic Template Part sidebar from the editor interface. Select the Alternative Header Template Part: Choose the alternative Header Template Part you created to replace the default header in this specific post. Save and Preview the Post: Save your changes and preview the post to verify that the alternative header is displayed correctly. Confirm Default Header on Other Posts: Ensure that all other posts without specific configurations continue to display the default header as intended. Unlock the power of dynamic templating and take control of your site’s design like never before! Hooks and Filters Dynamic Template Parts provides filters to allow developers to customise its behaviour. Below are the available filters and how to use them. Show Deselected Template Part The dynamic_template_parts_show_deselected_template_part filter lets you control whether a previously selected template part that is no longer available for selection should still be displayed. By default, the plugin keeps the part visible to avoid unintended changes, but you can override this to automatically remove unavailable template parts. Example: If you want to ensure that unavailable template parts are removed and replaced with the default template part, you can use the following code: add_filter( 'dynamic_template_parts_show_deselected_template_part', function( $show_deselected, $template_parts, $selected_part ) { // Always hide deselected template parts and fall back to the default. return false; }, 10, 3 ); Parameters: $show_deselected (bool): Whether to show the deselected template part. Defaults to true. $template_parts (array): The list of available template parts. $selected_part (string): The currently selected template part. User Permissions The dynamic_template_parts_user_can_switch filter lets you customise which users are allowed to switch template parts. By default, any user with the edit_posts capability can access this functionality, but you can restrict it to specific roles or capabilities. Example: If you want to restrict template part switching to administrators only, you can use the following code: add_filter( 'dynamic_template_parts_user_can_switch', function( $can_switch ) { // Allow only administrators to switch template parts. return current_user_can( 'manage_options' ); } ); Parameters: $can_switch (bool): Whether the current user has permission to switch template parts. Defaults to checking the edit_posts capability. Roadmap Support for additional content types: Support additional content types such as authors, terms and archive pages. Requirements WordPress version 5.8 or higher. PHP version 7.4 or higher. Known Issues See the Roadmap section for known issues.

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.