Recent downtime and the forum software - Printable Version +- LDraw.org Discussion Forums (https://forums.ldraw.org) +-- Forum: Administrative (https://forums.ldraw.org/forum-4.html) +--- Forum: Website Suggestions/Requests/Discussion (https://forums.ldraw.org/forum-23.html) +--- Thread: Recent downtime and the forum software (/thread-14978.html) |
Recent downtime and the forum software - Orion Pobursky - 2014-12-22 The recent downtime was cause by our forum software conflicting with out webhosts Apache security settings. I've implemented what I consider to be a non-ideal workaround. This issue and the fact that current software is wonky under PHP 5.4+ may force my hand into upgrading the forum software. This unfortunately will mean that the hybrid thread view will go away. Thankfully I did a lot a lot of legwork to convert the for before I decided to abandon the project to based on your feedback about liking the hybrid view a lot. Whether we convert or not is really going to depend on how deeply rooted this conflict is to the core of the form software. Stay tuned for more. Re: Recent downtime and the forum software - Michael Horvath - 2014-12-23 I don't like the hybrid view much. Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-25 Michael, you can change your view in the control center Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-25 I think I solved the PHP 5.4 issues. Please let me know if there are any issues with broken images/avatars Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-25 Ok. Guess not. Have to work today so I'll try another fix tomorrow. Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-26 Try number 2. Hopefully this sticks Re: Recent downtime and the forum software - Max Martin Richter - 2014-12-26 Still the same result :-( Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-26 Yup I know. I'm still working on it. Re: Recent downtime and the forum software - Orion Pobursky - 2014-12-27 Think I (finally) found the issue. Workaround implemented. Now to try and solve the root cause. |