Diagnose connection and rendering failures

This guide applies to the ShopiPress version identified in the page header, officially published on Freemius. Confirm the installed version before applying the procedure. Later versions may change screens, defaults or service boundaries.

Expected result

A defect report identifies the exact candidate, 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.

Prepare a rollback point and identify the authoritative Shopify record and the WordPress URL or administration surface that will prove the result. The test should be small enough to repeat without creating ambiguous catalog state.

Scope and current limits

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.

Keep the responsibility model visible throughout the task: Shopify remains the commercial source and checkout system; ShopiPress connects, synchronizes and renders the catalog according to delivered contracts; WordPress owns the publishing context. A successful WordPress result must not be interpreted as a transfer of orders, customers, payments or inventory authority.

Procedure

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

Do not skip the review step between an administrative action and public publication. A successful control response is only one layer of evidence; the stored WordPress record, rendered page and Shopify commerce path must agree.

Verify the result

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

Verify the result in the rendered WordPress page and in the authoritative Shopify surface, not only inside the ShopiPress administration screen. Use a representative product with price, availability, variant and collection data. Repeat the smallest safe operation when idempotence matters, and record any difference before broadening the test.

Common mistakes

• 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 a result is unexpected, stop broad actions and reduce the case to one record, one URL and one renderer. Preserve the failing response before changing settings or clearing caches so the diagnosis remains reproducible.

Troubleshooting

1. Confirm the package version and edition.
2. Reproduce the smallest safe case with controlled data.
3. Identify whether Shopify, ShopiPress or WordPress owns the failing step.
4. Compare the observed result with the delivered, partial or absent capability state.
5. Restore the test environment, repeat once and record whether the result is stable.

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.

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

SEO consequences

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.

Evidence to record

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

Related guides

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

Version and product state

ShopiPress is officially published on Freemius. This guide describes the documented version. Purchase and download links will be added to this site once their destinations are configured.