Safe ordinary-member testing when Release Manager shows “Version not found”

Ask the community
, , ,
1

Hi everyone. We’re preparing to test a Wix site with Velo, Wix Members and CMS collections, using only fictional test profiles.

We need to verify two ordinary members’ access separately, rather than testing with administrator privileges. Wix’s collection-permissions documentation says Editor Preview runs as admin, and its Test Site documentation does not describe an isolated database.

Release Manager has also shown “Version not found” for a test release. Before changing that release, could someone point us to current Wix documentation for:

  1. Testing as ordinary members against isolated synthetic data, without publishing unfinished changes to production or touching production records.
  2. Safely recovering or replacing a Test Site with this error while preserving the existing published version.
  3. Confirming which code revision and data collections a test session actually uses.

If a separate QA site is the supported approach, what prerequisites and limitations should we check? We are looking for documented steps rather than disabling permissions or using administrator access to make tests pass.

Thanks for any guidance.