UAG's customizability is fantastic, and quite rare in our industry, but it can also lead to a lot of heartache. Editing ASP and HTML code takes a certain amount of expertise, and troubleshooting code issues is something that huge books have been written about, so there's little we can help with there. However, one common source of trouble is the misunderstanding of the fundamentals of the CustomUpdate process. A common mistake is copying a full file from the main folder or from the samples folder into the CustomUpdate folder, without modification. That rarely works, and will often lead to server errors (500 errors). This happens because UAG runs the code inside CustomUpdate in addition to the main code files, so this may cause various variable and function collisions or race condition. Also, the samples themselves often contain multiple examples in a single file, causing the code to do multiple things that may collide.
Another thing that may daunt you is the fact that...
