#58: Switch to Dwoo_Core changed default compile and cache dir.
Issue revisions
- new by Sven Rautenberg at 2010-M-02 14:42
- closed by Jordi Boggiano at 2010-M-02 22:14
| Type |  bug |
|---|---|
| State |  closed |
| Priority |  normal |
| Resolution |  fixed |
| Assigned to | Nobody |
| Scheduled for | 1.2.0 |
| Affected versions | svn /trunk |
| Affected components | Core |
| Last change | Tuesday 2 March 2010 22:14:31 UTC by Jordi Boggiano |
Short description
Regarding commit 343 in the SVN:
Because Dwoo now extends Dwoo_Core, the default path for "compiled" and "cache" directory changed.
In the method "getCompileDir" the base directory is made up like this: $this->setCompileDir(dirname(__FILE__).DIRECTORY_SEPARATOR.'compiled'.DIRECTORY_SEPARATOR);
dirname(__FILE__) changed from "lib" to "lib/Dwoo" because the Dwoo_Core file is in this subdirectory.
In the file lib/Dwoo.compiled.php the default directory still works the same, because dirname(__FILE__) points to the "lib" directory.
This different behaviour is very undesirable. I'd be forced to create new default subdirs myself if I still want to pull Dwoo via svn-externals.
Steps to reproduce
Pull Dwoo via SVN-Externals. Do autoloading of Dwoo. Use a webserver setup (file rights) that does not allow the creation of new subdirs. Make the most basic Dwoo operation.
Expected behavior
Dwoo emits the rendered template. It uses the Path PATH_TO_DWOO-Externals/dwoo/lib/compiled/" to compile the template - this directory exists because it is in SVN.
Actual behavior
Dwoo fails with an Exception, saying: "The compile directory must be writable, chmod "PATH_TO_DWOO-Externals/dwoo/lib/Dwoo/compiled/" to make it writable".
Jordi Boggiano at Tuesday 2 March 2010 22:14:31 UTC
Sorry about that, totally forgot to fix this since the test suite sets them manually I didn't notice the error. Fixed in revision #344