# Staging Environment Restoration Plan ## Overview This plan outlines the steps to verify and complete the staging environment restoration after the production sync. ## Prerequisites - Production sync has been completed ✓ - Staging server details: - URL: wordpress-974670-5399585.cloudwaysapps.com - IP: 146.190.76.204 - Path: /home/974670.cloudwaysapps.com/uberrxmprk/public_html ## Verification Steps ### 1. Run Staging Verification ```bash ./bin/verify-staging.sh ``` This will: - Verify plugin activation - Check plugin status - Review debug logs - Verify required pages exist ### 2. Manual URL Verification Check the following URLs: - Homepage: https://wordpress-974670-5399585.cloudwaysapps.com/ - Admin Panel: https://wordpress-974670-5399585.cloudwaysapps.com/wp-admin - Community Login: https://wordpress-974670-5399585.cloudwaysapps.com/community-login/ - Trainer Registration: https://wordpress-974670-5399585.cloudwaysapps.com/trainer-registration/ ### 3. Configure PHPUnit Environment Configure PHPUnit for test execution: ```bash ./bin/configure-phpunit-staging.sh ``` This will: - Configure PHPUnit path in staging environment - Verify PHPUnit installation - Set up test environment variables ### 4. Run Basic Smoke Tests Execute the basic smoke test suite to verify core functionality: ```bash ./bin/run-staging-tests.sh ``` ## Success Criteria - [ ] verify-staging.sh completes without errors - [ ] All URLs are accessible - [ ] PHPUnit configuration successful - [ ] Basic smoke tests pass - [ ] Plugin is active and functioning - [ ] No critical errors in debug.log ## Rollback Plan If issues are encountered: 1. Document the specific failure 2. Check debug logs for errors 3. Consult with team for production sync retry if needed ## Notes - All production syncs must be coordinated with the user - Monitor debug.log for any warnings or errors - Document any issues encountered in the process - PHPUnit tests can be run using either global command or vendor path - Test results are stored in tests/test-results/ directory