Transforming UB’s digital communications.
During Step 2, QA2 is where you find and fix custom code issues. Once you've confirmed your fixes work, you'll need to get them into AUTHOR — here's how to do that without disrupting your live site.
Open your site on QA2 and compare it against QA. When you find something that looks off, use your browser's developer tools to inspect the element and identify the correct selector. Update your code in QA2 and confirm it works across desktop, tablet, and mobile before moving on.
See the Selector Change Log for known selector changes and the Custom Code & NextGen page for guidance on where your code lives and how to find it.
QA2 rebuilds from AUTHOR every weekend. Any fixes you've made directly in QA2 will be erased in that rebuild.
Each Friday, before the end of the day, copy your fixes to the same location in AUTHOR. If your code is scattered across multiple pages or locations, this is a good opportunity to consolidate — see Organize As You Go.
After the weekend sync, your fixes will be on QA2 automatically. You can pick up where you left off on Monday.
Do not publish the pages or areas where you've added NextGen code fixes in AUTHOR. Your fixes will go live automatically when your site activates in Step 4.
Custom code is yours to maintain — the help desk doesn't provide implementation support. If you've confirmed an issue isn't related to your custom code, report it using the conversion issues form.