Linux 软件免费装

Flx Modernize

开发者 rickey29
更新时间 2026年11月19日 23:16
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

elementor headless nodejs rendering twenty twenty-five

下载

0.0.2 1.2.0 1.13.0 1.8.0 1.8.1 1.8.2 1.1.0 1.4.0 1.5.0 1.6.0 1.0.0 1.10.0 1.7.0 1.9.0 1.12.0 1.14.0 1.15.0 1.11.0 1.15.1 1.15.2 1.3.0

详情介绍:

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. This release supports sites using the Twenty Twenty-Five theme. A Twenty Twenty-Five renderer package is available from modernize.flexplat.com; you can run it yourself or have it hosted for you. Sites on the Hello Elementor theme can serve pages built with the free Elementor plugin; see "Elementor" below. WooCommerce stores on the Storefront or Astra theme can opt in as well; see "WooCommerce stores" below. See it in 60 seconds https://youtu.be/1qbbvq67eu8 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 plugin demo page (visit it logged out). What is rendered through Flx 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. What always stays normal WordPress Elementor 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. WooCommerce stores Off unless a site opts in: on the Flx Modernize screen (WooCommerce → Store pages), or with the constant FLX_MODERNIZE_WOOCOMMERCE in wp-config.php. It needs the Storefront theme, the Astra theme (4.14, without a child theme) or the Flatsome theme (3.18.2; a child theme only with styles and functions.php), and a Render service that draws that theme: the Storefront renderer package, or an Astra or Flatsome renderer built for your site. Any other theme, or a theme or WooCommerce template this release wasn't reviewed against, stays normal WordPress. Safety Edge caching (optional) Off by default. With an edge cache time set (Flx Modernize screen, or FLX_MODERNIZE_EDGE_TTL, 60–3600 seconds), Flx pages that are the same for every visitor (pages, posts, the blog home page, category and tag archives, without a query string) can be stored by your CDN. Search results, the 404 page, URLs with a query string, fallback pages and everything WordPress renders itself are never cached. With a Cloudflare zone ID and a purge-only API token, any change that can show on a page clears your site from Cloudflare's cache, and Cloudflare can serve an expired copy once while it fetches a fresh one (stale-while-revalidate), so no visitor waits. WooCommerce stores can also cache the shop, category and product pages for at most 5 minutes (Store pages in the edge cache); Cart, Checkout, My account and shoppers with something in their cart never are. Settings, filters, the CDN rules (including the cart cookies to skip) and the Cloudflare Cache Rule are in the documentation. For developers The flx_modernize_should_render filter lets you turn Flx off for a request (return false). It can never turn Flx on for a logged-in user. The flx_modernize_head_footer_output filter turns off the head and footer output (return false). Documentation and a step-by-step tutorial for building a renderer for a theme are at modernize.flexplat.com.

安装:

  1. Install and activate Flx Modernize from the Plugins screen.
  2. Set up a Flx Render service for your theme (see modernize.flexplat.com), or have one hosted for you.
  3. Go to Flx Modernize in wp-admin and click Generate signing key. Copy the value it shows (once) into your Render service's FLX_RENDER_SIGNING_KEYS setting.
  4. Enter the Render service URL. To check Flx pages before your visitors see them, also tick Preview only. Save.
  5. Click Test connection: it tells you whether the Render service is reachable and accepts the key, and what to fix if not.
  6. With Preview only: open the preview link shown on the screen in a private window, and add the same ?flx-preview=… to other pages' addresses to check them. Visitors keep normal WordPress until you untick Preview only and save.
  7. Visit your site while logged out: pages are now served through Flx. While logged in you keep seeing normal WordPress.
Every setting can also be defined in wp-config.php 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; wp-config.php keeps it out of the database.

常见问题:

Which themes are supported?

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.

What happens if the Render service is down?

WordPress renders the page itself, automatically, and sends it with Cache-Control: no-store so the fallback page is not cached.

Why do I still see normal WordPress?

Because you are logged in. Flx serves anonymous visitors only. Open the site in a private window to see the Flx pages.

Does it work with page-cache plugins?

Flx pages tell page-cache plugins not to store them (DONOTCACHEPAGE) and send Cache-Control: private, no-store. To cache Flx pages at your CDN instead, turn on edge caching (see the Description).

Which menus are supported?

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).

Does it need WooCommerce?

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.

更新日志:

1.15.2 1.15.1 1.15.0 1.14.0 1.13.0 1.12.0 1.11.0 1.10.0 1.9.0 1.8.2 1.8.1 1.8.0 1.7.0 1.6.0 1.5.0 1.4.0 1.3.0 1.2.0 1.1.0 1.0.0 0.0.2