zeitounator/ezpublish — comment on commit 39d62493760e22fbc2ee0d5abe904b7d80408ee5
File:  line 0
By zeitounator:

I very well know why the root check was developped since I wipped out most of our development environment because of this "bug" just before living for vacation on december 24th 2008 :)

But I disagree on your argument. If CacheDir is set to an absolute path, it is part of my ezpublish installation but outside of my ez webroot. I do not want to bypass root check which is a very good. I only extended that root check so that it still works if my configured cache is outside of my ez webroot.

Disabling the root check when clearing the template cache (i.e. when using the ezcache script) would be a terrible mistake in my opinion and could potentially lead to the same situation as the issue you gave as example in case something goes wrong.