WP Travel Gutenberg Blocks vs No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor

WP Travel Gutenberg Blocks is a free plugin that integrates seamlessly with the Ultimate Travel Booking Plugin WP Travel and lets you display trips and tour packages using customizable Gutenberg blocks. You can add and arrange trip listings, images, buttons, forms, and other travel-related elements without writing code. View Documentation of WP Travel Gutenberg Blocks You will be able to completely build a new trip page, adding different blocks from the plugin. The add-on comes with a collection of ready-to-use custom blocks that are specially designed for travel agency sites. Built with simplicity in mind, you can select multiple layouts without touching a single line of code. 🌟 BLOCKS WE OFFER Slider: A Slider block can be used to create a slider of your choice. Trip Search: A Trip Search block can be used to search your trips. Trip List: A Trip List block can be used to display trips in different layouts. Trip Inquiry: A Trip Inquiry block can be used to display an inquiry form for trips. Trip Filters: A Trip Filters block can be used to filter trips based on different criteria. Breadcrumb: A Breadcrumb block can be used to display the navigation hierarchy. Trip Slider: A Trip Slider block can be used to display trips in a slider layout. Trip Featured Category: A Trip Featured Category block can be used to highlight featured trip categories. Filterable Trips: A Filterable Trips block can be used to display trips with filter options. Cart Button: A Cart Button block can be used to display the cart icon for the add-to-cart feature. Icon Picker: An Icon Picker block can be used to add and display icons. Trip Calendar: A Trip Calendar block can be used to select a date for booking a trip. Trip Categories: A Trip Categories block can be used to display trip categories or taxonomies. Trip Code: A Trip Code block can be used to display the unique code of a trip. Trip Duration: A Trip Duration block can be used to display the duration of a trip. Trip Excludes: A Trip Excludes block can be used to display excluded items from the trip. Trip Facts: A Trip Facts block can be used to display key trip information or facts. Trip FAQ: A Trip FAQ block can be used to display frequently asked questions related to the trip. Trip Gallery: A Trip Gallery block can be used to display images of the trip. Trip Group Size: A Trip Group Size block can be used to display the maximum group size. Trip Includes: A Trip Includes block can be used to display included items in the trip. Trip Map: A Trip Map block can be used to display the trip location on a map. Trip Pickup Location: A Trip Pickup Location block can be used to display the pickup location details. Trip Outline: A Trip Outline block can be used to display the itinerary outline. Trip Overview: A Trip Overview block can be used to display an overview of the trip. Trip Price: A Trip Price block can be used to display the trip price. Trip Rating: A Trip Rating block can be used to display trip ratings. Trip Review: A Trip Review block can be used to display a review summary or count. Trip Review List: A Trip Review List block can be used to display a list of reviews. Trip Tabs: A Trip Tabs block can be used to display trip content in a tabbed layout. Trip Timespan: A Trip Timespan block can be used to display trip duration and timing details. Trip Wishlists: A Trip Wishlists block can be used to display a wishlist option for trips. Trip Sale: A Trip Sale block can be used to display discounted or sale prices. Trip Departure: A Trip Departure block can be used to display departure dates or details. Trip Downloads: A Trip Downloads block can be used to display downloadable files for the trip. Trip Custom Content: A Trip Custom Content block can be used to display custom content sections. Trip Date Countdown: A Trip Date Countdown block can be used to show a countdown timer for trip start dates. Booking Close Countdown: A Booking Close Countdown block can be used to show the booking closing time countdown. WhatsApp Inquiry: A WhatsApp Inquiry block can be used to allow users to send inquiries via WhatsApp. Trip Button: A Trip Button block can be used to link to a specific trip page. Book Button: A Book Button block can be used to display a “Book Now” button. Trip Guide List: A Trip Guide List block can be used to display a list of guides. Guide Image: A Guide Image block can be used to display the guide’s image. Guide Full Name: A Guide Full Name block can be used to display the guide’s name. Guide Contact Number: A Guide Contact Number block can be used to display the guide’s phone number. Guide Email: A Guide Email block can be used to display the guide’s email address. Guide Country: A Guide Country block can be used to display the guide’s country. Guide City: A Guide City block can be used to display the guide’s city. Guide Age: A Guide Age block can be used to display the guide’s age. Guide Join Year: A Guide Join Year block can be used to display the year the guide joined. Guide Language: A Guide Language block can be used to display the languages spoken by the guide. Guide Gender: A Guide Gender block can be used to display the guide’s gender. Guide Social Link: A Guide Social Link block can be used to display social media links. Guide Slogan: A Guide Slogan block can be used to display the guide’s slogan or tagline. Guide Short Description: A Guide Short Description block can be used to display a short introduction. Guide Biography: A Guide Biography block can be used to display the full biography of the guide. Guide Featured Trip: A Guide Featured Trip block can be used to display trips assigned to the guide. Guide Review: A Guide Review block can be used to display reviews for the guide. Guide Review Form: A Guide Review Form block can be used to submit reviews for the guide. Guide Code: A Guide Code block can be used to display the guide’s unique code. Trip Extra Description: A Trip Extra Description block can be used to display extra details. Trip Extra Price: A Trip Extra Price block can be used to display pricing for extra services. Trip Extra Gallery: A Trip Extra Gallery block can be used to display additional images. Note With the release of WP Travel Block v3.0.0, we have added a separate plugin for the Elementor widgets as WT Widgets for Elementor. FREE TRAVEL THEMES COMPATIBLE WITH WP TRAVEL GUTENBERG BLOCKS PLUGIN WENS Adventure by WP Travel Travelin by WP Travel WP Yatra by WP Travel Travelaero by WP Travel Travel Knock by WP Travel Travel Solution by WP Travel Travelyo by WP Travel Travel Mates by WP Travel Triphub by WP Travel Trovity by WP Travel Travo Nomad by WP Travel Advantura Trails by WP Travel WP Travel FSE by WEN Solutions Travelvania by WEN Solutions WENS Travel Expanse by WEN Solutions WENS Explore Ease by WEN Solutions WENS Trails by WEN Solutions WENS Travel by WEN Solutions WENS Wander by WEN Solutions Wens TravelGo by WEN Solutions WENS Track by WEN Solutions WENS Travel Next by WEN Solutions WENS Travel Studio by WEN Solutions WENS TravelX by WEN Solutions WENS Travel Joy by WEN Solutions WENS Explore Ease Lite by WEN Solutions Travel FSE by Eagle Themes 📝 RELEASE NOTES Before updating the plugin, please check “Our latest release notes”. 🔁 REQUIRED PLUGINS WP Travel 🌍 WP Travel WP Travel is the optimal choice among the WordPress Travel Booking Plugins and Tour Operators to Create Travel and Trekking Websites in Minutes, Without Coding! If you are looking for a reliable travel plugin for your WordPress travel booking website, then look no further than the WP Travel plugin. It’s a powerful, free travel engine (also available in a Pro version with additional features) for creating customized travel agency or tour operator websites on WordPress in minutes. The plugin is useful for travel agencies, tour operators, or anyone looking to build a travel-focused site with features like booking forms, itineraries, and customer management. View: Demo of Best Travel & Tour plugin | Modules | Best Travel & Tour Themes | Documentations | Video Tutorials How to Create a Travel Booking Website Without Coding Using the WP Travel plugin? 💁‍♂️ Dedicated Support We have an entire team of happy, smart engineers ready to help you. You can easily ask your questions in support forum. ❤️ Love WP Travel? We are doing our best from our side to help and provide support as soon as we can. Join our Facebook Community group Like our Facebook Page Follow us on LinkedIn Page Subscribe to our Youtube Channel Follow us on Instagram Find us on Pinterest

