I'm delivering a report on our current situation at on Orain.
Yes, we are working on it, and it's a global problem, one with multiple facets. We've already nailed down most of the smaller issues, but one of the biggest issues is centered around the ParserFunctions extension, which, while we could remove it to bring back full functionality of at least viewing ATT, this is a bad idea for several reasons:
* That cures an immediate symptom without curing the disease.
* ATT's templates and site code make extensive use of ParserFunctions, it's literally the backbone of almost all of our site layout. Without it, almost none of our templates will function at all and will leave countless pages in a more or less broken state, which, while readable, will be a massive hassle to edit.
* The problem lies at the server level. We discovered some corrupted settings that were part of the problem, but the problems concerning ParserFunctions are not something as simple as us needing to swap out the 1.24 branch for another, and what remedy we must do is still being determined, but we need to be careful, as a lot of Orain wikis make use of it, and doing the wrong thing will break the entire farm to a greater or lesser degree.
* I was the one to discover ParserFunctions went south on Orain, and it has been confirmed via other tests by Orain Staff, and once we get it functional, we should be able to enable all other extensions we disabled earlier to restore us to full functionality and service.
I will keep you all apprised of further updates as we work on this, my apologies for the issues at hand.
Yes, we are working on it, and it's a global problem, one with multiple facets. We've already nailed down most of the smaller issues, but one of the biggest issues is centered around the ParserFunctions extension, which, while we could remove it to bring back full functionality of at least viewing ATT, this is a bad idea for several reasons:
* That cures an immediate symptom without curing the disease.
* ATT's templates and site code make extensive use of ParserFunctions, it's literally the backbone of almost all of our site layout. Without it, almost none of our templates will function at all and will leave countless pages in a more or less broken state, which, while readable, will be a massive hassle to edit.
* The problem lies at the server level. We discovered some corrupted settings that were part of the problem, but the problems concerning ParserFunctions are not something as simple as us needing to swap out the 1.24 branch for another, and what remedy we must do is still being determined, but we need to be careful, as a lot of Orain wikis make use of it, and doing the wrong thing will break the entire farm to a greater or lesser degree.
* I was the one to discover ParserFunctions went south on Orain, and it has been confirmed via other tests by Orain Staff, and once we get it functional, we should be able to enable all other extensions we disabled earlier to restore us to full functionality and service.
I will keep you all apprised of further updates as we work on this, my apologies for the issues at hand.