It seems to be very useful, but really slows down compiles (of course I already need more RAM so this doesn’t help). Looks like I’ll have to let it build XML files separate from regular compiles.
Now I need to get up to speed on XSLT to turn those XML files into something readable for non-techies. My project is getting a new person to help write documentation and I am sure the info I generate with this tool will help her out significantly.
The public site I maintain is gathering 500 errors of the dreaded “The viewstate is invalid for this page and might be corrupted” type. Strangely enough, the only users seeing this error are Macintosh users, using IE! The problem is not isloated to a single page, it seems to be happening on any page, but not necessarily every page for that user. In some cases it is clear that the user was getting around fine (they were logged in as members to the site), and later the problem occurred.
I cannot find anything on the web except a solitary Usenet post of a person describing the exact same problem.
Here are the agent strings of the browsers recorded when the error occurred:
According to the log files, MacPPC users are just under 1% of the site users, so this problem is clearly not a showstopper, but I hate for any users to have a problem. I am hoping to get a Mac set up to test the problem locally, but the agent string doesn’t give me any Mac OS versions….