I started a new job a few months ago, and part of the job is to keep the webpage updated. I am quite experienced in web development, but I've never encountered DotNetNuke. With a rather open mind, I started learning how to use it and keep our website looking fresh.
That said, I've got to say that it has been the worst CMS I've ever used or experienced in my 10+ years of web development. I have to wonder: is DNN truly awful, or is it awful because of our webhost / the original developer? The system is extremely slow, and about half of the updates I try to make are impossible. I'm constantly met with both HTTP error 504, as well as having the server unexpectedly drop the connection. Once I get these errors, I will continue to get them *every* time I try making additional changes, and it also has the side effect of blanking out the entire page in question. Naturally, the original developer can't provide much help aside from pasting in my updates and telling me that it works fine for him.
Of course, due to the lack of information, I can't tell if it's an issue with the web server or DotNetNuke itself. I can rule out my PC and connection, as every other site I develop or maintain works fine. In addition, I have these issues across multiple browsers, computers, operating systems, and internet connections.
So, someone tell me: is DotNetNuke always this terrible? I'm not sure if I should be shopping for a new web host or if I should be building a new site based on a CMS that's actually usable.