How do you test?

Ask the community
,
1

My site has been online and active for 2 years. I have written a great deal of JS code for custom logins, payments, etc. All is working well. However, I am often making changes/improvements but I don’t like my PROCESS.

What I typically do for a tricky change is as follows:

  1. Duplicate the site

  2. Change all my PaidPlan IDs to match the new site.

  3. Change the PaidPlan amounts to $1 to make testing less of a financial burden.

  4. Make code changes, test. Fix code changes, test. Fix the fixes, test. Declare it “ready” for publishing.

  5. Copy ALL the code i just changed from various pages as well as all the screen property changes for any items that were required to support my code to the Paid site from the duplicated site.

  6. Publish the site

  7. Hope I didn’t forget something!!

I follow this process because you cannot test login flow or payments in Preview mode.

PLEASE tell me you have a better process! For example can i make the duplicated test site the “Paid site” somehow? Or, can I duplicate the test site and rename it the live site?

What do you guys do?? I’m sure I must be missing something!

Thanks in advance!

2

I would love to hear other experienced WiX devs chime in on this. Similar to the OP, I’ve been managing a site that has been operational a couple years. Previous maintenance was fairly minor, so could manage copying updates from a duplicate. Now, we’re greatly expanding the product line and I’ve generated several new collections, added many new pages, and a ton of JS code to accommodate the new products. The only alternative I found on a different post (https://www.wix.com/velo/forum/coding-with-velo/how-to-copy-an-entire-wix-site-over-to-replace-my-live-published-site) was to create a duplicate, update the duplicate and then reassign the premium to that new duplicate to make it the new live site (and I guess move over the domain assignment too) . However, I think that will wipe out a lot of SEO, leave behind old logs, and do who knows what to store data - so that method is a non-starter if you care at all about maintaining traffic to your site.

Ideas? Otherwise, we’re back to the OP’s plan…with careful documentation to remember where the heck all the changes were done.