Fy2Press 1.0.0 · 10
Reference the 17 dynamic Gutenberg blocks
Map every registered server-rendered block to the catalog surface it controls.
Documentation for Fy2Press 1.0.0. The free plugin is available on WordPress.org. PRO is sold separately through Freemius, our licensing and payment provider.
In three steps
- Insert the block from the Fy2Press category.
- Confirm that its product or collection context resolves in the editor preview.
- Preview the public page because editor registration does not prove theme-level output parity.
This guide describes Fy2Press 1.0.0. Screens can change in later versions, so check the version shown on the Plugins screen before you follow it.
Expected result
Map every registered server-rendered block to the catalog surface it controls.
The version shown registers 17 dynamic Gutenberg blocks. Every block has apiVersion 3 metadata, a PHP render callback and a ServerSideRender editor preview. The metadata declares no user attributes, so this reference must not invent inspector controls.
Before you begin
- Insert the block from the Fy2Press category.
- Confirm that its product or collection context resolves in the editor preview.
- Preview the public page because editor registration does not prove theme-level output parity.
What this covers
Remember who does what: Shopify keeps products, inventory, orders, payments and checkout; Fy2Press brings the catalog into WordPress and displays it; WordPress hosts your pages and editorial content. Nothing in this guide moves orders, customers or payments to WordPress.
The version shown registers 17 dynamic Gutenberg blocks. Every block has apiVersion 3 metadata, a PHP render callback and a ServerSideRender editor preview. The metadata declares no user attributes, so this reference must not invent inspector controls.
Steps
- Insert the block from the Fy2Press category. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.
- Confirm that its product or collection context resolves in the editor preview. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.
- Preview the public page because editor registration does not prove theme-level output parity. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.
Check the result
Check the result where visitors will see it: open the public WordPress page, not only the Fy2Press screen, and compare a representative product with Shopify, including its price, availability, variants and collection. Repeat a small change once to confirm that the behaviour is stable.
- Confirm the exact name or stable ID.
- Compare the declared context with the rendered page.
- Test empty, long and unavailable data states.
- Compare Gutenberg, shortcode, Elementor and WPBakery output only where the coverage matrix declares a component.
Common problems
- Do not infer an attribute, block control or builder component from a similar name.
- Do not count builder-only components among public shortcodes.
- Do not describe conceptual coverage as control, markup or behavioral parity.
Troubleshooting
- Reconfirm the installed package version and edition.
- Reduce the issue to one component, one known catalog record and one WordPress URL.
- Compare the exact name, stable ID, context and output with the version-bound inventory below.
- Identify whether the failing responsibility belongs to Shopify, Fy2Press or WordPress.
- Preserve the rendered response and settings before changing configuration, then repeat the smallest safe test once.
Security and data
If you ask for help, note the plugin version, the WordPress and PHP versions, your theme or page builder, the page address and the steps you followed. Use test products, and remove tokens, customer data, order details and private addresses from screenshots before sharing them.
Effect on search
Reference components can change headings, links, product data and interactive controls. Inspect rendered semantics, accessibility, canonical behavior and the Shopify buying handoff on a representative page.
Information for support
If you ask for help, note the plugin version, the WordPress and PHP versions, your theme or page builder, the page address and the steps you followed. Use test products, and remove tokens, customer data, order details and private addresses from screenshots before sharing them.
Related guides
Version and availability
Documentation for Fy2Press 1.0.0. The free plugin is available on WordPress.org. PRO is sold separately through Freemius, our licensing and payment provider.
Go further: Build with blocks and shortcodes (EN)
Product surface
Every block has apiVersion 3 block.json metadata, a ServerSideRender editor preview and a dynamic PHP callback. The block metadata of the version shown declares no user attributes.
shopipress/add-to-cart- Dynamic server-rendered Gutenberg block. Namespace: shopipress/add-to-cart. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/availability- Dynamic server-rendered Gutenberg block. Namespace: shopipress/availability. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/buy-now- Dynamic server-rendered Gutenberg block. Namespace: shopipress/buy-now. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/collections- Dynamic server-rendered Gutenberg block. Namespace: shopipress/collections. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/description- Dynamic server-rendered Gutenberg block. Namespace: shopipress/description. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/gallery- Dynamic server-rendered Gutenberg block. Namespace: shopipress/gallery. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/image- Dynamic server-rendered Gutenberg block. Namespace: shopipress/image. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/price- Dynamic server-rendered Gutenberg block. Namespace: shopipress/price. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/tags- Dynamic server-rendered Gutenberg block. Namespace: shopipress/tags. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/title- Dynamic server-rendered Gutenberg block. Namespace: shopipress/title. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/variants- Dynamic server-rendered Gutenberg block. Namespace: shopipress/variants. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/vendor- Dynamic server-rendered Gutenberg block. Namespace: shopipress/vendor. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
Collection surface
Every block has apiVersion 3 block.json metadata, a ServerSideRender editor preview and a dynamic PHP callback. The block metadata of the version shown declares no user attributes.
shopipress/collection-description- Dynamic server-rendered Gutenberg block. Namespace: shopipress/collection-description. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/collection-products-per-page- Dynamic server-rendered Gutenberg block. Namespace: shopipress/collection-products-per-page. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/collection-sort- Dynamic server-rendered Gutenberg block. Namespace: shopipress/collection-sort. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/collection-title- Dynamic server-rendered Gutenberg block. Namespace: shopipress/collection-title. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
shopipress/products-loop- Dynamic server-rendered Gutenberg block. Namespace: shopipress/products-loop. Editor preview and frontend output use the PHP block renderer; control, markup and accessibility parity must be verified per builder.
Keep the system boundary visible
Shopify remains the commerce source; Fy2Press moves catalog records and rendering contracts; WordPress owns publication.
Shopify · catalog source and checkout
Fy2Press · manual sync and rendering
WordPress · content, templates and SEO surface
Verify before moving on
- Confirm the result in WordPress, not only in the Fy2Press interface.
- Keep cart and checkout on Shopify.
- Record the installed version when reporting a defect.