Diagnose connection and rendering failures

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

A defect report identifies the installed version, affected system, reproducible steps, expected and observed behavior, and safe evidence without leaking credentials or customer data.

Separate Shopify access, WordPress HTTP, synchronization data and theme rendering before changing credentials or templates.

Before you begin

• The installed version, edition and package provenance.
• A reproducible test page or catalog record using controlled data.
• Browser, WordPress, PHP and active builder or SEO-plugin versions.
• A database backup before destructive diagnosis or repeated synchronization.

Plan a way back before you start: a backup or a staging copy, the Shopify product you will compare with, and the WordPress page that should show the result. Start with a small test that you can repeat.

What this covers

The support form is intentionally fail-closed until its edge controls are configured. A prepared report can be assembled locally, but the site must not imply that an unconfigured form delivered it.

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.

Steps

1. Classify the failure as connection, discovery, synchronization, WordPress data, rendering, buying, SEO or lifecycle.
2. Reduce the case to one product, collection, shortcode, block or URL whenever possible.
3. Record exact steps and compare expected behavior with the delivered, partial or absent capability state.
4. Capture the rendered page and relevant Fy2Press screen after removing tokens, domains that must remain private and personal data.
5. Restore the environment after experiments and confirm whether the defect persists on the clean state.

Review the result before you share a page publicly. A success message is a good sign, but the public page and the Shopify buying path must agree too.

Check the result

• Another administrator can reproduce the defect from the report without guessing missing steps.
• The report distinguishes the Shopify source, Fy2Press transport and WordPress presentation layers.
• Every attachment is free of tokens, customer records, order details and private URLs.

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.

Common problems

• Intermittent behavior: capture timestamps and the sequence of state changes rather than repeatedly clicking the action.
• Only the builder preview fails: test the frontend renderer and identify whether the issue is editor-only.
• SEO output is unexpected: save the final HTML and active integration list before clearing caches.

When something unexpected happens, stop large operations and try again with one product and one page. Keep the exact error message before you change settings or clear caches.

Troubleshooting

1. Confirm the plugin version and edition (FREE or PRO).
2. Reproduce the problem with one test product.
3. Decide whether the issue comes from Shopify, Fy2Press or your WordPress theme.
4. Compare the result with what your edition includes, as described in the edition guide.
5. Restore your test setup, try once more and note whether the result repeats.

Security and data

Sanitize evidence before sharing. Replace tokens, customer information, order identifiers and private store domains with controlled placeholders while preserving the structure needed to reproduce the issue.

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

For SEO defects, include the exact response status, canonical, robots, hreflang if relevant, sitemap membership, structured data and internal links. A screenshot alone is insufficient.

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

• Installation
• Publish with WordPress
• Google and SEO
• Security and data

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.