If you get any more Error 500s, please send the specific error messages to me, preferably as a paste. You can send them to me Twitter (@DavidJCobb), Xbox LIVE (DavidJCobb), a PM on Halo Waypoint if you happen to be a member there, or you can send the paste or screenshot to noklu and ask that he forward them to me on Facebook. If you can also include the specific URL or page you were trying to access (and details on what you expected to see instead of an error message), that would be very helpful.
Please also convey that directive to anyone else who reports seeing these sorts of errors.
I've seen two screenshots so far, but they didn't show the same error, so I don't know if they were one-off events or if there is something wrong with Reaching Perfection specifically. I'll try to look into them soon now that it looks less like a one-off problem, but more data would be helpful. Once I know what the error actually is, I can either attempt to fix it, or ask Nabble staff for some insight.
EDIT: Screenshots are no-goes. Need the entire error message, long-ass stack trace included.
The error occurs because of a bad URL. The URL species "new_topic" but doesn't say what that is (should be "macro=new_topic"), and it doesn't specify a "node" (where the new topic should be created).
How exactly did you get to that error page? Walk me through the steps you took -- particularly the links/buttons you clicked. Did the error occur when you first loaded the page, or did you reload it from some other means (Back button, browser session restore, etc.)?
Looks like the Permalink generated incorrectly for some reason. Did you use the one at the top of the page, or the one on your specific post (under the "More" menu)?
Just looked into it. The Permalink code doesn't grab the location of the forum IFRAME's contentWindow; instead, it grabs the href of the IFRAME itself. Your bug would be the consequence of Google Chrome failing to update that href after you created a new topic, but I just did a quick test and that didn't happen to me.
Strange. Please continue to keep an eye out for more Error 500s, and send any details you have to me. Pasting it into an email works; pastebin.com is also good. Screenshots are a no-go.
I encourage anyone else that may be reading this to follow the same instructions. If you get an error, send me the exact message you see.