Add WooCommerce test store blueprints (Hello Elementor and Astra) - #226
Merged
adamziel merged 1 commit intoJul 28, 2026
Merged
Conversation
Contributor
Test using WordPress PlaygroundThe changes in this pull request can be previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. Blueprint previews |
…o Elementor + Astra) Two WooCommerce store blueprints capturing common store configurations for testing: - woocommerce-test-store-hello-elementor: Hello Elementor theme, EUR/DE locale - woocommerce-test-store-astra: Astra theme, USD/US locale Each installs a set of widely-used WooCommerce extensions (installed inactive, then activated last so seeding runs on a WooCommerce-only stack), configures a realistic locale + store settings, and seeds sample products. Both boot clean on WooCommerce latest and pass validate-pr-blueprints. Each folder includes a README describing the setup and how to change the WooCommerce version.
alopezari
force-pushed
the
add-woocommerce-store-blueprints
branch
from
July 27, 2026 14:54
71384a6 to
2f094ba
Compare
alopezari
marked this pull request as ready for review
July 27, 2026 15:11
adamziel
pushed a commit
that referenced
this pull request
Jul 29, 2026
…227) Follow-up to #226. Three of the bundled plugins (Elementor, WPForms, WP Mail SMTP) grab the first wp-admin visit after activation and drop you into their setup wizard. That's exactly what you don't want from a blueprint whose point is landing on a ready-to-use store, so this adds one last `runPHP` step to both blueprints that marks the wizards as already done. For Elementor that means setting `elementor_onboarded`, for WPForms `wpforms_setup_wizard_completed`, and for WP Mail SMTP `wp_mail_smtp_activation_prevent_redirect`, plus deleting each plugin's activation-redirect transient. The step has to run after the activation step because `WPFORMS_VERSION` only exists once the plugin is active. Nothing is removed: the wizards are still reachable from each plugin's menu, they just stop auto-launching. This also adds the screenshots for both blueprints. The screenshot workflow doesn't run on fork PRs, so #226 merged without them and both stores show the "no screenshot" placeholder in the gallery. ## Testing - A/B tested the WPForms path with `@wp-playground/cli`: a minimal blueprint that installs and activates `wpforms-lite` the same way these do renders "WPForms Setup Wizard" on the first `/wp-admin/` load. With the new step, the same request renders the normal dashboard. - `npm run validate:pr-blueprints` passes for both blueprints.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two blueprints that set up a WooCommerce store with a realistic configuration, so you can test plugins, themes, or WooCommerce itself against something closer to a real store than a bare install.
woocommerce-test-store-hello-elementor— Hello Elementor theme, EUR / German localewoocommerce-test-store-astra— Astra theme, USD / US localeEach installs WooCommerce (latest) plus a set of widely-used extensions (Yoast, Jetpack, Elementor, PayPal / Stripe / WooPayments, Site Kit, Google Listings & Ads, Contact Form 7, WP Mail SMTP, LiteSpeed, Loco Translate, Code Snippets, WPForms, Classic Editor), sets a realistic locale and store config, and seeds three sample products. Each folder has a README.
I split it into two because no single theme or locale dominates real stores. I took the two most common theme families and paired them with the EUR and USD profiles. The two blueprints differ only by theme and locale; everything else is identical.
Notes
Plugins are installed inactive and activated in a final step, so the sample content is created on a WooCommerce-only stack. If everything is active up front, Elementor throws "Access denied" when the seeding step saves a page. Activating last avoids it.
All extensions are active by default. That's a lot of plugins for Playground, so the admin can feel slow on a constrained host — each README notes which ones to deactivate for a snappier site.
Testing
@wp-playground/cli run-blueprint; verified the products, pages, and locale on the running site.npm run validate:pr-blueprints.No screenshots yet — the gallery auto-generates them on merge. Happy to add my own if you'd rather.