Steve texted me and we jumped on the GoToMeeting session. He was working on his custom label settings. We got deep into looking at dependencies for payee and corp-wide settings for custom colors. Basically, the page that he was coding had an if statement up higher that would split the page based on payee (user) level settings. We verified that the pages were the same, it was just the settings that were different. Anyways, we ended up looking at pages that ran correctly vs pages that did not run correctly. We were comparing things and looking deep into the dependencies. It turned into a virtual witch hunt and trying to find what the different settings did and which ones controlled the pages in different ways. We ran out of time, but at least we know where to look now.

Somehow the page was adding in two top portions of the HTML file and skipping some key CSS code. We found this by looking at the custom PO labels settings on servers and corporations that had different settings. Basically, the page would work if a person has a certain setting but it would fail if that setting was not in place.

As a side note, we had to compare the final browser output (page source code) vs the underlying code (actual code). Sometimes you can find the bug directly in the code. That's the normal way. Other times, you have to let the code generate and then look under the covers from what gets pushed back to the browser (html source code - what gets returned). Almost finding things after the fact vs up front. Anyways, that is how we found this error. We went backwards on it.