Evan Reiter Share Posted July 22, 2011 The website and forums may be offline temporarily starting at 11:30am on Friday, July 22 and continuing until 2-4am on Saturday, July 23. Evan Reiter Community Director Administration Team Link to comment
Evan Reiter Author Share Posted July 23, 2011 Website maintenance complete. We have performed a MAJOR overhaul to the main website's backend; this should not be too apparent to users but there may be a few pages that have been modified. If you notice anything strange about the website, or any pages that do not look as they should, please let us know! Evan Reiter Community Director Administration Team Link to comment
Tom Guerrette Share Posted July 24, 2011 This doesn't seem right: It clearly says I'm logged in at the top (tofutwitch11 - Logout) but says I'm not logged in.. Tom G. FSExpo Liaison [email protected] www.bvartcc.com Link to comment
Guest Brandon Carter Share Posted July 24, 2011 This doesn't seem right: It clearly says I'm logged in at the top (tofutwitch11 - Logout) but says I'm not logged in.. I have the same issue. Hopefully DNN will release another update soon that fixes it. I think you use Firefox and still have that issue, right? Link to comment
Tom Guerrette Share Posted July 24, 2011 Yes, I use FF. Tom G. FSExpo Liaison [email protected] www.bvartcc.com Link to comment
Evan Reiter Author Share Posted July 24, 2011 I am unable to reproduce the error. Evan Reiter Community Director Administration Team Link to comment
Evan Reiter Author Share Posted July 25, 2011 I made this post in a response to a question Tom asked me in a restricted section of the forums and thought it was worth passing along to the general community as well. What was wrong with the way it was before? It seems this update has caused more problems than it fixed (if any). Good question. The content management system that we use -- DotNetNuke (DNN) -- works something like the OS on your computer in that regular updates come out for the software. The same is true with our forums. Normally these updates are minor, fixing small bugs and security holes. The forums were updated at the same time as the website but I haven't noticed a difference. I was expecting the same with the website. It's important to make the updates quickly because they often address security holes and make a big functionality improvement. The longer we wait, and the more updates we miss, the worse will be the eventual updgrade and the more likely that upgrade will be to, for want of a better term, blow up. However, it turns out DNN has totally re-done the interface of the website. This was unexpected. Nevertheless, it's something we had to do. The website on our previous ISP was so bug-ridden in part because we were using a version of the operating system that was 2.5 years old. We had to complete 2 years' worth of updates when we migrated the server over and that process caused all sorts of problems. When the ATC page broke a few months ago, it was because we updated a module that hadn't been touched since 2006. Ever since then we've been keeping up with the updates because eventually we would be in the same situation if we never updated. So your next question is probably "why didn't we test the update more thoroughly before we updated the site live?" That's a good question and the answer is two-fold. Firstly, it's impossible to update the site behind the scenes and then release it to you...there's just no functionality like that. It's not like we can make an update, test it, and then click "go" and let you all see it. The only thing we have been able to do -- thanks to the hard work of Phil, our soon-to-be DNN expert (we hope) -- is to have someone set up a local copy of DNN on their own machine. This can't be connected to our DNN, so any changes we make on our side have to be made again on his, users don't update, etc. But at least we have an idea as to what we're getting into. This situation was unique for several reasons. Firstly, a previous update we performed on the website on Sunday (a minor update) was completed incorrectly because we tried to do it at a time when multiple users were on the website (since neither Phil nor I could manage to stay awake until 3am like I did for this update). Consequently, several features (like the ability to change font sizes/colors) weren't working properly. When the newest version came out Thursday, I thought it would be a good opportunity to get the newest version installed to resolve the font bug and, since I had some time, dedicate another Friday night to BVA and stay awake until late to make that update at a time when nobody would be inconvenienced. Because Phil is on vacation, we weren't able to do our usual offline testing. On Saturday morning, as you saw from the original post, I completed the updates around 3am. Obviously we have a few issues that resulted from them -- these are the things you've been complaining about. It was a tough call: make the upgrade, fix the issues, but chance major changes, or wait for Phil to return, put up with the inability to make changes to fonts (for at least 2 weeks since next weekend is a long weekend), and then try to find another available time to do an upgrade. Contrary to popular belief, I actually don't like missing friends' birthday parties to be here making updates but I do because I'm afraid of what will happen if I try to make a major update to the site in the middle of the day. Evidently I chose wrong on this occasion. I apologize for the extreme inconvience you have been caused by the website's lack of functionality. I do not know DNN very well and am spread relatively thin but will do my best to research and fix any of the issues we've seen with the login and controllers' event sign-up. Since I can't reproduce the login issue, that one will be very difficult to fix. The controllers' sign-up will probably be resolved by making the event details pages into regular DNN pages rather than pop-up windows (which I've wanted to do for a little while anyway). If it makes you feel any better, Bill has also had to work hard on a fix for FlightDesk since the upgrade changed the way the login page is structured (not the way it functions) and that meant no users could sign in to FlightDesk. We're all scrambling to give you the best possible experience; I'm sorry we can't do it fast enough. I'm also sorry that I wasn't able to perform a seamless upgrade. Hopefully DNN will come out with a fix for the issues with the login page and we'll have a fully-functional website again soon. Evan Reiter Community Director Administration Team Link to comment
Evan Reiter Author Share Posted July 25, 2011 ...and now the site is broken. Working on it. Evan Reiter Community Director Administration Team Link to comment
Evan Reiter Author Share Posted July 25, 2011 To address additional functionality concerns, I have reverted the website back to the previous version we were using. While it will now mean manual adjustments of any text, we also have our normal editor back for ATCs, and should have resolved the login issues we were having. We will thoroughly test the new version of DotNetNuke while waiting for a patch to come out to fix the issues you noticed. As part of reverting the website, some user accounts were deleted. If your BVA ID is on the list below, you will not be able to sign in to FlightDesk or the website today. I will manually re-create your accounts when I have time, probably tonight, and be addressing you individually by e-mail. ZEGO Blue_Skies97 CM039 gruffalo95 president757 Again, please let me know of any issues right away (as Tom and Brandon have) so that we can address them quickly. Thanks again! Evan Reiter Community Director Administration Team Link to comment
Evan Reiter Author Share Posted July 25, 2011 All user have been re-activated and everyone should be able to login to the website fine. Again, please let us know if you have any issues with the site. The last post about an issue prompted a long response from me because I wanted to explain my rationale to everyone and it took a long post to do that. But without getting information from people about issues, I can't fix them, and I am always grateful to the people that are willing to stand up to let us know something is wrong. That's why one of my personal development goals is to be more responsive and open when responding to problems in crisis situations. For now, let's hope that none of that will happen again now that the site has been restored... Evan Reiter Community Director Administration Team Link to comment
