2

Answer:

Kohana 3.3, they didn't take into account case-sensitivity on folders/files (they capitalized some directories/files) so this is going to drive some folks nuts when they start switching to the new Kohana (just like I did).

I switched back to Kohana 3.2 until this has been fixed.


Thank you very much for taking time in reading my huge post I had about this silly problem, and I hope this answer saves a poor souls life in the future =)

adamj
  • 4,672
  • 5
  • 49
  • 60

2 Answers2

5

It is not correct that "they didn't take into account case-sensitivity on folders/files." The change was a conscious decision, as documented in the guide under "Upgrading from v3.2".

Kohana 3.3 adds partial support for the PHP Framework Interop Group's PSR-0 standard. PHP framework developers are encouraged to follow this standard to simplify interaction between frameworks.

One of the requirements of PSR-0 is that the class names and file names match. Previously, Kohana used Title Case class names but lowercase file names. Now, the case of both matches. If you look, you will see that all Kohana class files have been uppercased.

This will not be "fixed" in a future release because the lowercase filenames were "broken" and now they are fixed.

In general, Kohana sometimes introduces breaking changes between versions, but you should always be able to find them in the guide.

Moshe Katz
  • 15,992
  • 7
  • 69
  • 116
  • Ah I guess I should have kept a closer eye on it. Though I must say making the framework compatible with a certain standard and then breaking the framework's functionality is fairly bad. I guess Linux based servers will be mostly affected since they have issues with case-sensitivity. In any case, it's a matter of fix one thing and break a million in the process haha. Thank you for your reply. – adamj Nov 07 '12 at 13:41
1

If I am not wrong, you can work from subdirectory. Just mention it in your application/bootstrap.php file:

Kohana::init(array(
    'base_url' => '/subfolder',
));