{"id":374819,"date":"2026-09-24T11:50:18","date_gmt":"2026-09-24T11:50:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/flx-modernize\/"},"modified":"2026-11-15T21:17:06","modified_gmt":"2026-11-15T21:17:06","slug":"flx-modernize","status":"publish","type":"plugin","link":"https:\/\/he.wordpress.org\/plugins\/flx-modernize\/","author":161177,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.14.0","stable_tag":"1.14.0","tested":"7.1.4","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Flx Modernize","header_author":"Rickey Gu","header_description":"Adds a sale-savings badge (\"Save NN%\") to supported WooCommerce product pages, computed locally from each product's own regular\/sale price -- no external service required. Optionally, an experimental external Flx Render integration can also be configured; native WooCommerce rendering is always the fallback. Manage both under Settings > Flx Modernize.","last_updated":"2026-11-15 21:17:06","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/modernize.flexplat.com\/","header_author_uri":"https:\/\/github.com\/rickey29","rating":0,"author_block_rating":0,"active_installs":0,"downloads":1087,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.0.2":{"tag":"0.0.2","author":"rickey29","date":"2026-09-24 11:49:53","revision":3711211},"1.0.0":{"tag":"1.0.0","author":"rickey29","date":"2026-10-29 18:05:41","revision":3773722},"1.1.0":{"tag":"1.1.0","author":"rickey29","date":"2026-10-31 22:38:30","revision":3777401},"1.10.0":{"tag":"1.10.0","author":"rickey29","date":"2026-11-09 19:33:11","revision":3793151},"1.11.0":{"tag":"1.11.0","author":"rickey29","date":"2026-11-12 15:13:12","revision":3798624},"1.12.0":{"tag":"1.12.0","author":"rickey29","date":"2026-11-14 21:07:10","revision":3802478},"1.13.0":{"tag":"1.13.0","author":"rickey29","date":"2026-11-15 00:59:46","revision":3802616},"1.14.0":{"tag":"1.14.0","author":"rickey29","date":"2026-11-15 21:17:06","revision":3803889},"1.2.0":{"tag":"1.2.0","author":"rickey29","date":"2026-11-01 18:20:46","revision":3778404},"1.3.0":{"tag":"1.3.0","author":"rickey29","date":"2026-11-01 20:25:17","revision":3778533},"1.4.0":{"tag":"1.4.0","author":"rickey29","date":"2026-11-01 23:36:34","revision":3778648},"1.5.0":{"tag":"1.5.0","author":"rickey29","date":"2026-11-02 00:47:30","revision":3778747},"1.6.0":{"tag":"1.6.0","author":"rickey29","date":"2026-11-03 13:26:58","revision":3781908},"1.7.0":{"tag":"1.7.0","author":"rickey29","date":"2026-11-04 20:12:22","revision":3784718},"1.8.0":{"tag":"1.8.0","author":"rickey29","date":"2026-11-05 19:02:43","revision":3786593},"1.8.1":{"tag":"1.8.1","author":"rickey29","date":"2026-11-06 18:44:30","revision":3788556},"1.8.2":{"tag":"1.8.2","author":"rickey29","date":"2026-11-08 13:40:46","revision":3791051},"1.9.0":{"tag":"1.9.0","author":"rickey29","date":"2026-11-08 14:53:22","revision":3791119}},"upgrade_notice":[],"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.0.2","1.0.0","1.1.0","1.10.0","1.11.0","1.12.0","1.13.0","1.14.0","1.2.0","1.3.0","1.4.0","1.5.0","1.6.0","1.7.0","1.8.0","1.8.1","1.8.2","1.9.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[76538,141196,129329,17455,289553],"plugin_category":[45],"plugin_contributors":[153307],"plugin_business_model":[],"class_list":["post-374819","plugin","type-plugin","status-publish","hentry","plugin_tags-elementor","plugin_tags-headless","plugin_tags-nodejs","plugin_tags-rendering","plugin_tags-twenty-twenty-five","plugin_category-ecommerce","plugin_contributors-rickey29","plugin_committers-rickey29"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/flx-modernize.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Flx Modernize sends the content of a page to a Flx Render service, a Node.js app, which returns the finished HTML page in your theme's look. WordPress keeps handling each request, so its hooks and plugins keep running. If the Render service is unavailable, WordPress renders the page itself.<\/p>\n\n<p>This release supports sites using the <strong>Twenty Twenty-Five<\/strong> theme. A Twenty Twenty-Five renderer package is available from <a href=\"https:\/\/modernize.flexplat.com\/downloads\/\">modernize.flexplat.com<\/a>; you can run it yourself or have it hosted for you. Sites on the <strong>Hello Elementor<\/strong> theme can serve pages built with the free <strong>Elementor<\/strong> plugin; see \"Elementor\" below. WooCommerce stores on the <strong>Storefront<\/strong> or <strong>Astra<\/strong> theme can opt in as well; see \"WooCommerce stores\" below.<\/p>\n\n<h4>See it in 60 seconds<\/h4>\n\n<p>https:\/\/youtu.be\/1qbbvq67eu8<\/p>\n\n<p>The same WordPress page with Contact Form 7 and a jQuery lightbox, first in a typical Next.js + REST API front end, then rendered by Node.js with Flx Modernize. Try it yourself on the <a href=\"https:\/\/twenty-twenty-five.flexplat.com\/plugin-demo\/\">plugin demo page<\/a> (visit it logged out).<\/p>\n\n<h4>What is rendered through Flx<\/h4>\n\n<ul>\n<li>The blog home page, category and tag archives<\/li>\n<li>Single posts and pages<\/li>\n<li>Search results<\/li>\n<li>The \"Page not found\" (404) page, still sent with a real 404 status<\/li>\n<\/ul>\n\n<p>The theme's header with its menu, and its footer, appear on every one of these pages. What your plugins print in the page head and footer carries over too: the title, SEO tags (for example from Yoast SEO), structured data and scripts such as analytics. So do plugin styles, and plugin scripts together with the WordPress scripts they need, such as jQuery.<\/p>\n\n<h4>What always stays normal WordPress<\/h4>\n\n<ul>\n<li>Anyone who is logged in (administrators and editors always see normal WordPress). A WooCommerce store can let logged-in customers have its catalogue pages; see \"WooCommerce stores\" below<\/li>\n<li>Previews, drafts, private, scheduled and password-protected content<\/li>\n<li>Feeds, embeds, robots.txt, trackbacks and any request other than GET or HEAD<\/li>\n<li>Visitors who have commented (WordPress's comment cookies), and reply or \"awaiting moderation\" links, so they see their own pending comment and a filled-in form<\/li>\n<li>With WooCommerce active: the shop, product pages, product categories and tags, the cart, checkout and My account pages, product search and WooCommerce's own requests; visitors with something in their cart; and the whole site while WooCommerce's \"Coming soon\" mode is on. A store that opts in changes some of this; see \"WooCommerce stores\" below<\/li>\n<li>Page types your Render service does not offer: when it answers that it has no such page type, WordPress serves that type for the next hour without asking again<\/li>\n<\/ul>\n\n<h4>Elementor<\/h4>\n\n<p>Pages built with Elementor on the Hello Elementor theme go through Flx when they use the \"Elementor Full Width\" or \"Elementor Canvas\" template, with Elementor's own markup, styles and scripts. It needs Hello Elementor 3.5 (not a child theme) with the free Elementor plugin 4.3, the versions this release was tested with, and a Render service built for the site; there is no Elementor renderer package to download.<\/p>\n\n<ul>\n<li>Everything else on such a site stays normal WordPress: posts, archives, search, other page templates and WooCommerce store pages.<\/li>\n<li>With Elementor Pro, a Hello child theme, or other Elementor or Hello versions, the whole site stays normal WordPress.<\/li>\n<li>If the Render service fails, the normal WordPress page is served with all of Elementor's styles.<\/li>\n<\/ul>\n\n<h4>WooCommerce stores<\/h4>\n\n<p>Off unless a site opts in: on the Flx Modernize screen (WooCommerce \u2192 Store pages), or with the constant <code>FLX_MODERNIZE_WOOCOMMERCE<\/code> in <code>wp-config.php<\/code>. It needs the Storefront theme, or the Astra theme (4.14, without a child theme), and a Render service that draws that theme: the Storefront renderer package, or an Astra renderer built for your site. Any other theme, or a theme or WooCommerce template this release wasn't reviewed against, stays normal WordPress.<\/p>\n\n<ul>\n<li>The shop, product categories and tags, products and Storefront's home page go through Flx, for visitors with or without something in their cart.<\/li>\n<li>On Astra, the store's pages on the default page template go through Flx as well; other page templates, posts, archives and search stay normal WordPress. Astra's header and footer come from WordPress, as your header and footer builder prints them. Every visitor gets the same page, built with an empty cart, and WooCommerce's own scripts fill in the visitor's cart in the browser. No cart or customer data is sent to the Render service.<\/li>\n<li>A further constant, <code>FLX_MODERNIZE_WOOCOMMERCE_SHELL<\/code>, puts the site's header and footer from the Render service around the Cart and a guest's My account page, and <code>FLX_MODERNIZE_WOOCOMMERCE_SHELL_CHECKOUT<\/code> does the same for Checkout. WordPress fills in these pages on your own server, so their contents are never sent. What comes from the Render service for these pages must pass a strict check, built on WordPress 6.9's output buffer: no scripts and no forms. If it doesn't pass, or on older WordPress, these pages stay normal WordPress. If you take real payments, ask your payment provider or assessor before turning on Checkout.<\/li>\n<li>Logged-in customers stay normal WordPress, unless the store also sets <code>FLX_MODERNIZE_LOGGED_IN_CUSTOMERS<\/code>. Then they get the same catalogue pages as a guest, built the same way with nothing about them sent; WordPress marks the page as logged in and hides the review form's name and email fields, which come from their account; on Astra it also puts the customer's own account link or avatar in the header. These changes are made on your server. Everything else stays normal WordPress for them, and anyone who can edit content or run the store always does. Leave it off if your prices or products differ per customer (memberships, wholesale or role-based prices).<\/li>\n<li>Order pages, product search and sorted or filtered lists always stay normal WordPress.<\/li>\n<\/ul>\n\n<h4>Safety<\/h4>\n\n<ul>\n<li>Only anonymous visitors get Flx pages (and, on a store that turns it on, logged-in customers on catalogue pages), and the page data is always built as an anonymous visitor.<\/li>\n<li>No visitor data is sent to the Render service: no cookies, no user account and no query-string values. The one exception is the words a visitor searches for, because the search results page shows them.<\/li>\n<li>Requests to the Render service can be signed with a key only your site holds; a Render service in enforce mode rejects anything else.<\/li>\n<li>Flx pages are sent with <code>Cache-Control: private, no-store<\/code>, unless you turn on edge caching (below). A page served by WordPress because the Render service failed is always sent with <code>no-store<\/code>.<\/li>\n<li>If the Render service fails after a page was started, the normal page is fetched fresh from your own site, as the same visitor, so nothing the plugin did while preparing the page can change it. If your server cannot reach its own address, WordPress serves the page directly, as in earlier versions. Setting <code>FLX_MODERNIZE_LOOPBACK_FALLBACK<\/code> to <code>false<\/code> in <code>wp-config.php<\/code> turns the fresh fetch off.<\/li>\n<li>Deactivating the plugin instantly returns the whole site to normal WordPress.<\/li>\n<\/ul>\n\n<h4>Edge caching (optional)<\/h4>\n\n<p>Off by default. Set an edge cache time on the Flx Modernize screen, or add <code>define( 'FLX_MODERNIZE_EDGE_TTL', 300 );<\/code> to <code>wp-config.php<\/code> (seconds, 60 to 3600), and Flx pages that are the same for every visitor can be stored by your CDN: pages, single posts, the blog home page and category and tag archives, requested without a query string. They are sent <code>Cache-Control: public, max-age=0, s-maxage=&lt;TTL&gt;<\/code>. Search results, the 404 page, URLs with a query string, fallback pages and everything WordPress renders itself (logged-in users, previews, password-protected content) are never cached.<\/p>\n\n<p>With a Cloudflare zone ID and API token (a token that can only purge cache) also set, on the screen or as <code>FLX_MODERNIZE_CLOUDFLARE_ZONE_ID<\/code> and <code>FLX_MODERNIZE_CLOUDFLARE_API_TOKEN<\/code>, the plugin clears your site from Cloudflare's cache after any change that can show on a page. Your CDN must be set to follow the origin's <code>Cache-Control<\/code> header; the documentation at modernize.flexplat.com shows the Cloudflare Cache Rule.<\/p>\n\n<p>Cached pages also get a <code>Cloudflare-CDN-Cache-Control<\/code> header with the same time plus <code>stale-while-revalidate<\/code>, so when a cached copy runs out Cloudflare can serve it once more while it fetches a fresh one, and no visitor waits. A purge still removes the copy at once. The window is one hour for pages and posts when the Cloudflare purge is set up (the edge cache time without it), and 60 seconds for store pages. A failed purge is tried once more about 30 seconds later, and changing the edge cache time or the Cloudflare settings clears the cache. The <code>flx_modernize_stale_while_revalidate<\/code> filter changes it (0 turns it off). Other CDNs ignore this header.<\/p>\n\n<p>For a WooCommerce store that opted in, <strong>Store pages in the edge cache<\/strong> (on the screen, or <code>define( 'FLX_MODERNIZE_STORE_EDGE_CACHE', true );<\/code>) also lets your CDN store the Flx shop, product category, tag and product pages, for at most 5 minutes whatever the edge cache time. It needs the Cloudflare zone ID and token, so that changes clear the cache. Cart, Checkout and My account, shoppers with something in their cart and logged-in customers are never cached. Stock, sale and tax rate changes, new paid orders and saved WooCommerce settings also clear the cache, about 30 seconds later and once for several changes, so a checkout never waits for it (WP-Cron must run; if it doesn't, pages refresh when the 5 minutes end). Store pages are not cached while WooCommerce geolocates visitors (Default customer location). Your CDN must skip its cache for visitors with the cookies <code>woocommerce_items_in_cart<\/code>, <code>woocommerce_cart_hash<\/code> and <code>wp_woocommerce_session_*<\/code>. Leave it off if a plugin shows prices, currency or products per visitor, or return <code>false<\/code> from the <code>flx_modernize_store_route_cacheable<\/code> filter.<\/p>\n\n<h4>For developers<\/h4>\n\n<p>The <code>flx_modernize_should_render<\/code> filter lets you turn Flx off for a request (return <code>false<\/code>). It can never turn Flx on for a logged-in user.<\/p>\n\n<p>The <code>flx_modernize_head_footer_output<\/code> filter turns off the head and footer output (return <code>false<\/code>).<\/p>\n\n<p>Documentation and a step-by-step tutorial for building a renderer for a theme are at <a href=\"https:\/\/modernize.flexplat.com\/\">modernize.flexplat.com<\/a>.<\/p>\n\n<h3>External Services<\/h3>\n\n<p>Flx Modernize works by sending page data to an external <strong>Flx Render service<\/strong> over HTTPS and displaying the HTML it returns.<\/p>\n\n<ul>\n<li><strong>Which service:<\/strong> the one whose URL an administrator enters on the Flx Modernize settings screen. It can be your own self-hosted instance (the renderer package is GPL-licensed open source) or one hosted for you. There is no default: until a Render URL is saved, the plugin sends nothing anywhere and WordPress renders every page normally.<\/li>\n<li><strong>When data is sent:<\/strong> only when an anonymous visitor requests a page that Flx renders (see the lists above), and when an administrator clicks <strong>Test connection<\/strong> on the settings screen (a health check and one signed request with no page content). A store using the optional header and footer around Cart, Checkout or My account also sends the site's shared parts in a background request from the site itself, about every 5 minutes while those pages are visited; nothing about the visitor or those pages' contents is in it.<\/li>\n<li><strong>What is sent:<\/strong> the content needed to draw that page: title, content, excerpt, slug and permalink; publish and modified dates and author display name; featured image URL, size and alt text; site name, home URL and site language; the header menu's labels and links; links to the site's own theme CSS (which the Render service then fetches from your site); for archives and search, the list of posts and paging; for posts, the author's archive link, the post's categories and tags, the previous and next posts (title and link), the four latest posts for the theme's \"More posts\" list, and the comments section as WordPress renders it for an anonymous visitor (approved comments with their author names, avatars and links, and the empty reply form); for search, the search words and the four latest posts (title, link and date) for the theme's \"More posts\" list; the SEO tags, structured data (JSON-LD) and scripts that your plugins print in the page head and footer, captured as an anonymous visitor without cookies (WordPress's own styles and scripts are left out). The filter <code>flx_modernize_head_footer_output<\/code> turns this off. The filter <code>flx_modernize_comments_html<\/code> can change or remove the comments section.<\/li>\n<li><strong>What a WooCommerce store that opted in also sends, for catalogue pages:<\/strong> the page's middle as WooCommerce prints it (product descriptions, prices, stock, reviews with their authors' names and avatars, related products and sidebar widgets); each product's name, link, type, SKU, prices, stock, rating, review count, image and add-to-cart link; the site's tagline and logo, its menus, its account, cart and privacy links, Storefront's hook and widget output, and the page's body classes; on Astra, Astra's header, footer and other theme hook output as Astra prints them for an anonymous visitor, the page's body and container attributes and, for the store's pages, the page's middle as Astra prints it; and everything WordPress prints in the page head and footer, including styles and scripts, apart from the charset and viewport tags.<\/li>\n<li><strong>What the optional header and footer around Cart, Checkout and My account send:<\/strong> the site's name, tagline, logo and home URL, its menus, its account, cart and privacy links, the header's style, the breadcrumb, footer widgets and Storefront's hook output around the header and footer. No page content or head and footer output.<\/li>\n<li><strong>What is never sent:<\/strong> visitor cookies, IP addresses, user accounts, email addresses, passwords or other query-string values. For a store, nor is the visitor's cart or customer data. A plugin can still print something on a catalogue page that depends on the visitor, such as a price or currency chosen from their location; that output is part of the page, so check such plugins before opting in.<\/li>\n<\/ul>\n\n<p><strong>Cloudflare API (optional).<\/strong> Only when an administrator has turned on edge caching and set a Cloudflare zone ID and API token, on the Flx Modernize screen or in <code>wp-config.php<\/code>: after a change that can alter public pages (for example a post published or a menu saved), the plugin asks Cloudflare to clear its cache for the site's host name. It sends the zone ID, the token (as the <code>Authorization<\/code> header) and the site's host name to <code>api.cloudflare.com<\/code>; nothing about visitors is sent. Without them the plugin never contacts Cloudflare. Cloudflare's <a href=\"https:\/\/www.cloudflare.com\/terms\/\">terms<\/a> and <a href=\"https:\/\/www.cloudflare.com\/privacypolicy\/\">privacy policy<\/a> apply.<\/p>\n\n<p>The Render service is operated by whoever hosts it: you, or the provider you choose. When the hosting is provided by Flx (Rickey Gu), the terms are agreed with you directly; see <a href=\"https:\/\/modernize.flexplat.com\/\">modernize.flexplat.com<\/a>.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate Flx Modernize from the Plugins screen.<\/li>\n<li>Set up a Flx Render service for your theme (see <a href=\"https:\/\/modernize.flexplat.com\/downloads\/\">modernize.flexplat.com<\/a>), or have one hosted for you.<\/li>\n<li>Go to <strong>Flx Modernize<\/strong> in wp-admin and click <strong>Generate signing key<\/strong>. Copy the value it shows (once) into your Render service's <code>FLX_RENDER_SIGNING_KEYS<\/code> setting.<\/li>\n<li>Enter the Render service URL and save.<\/li>\n<li>Click <strong>Test connection<\/strong>: it tells you whether the Render service is reachable and accepts the key, and what to fix if not.<\/li>\n<li>Visit your site while logged out: pages are now served through Flx. While logged in you keep seeing normal WordPress.<\/li>\n<\/ol>\n\n<p>Every setting can also be defined in <code>wp-config.php<\/code> instead (see the documentation); a constant takes priority, and the screen then shows that setting read-only. A secret saved on the screen is stored in the WordPress database; <code>wp-config.php<\/code> keeps it out of the database.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"which%20themes%20are%20supported%3F\"><h3>Which themes are supported?<\/h3><\/dt>\n<dd><p>Twenty Twenty-Five; Hello Elementor, for pages built with the free Elementor plugin (see \"Elementor\" above); and, for WooCommerce stores that opt in, Storefront and Astra. Each theme needs a renderer that knows its design; the tutorial at modernize.flexplat.com shows how one is built.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20the%20render%20service%20is%20down%3F\"><h3>What happens if the Render service is down?<\/h3><\/dt>\n<dd><p>WordPress renders the page itself, automatically, and sends it with <code>Cache-Control: no-store<\/code> so the fallback page is not cached.<\/p><\/dd>\n<dt id=\"why%20do%20i%20still%20see%20normal%20wordpress%3F\"><h3>Why do I still see normal WordPress?<\/h3><\/dt>\n<dd><p>Because you are logged in. Flx serves anonymous visitors only. Open the site in a private window to see the Flx pages.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20page-cache%20plugins%3F\"><h3>Does it work with page-cache plugins?<\/h3><\/dt>\n<dd><p>Flx pages tell page-cache plugins not to store them (<code>DONOTCACHEPAGE<\/code>) and send <code>Cache-Control: private, no-store<\/code>. To cache Flx pages at your CDN instead, turn on edge caching (see the Description).<\/p><\/dd>\n<dt id=\"which%20menus%20are%20supported%3F\"><h3>Which menus are supported?<\/h3><\/dt>\n<dd><p>The header menu, with custom, page, post and category links, and sub-menus up to three levels deep (they open on hover and keyboard focus).<\/p><\/dd>\n<dt id=\"does%20it%20need%20woocommerce%3F\"><h3>Does it need WooCommerce?<\/h3><\/dt>\n<dd><p>No. On a site with WooCommerce, your pages and posts are served through Flx as usual, while the store (shop, products, cart, checkout and My account) and shoppers with something in their cart get normal WordPress, unless the site opts in; see \"WooCommerce stores\" above.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.14.0<\/h4>\n\n<ul>\n<li>New: with edge caching on, Cloudflare can now serve a cached page for a while after its edge cache time ends while it fetches a fresh one in the background (<code>Cloudflare-CDN-Cache-Control<\/code> with <code>stale-while-revalidate<\/code>), so no visitor waits for an expired copy. A purge still removes the copy at once.<\/li>\n<li>The window is one hour for pages and posts when the Cloudflare purge is set up (the edge cache time without it) and 60 seconds for store pages. The new <code>flx_modernize_stale_while_revalidate<\/code> filter changes it (0 turns it off). <code>Cache-Control<\/code> is unchanged, and other CDNs ignore the new header.<\/li>\n<li>A failed Cloudflare purge is now tried once more about 30 seconds later, and changing the edge cache time or the Cloudflare settings clears the cache.<\/li>\n<\/ul>\n\n<h4>1.13.0<\/h4>\n\n<ul>\n<li>New for WooCommerce stores: <strong>Store pages in the edge cache<\/strong> (Edge caching section, or <code>FLX_MODERNIZE_STORE_EDGE_CACHE<\/code>). The shop, product category, tag and product pages that Flx renders can now be stored by your CDN, for at most 5 minutes. Off by default; it needs the store opt-in, an edge cache time and the Cloudflare purge.<\/li>\n<li>Stock, sale and tax rate changes, new paid orders and saved WooCommerce settings clear the cache about 30 seconds later, once for several changes, so a checkout never waits for Cloudflare.<\/li>\n<li>Store pages are never cached while WooCommerce geolocates visitors, for logged-in customers, or for shoppers with something in their cart. The new <code>flx_modernize_store_route_cacheable<\/code> filter can turn store caching off, for example with a multi-currency plugin.<\/li>\n<li>Changing the store opt-in, the store caching setting or WooCommerce's default customer location now also clears the edge cache.<\/li>\n<\/ul>\n\n<h4>1.12.0<\/h4>\n\n<ul>\n<li>New: set up the plugin from the dashboard, without editing files. <strong>Generate signing key<\/strong> creates the key and shows the value for your Render service once; <strong>Test connection<\/strong> checks that the Render service is reachable and accepts the key, and says what to fix if not.<\/li>\n<li>New: the WooCommerce opt-in, logged-in customers, edge caching and the Cloudflare purge can be set on the Flx Modernize screen too. Settings already in <code>wp-config.php<\/code> keep priority and are shown read-only, so sites that use them see no change.<\/li>\n<li>A signing secret or Cloudflare token saved on the screen is stored in the database (not loaded on every page). For stronger protection, keep them in <code>wp-config.php<\/code>.<\/li>\n<li>Uninstalling now also removes the signing key saved in the database.<\/li>\n<\/ul>\n\n<h4>1.11.0<\/h4>\n\n<ul>\n<li>New for WooCommerce stores that opted in: the Astra theme (4.14, without a child theme). The shop, product categories and tags, products and the store's pages on the default page template go through Flx, with Astra's header and footer as your site prints them. Logged-in customers (<code>FLX_MODERNIZE_LOGGED_IN_CUSTOMERS<\/code>) get these catalogue pages too, with their own account link or avatar in the header, made on your server.<\/li>\n<li>Fixed: a classic theme's page could go to the Render service without the theme's styles in the page head; it now stays normal WordPress instead. The theme's head and footer output may now be up to 256 KB each (was 128 KB), so themes that print a lot of CSS in the page head, such as Astra, no longer always stay normal WordPress.<\/li>\n<li>Fixed: on some themes (seen with Astra), the review form's name and email fields could still show for a logged-in customer; they are now hidden.<\/li>\n<li>Changed: on a store that opted in with a classic theme, returning <code>false<\/code> from <code>flx_modernize_head_footer_output<\/code> now keeps every page normal WordPress, not only the store's pages.<\/li>\n<li>Sites that don't use these see no other change.<\/li>\n<\/ul>\n\n<h4>1.10.0<\/h4>\n\n<ul>\n<li>Fixed: when the Render service failed after a page was started, the normal WordPress page served instead could miss styles, scripts or widgets that some themes and plugins add (seen with the Astra theme). That page is now fetched fresh from your own site, as the same visitor, and sent with <code>no-store<\/code>. If your server cannot reach its own address, the page is served as before. <code>FLX_MODERNIZE_LOOPBACK_FALLBACK<\/code> set to <code>false<\/code> turns this off.<\/li>\n<li>New for WooCommerce stores that opted in: <code>FLX_MODERNIZE_LOGGED_IN_CUSTOMERS<\/code> (off by default) gives logged-in customers the same catalogue pages as guests. Nothing about the customer is sent to the Render service; editors and shop managers keep normal WordPress.<\/li>\n<li>Sites that don't use these see no other change.<\/li>\n<\/ul>\n\n<h4>1.9.0<\/h4>\n\n<ul>\n<li>New: Elementor support on the Hello Elementor theme (Elementor 4.3 and Hello Elementor 3.5, free versions). Pages built with Elementor on the \"Elementor Full Width\" or \"Elementor Canvas\" template are served through your Render service, with Elementor's own markup, styles and scripts.<\/li>\n<li>Everything else on such a site stays normal WordPress: posts, archives, search, other page templates, Hello child themes, Elementor Pro, WooCommerce store pages, and other Elementor or Hello versions.<\/li>\n<li>If the Render service fails, the normal WordPress page is served with all of Elementor's styles.<\/li>\n<li>Sites without Elementor see no change.<\/li>\n<\/ul>\n\n<h4>1.8.2<\/h4>\n\n<ul>\n<li>Fixed: on a site using Elementor, activating the plugin removed Elementor's site-wide styles (global colours, typography and spacing) from your pages for visitors who are not logged in, even before a Render service was set up. Sites with Elementor active are now always served by normal WordPress; Elementor support is planned for a later release.<\/li>\n<li>With no Render service URL set, every page is normal WordPress and the plugin builds no page data.<\/li>\n<li>Other sites see no change.<\/li>\n<\/ul>\n\n<h4>1.8.1<\/h4>\n\n<ul>\n<li>Fixed: on WooCommerce stores that opted in, the Storefront theme's sticky add-to-cart bar did not appear on product pages.<\/li>\n<li>Sites that don't opt in see no change.<\/li>\n<\/ul>\n\n<h4>1.8.0<\/h4>\n\n<ul>\n<li>WooCommerce stores on the Storefront theme can opt in (<code>FLX_MODERNIZE_WOOCOMMERCE<\/code>, off by default): the shop, product categories and tags, products and Storefront's home page go through Flx, including for shoppers with a cart. Page data is built with an empty cart and no customer data; WooCommerce's scripts fill in the cart in the browser. A template this release wasn't reviewed against stays normal WordPress.<\/li>\n<li>Sections of those pages can be taken over in the Render service: product cards and the single product's layout are sent as structured data as well as WooCommerce's markup.<\/li>\n<li>Optional for those stores (<code>FLX_MODERNIZE_WOOCOMMERCE_SHELL<\/code>, and <code>FLX_MODERNIZE_WOOCOMMERCE_SHELL_CHECKOUT<\/code> for Checkout; WordPress 6.9 or later): the Cart, Checkout and a guest's My account inside the site's header and footer from the Render service. Built in advance with no visitor data, checked against a strict allowlist, and filled in by WordPress on your server.<\/li>\n<li>Fixed: on a WooCommerce site, the normal page served after a Render service failure lost WooCommerce's script settings, which stopped AJAX add to cart, variation forms and cart refresh.<\/li>\n<li>Sites that don't opt in see no other change.<\/li>\n<\/ul>\n\n<h4>1.7.0<\/h4>\n\n<ul>\n<li>WooCommerce-aware: on a site with WooCommerce active, the store pages (shop, products, product categories and tags, cart, checkout, My account and its endpoints, product search, WooCommerce's AJAX and API requests), visitors with a WooCommerce cart or session, and the whole site in WooCommerce's \"Coming soon\" mode are always served by normal WordPress. The site's other pages and posts keep using Flx. Without WooCommerce nothing changes.<\/li>\n<li>Page types the Render service does not offer: when it answers that it has no such page type (HTTP 404), WordPress serves that type for an hour without calling the Render service, sent like any fallback (<code>no-store<\/code>). Changing the Render URL or signing key clears this at once.<\/li>\n<\/ul>\n\n<h4>1.6.0<\/h4>\n\n<ul>\n<li>Plugin stylesheets and inline styles from the page head and footer now reach Flx pages, and plugin scripts get the WordPress scripts they depend on (jQuery, wp-i18n, ...), in WordPress's order. Tested with Contact Form 7 and Easy FancyBox. WordPress's block and theme styles stay out; the renderer provides them. Renderer package 1.6.0 keeps form fields in post content looking as on WordPress.<\/li>\n<\/ul>\n\n<h4>1.5.0<\/h4>\n\n<ul>\n<li>Post pages get the theme's \"Written by ... in \" line, tags, previous\/next post links and \"More posts\" list (<code>author_url<\/code>, <code>categories<\/code>, <code>tags<\/code>, <code>previous<\/code>, <code>next<\/code>, <code>more_posts<\/code>; renderer package 1.5.0 or later).<\/li>\n<\/ul>\n\n<h4>1.4.0<\/h4>\n\n<ul>\n<li>Comments on post pages: the theme's comments section (approved comments and the reply form) is sent as WordPress renders it for an anonymous visitor (<code>comments_html<\/code>, renderer package 1.4.0 or later). Form plugins keep working. Visitors who have commented, and reply or \"awaiting moderation\" links, get normal WordPress. The filter <code>flx_modernize_comments_html<\/code> can change or remove the section.<\/li>\n<li>Header sub-menus, up to three levels deep (renderer package 1.4.0 or later); they open on hover and keyboard focus.<\/li>\n<li>Search results get the theme's \"More posts\" list (<code>more_posts<\/code>, the four latest posts; renderer package 1.4.0 or later).<\/li>\n<li>Edge caching also purges when a comment is approved on arrival or edited, and when comment settings change.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>The site language is sent to the Render service (<code>language<\/code>, as in <code>get_bloginfo( 'language' )<\/code>), so Flx pages have the right <code>&lt;html lang&gt;<\/code> (renderer package 1.3.0 or later). Renderer package 1.3.0 also adds the \"Skip to content\" link.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Optional edge caching: with <code>FLX_MODERNIZE_EDGE_TTL<\/code> in <code>wp-config.php<\/code>, pages, posts, the blog home page and category and tag archives without a query string are sent <code>public, max-age=0, s-maxage=&lt;TTL&gt;<\/code> so a CDN can store them. Search, 404, query strings, fallback pages and logged-in users are never cached.<\/li>\n<li>Optional Cloudflare purge after content, menu, settings or plugin changes (<code>FLX_MODERNIZE_CLOUDFLARE_ZONE_ID<\/code>, <code>FLX_MODERNIZE_CLOUDFLARE_API_TOKEN<\/code>).<\/li>\n<li>Works with renderer package 1.2.0 (Tailwind CSS styling).<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>SEO tags, JSON-LD and plugin scripts from <code>wp_head<\/code> and <code>wp_footer<\/code> are sent to the Render service (<code>head_html<\/code>, <code>footer_html<\/code>), so SEO plugins such as Yoast work on Flx pages. Filter <code>flx_modernize_head_footer_output<\/code> turns it off.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>New Flx Modernize: renders the blog home page, archives, posts, pages, search results and the 404 page through your Flx Render service, in the Twenty Twenty-Five theme's look.<\/li>\n<li>Serves anonymous visitors only; logged-in users, previews and password-protected or non-public content always get normal WordPress.<\/li>\n<li>Page data is built as an anonymous visitor; no visitor data is sent except search words.<\/li>\n<li>Optional signed requests to the Render service.<\/li>\n<li><code>Cache-Control: private, no-store<\/code> on Flx pages and <code>no-store<\/code> on fallback pages; <code>DONOTCACHEPAGE<\/code> for page-cache plugins.<\/li>\n<li>Header menus with custom, page, post and category links.<\/li>\n<li><code>flx_modernize_should_render<\/code> filter to turn Flx off for a request.<\/li>\n<li>No default Render URL: nothing is sent until an administrator saves one.<\/li>\n<\/ul>\n\n<h4>0.0.2<\/h4>\n\n<ul>\n<li>Early preview.<\/li>\n<\/ul>","raw_excerpt":"Render your WordPress pages in Node.js while WordPress and its plugins keep running, with automatic fallback to WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/374819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=374819"}],"author":[{"embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rickey29"}],"wp:attachment":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=374819"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=374819"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=374819"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=374819"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=374819"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=374819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}