The most configurable way to leave the block editor behind. Activate it and everything block related is gone: the block editor, Global Styles, patterns, block widgets, the Site Editor and the block CSS and JavaScript that every page loads. From there you decide the scope: everywhere, or only for the post types, roles, templates and entries you choose. What this plugin removes: Core Gutenberg Features Gutenberg Block Editor (completely disabled) Full Site Editing (FSE) Global Styles and inline CSS Block-based Widget Editor (reverts to Classic Widgets) Block Patterns and Pattern Directory Theme.json support and processing Block Directory integration Site Editor functionality Performance Optimizations The block library CSS and JavaScript that every page loads The Global Styles inline CSS, which dequeuing the handle never reaches The block assets of any other plugin that registers blocks, on pages where no block appears The block editor assets in the admin, wherever the Classic Editor is the one opening WooCommerce Integration The block based product editor, which follows the same rules as any other post type The WooCommerce block styles and scripts, removed along with the rest of the block assets Nothing else: leave blocks on for products and the block product editor keeps working Admin Experience Removes the welcome panel that promotes the block editor Removes the Patterns submenu from the Appearance menu (WP 6.5+) Removes the Fonts submenu from the Appearance menu (WP 7.0+) Blocks access to Site Editor pages Shows activation success notice Warns you when a block theme is active Adds settings and support links to plugin actions A default that asks nothing, and a settings page for everything else – Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that. Full control when you need it – The settings page lives under Settings > No Gutenberg?, built around one master switch. Leave it on and the whole site keeps the complete disable. Turn it off and you decide where the block editor goes away: by post type, by user role, by page template or by individual entry. The site wide pieces (classic widgets, block patterns, frontend block assets, theme.json and the Site Editor) are then yours to keep or remove one by one. Every checkbox means the same thing, so no setting ever undoes another one. Switch editors entry by entry, where it makes sense – Editor switching is chosen per post type, right next to the rule that disables the block editor. Enable it for pages, for instance, and every page gets “Edit (Classic)” and “Edit (Blocks)” links in the list plus a switch inside both editors, while your posts stay untouched. Each entry remembers the editor chosen for it, and that choice beats the rules in both directions: one landing page can stay on the Classic Editor while the rest keep blocks, or the other way around. It tells you what it is doing – The settings screen opens with a status panel for your particular site: how many block patterns are being blocked, how much weight is off every page, whether your theme is a block theme, and how much of your published content is really built with blocks. That last number is the one that should decide whether you strip the block styles from the frontend or not, and no other plugin tells you. Built for agencies and managed sites – The whole configuration can be fixed from wp-config.php, and the settings screen locked as read only or hidden altogether, so a site you deliver keeps the setup you left behind. A whole network configured in one file – This is where the plugin stands alone. Every single setting it has, and not just which editor opens, can be written in wp-config.php, the same file every site of a multisite network reads. A network of a hundred sites is set up once, all of them with the same rules, all of them with the same block CSS gone, and none of them able to drift away from it. The plugin can also be network activated and left alone, because settings are stored per site, so a network can equally let each site decide for itself. Same mechanism as the locking above, and this is how it is written. One configuration for a whole network, or for a site you deliver Everything the settings screen does can also be written in wp-config.php, where nobody changes it by accident, and what you write there wins over whatever is stored in the database. It is the same file for every site of a multisite network, so it is also how you set up a network without repeating the configuration site by site. Add the lines you need above the comment that says “That’s all, stop editing! Happy publishing.” To disable Gutenberg everywhere and leave no settings screen for anyone to touch, which is the usual setup both for a network and for a site you hand over to a client: define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => true ) ); define( 'NO_GUTENBERG_HIDE_SETTINGS', true ); Drop that second line and the settings page is still there, showing the configuration the site is really running, but read only. And if all you want is to lock the screen, leaving the configuration as each site has it stored: define( 'NO_GUTENBERG_LOCK_SETTINGS', true ); NO_GUTENBERG_OPTIONS takes any of the settings on the screen, so a selective setup is written the same way: define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => false, 'disable_post_types' => array( 'post', 'page' ), 'disable_roles' => array( 'editor', 'author' ), 'frontend_css' => false, ) ); The keys are the settings on the screen. complete, widgets, patterns, frontend_css, theme_json, site_editor and fse_notices take true or false, while disable_post_types, disable_roles, disable_templates and switch_post_types take an array of slugs, and disable_ids an array of entry IDs. Any key you leave out keeps the value stored on the site. Note that defining NO_GUTENBERG_OPTIONS already turns the whole screen read only, so NO_GUTENBERG_LOCK_SETTINGS is not needed on top of it. It fits sites that: – Work better in the Classic Editor and want it back – Run classic themes and plugins that were never built around blocks – Are paying for block CSS and JavaScript on pages with no blocks in them – Need the Classic Editor for everyone except a few post types, roles or people – Are a multisite network that wants the same editing experience on every site Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.