He's a great bloke. It turns out an empty node cache was the problem again (he told me via PM). Neither of us have any idea as to why it occurred in the first place or if it'll happen again, but it's fixed for the time being - which is nice!
Yeah, I was wondering what that error was all about until I read the thread. Odd, and that occurred even after a new installation (or well, replacement of files). I guess we all learn something each day!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
