I just read over my original post, and realised I was getting the two issues confused: Modules and Models (ahem). But to try to clarify:
On 26 Oct 2009, at 09:11, Felix Gilcher wrote: > this is indeed not an issue that needs fixing. If you choose to name > you module or action "admin" because you prefer lower-case letters at > the start we let you do this. You'll need to refer to it as "admin" > with a lower case letter any where else in the code. Or do I miss > something and it fails even if you're using the same case everywhere? It's the *lack* of failing when different capitalisation is used on OS X that's the issue, 1. For the capitalisation of *models*, the getModel method is case insensitive on OS X, but case sensitive on Linux. Therefore code that works on OS X will fail on Linux (as I discovered). If the incorrect capitalisation is used as an argument to getModel, I think it should fail in both cases. 2. For the capitalisation of *modules*, during the action-create script, using the incorrect capitalisation will not fail the script on OS X: it will appear to finish properly. However, the script uses this incorrect capitalisation in generated class names, and so then when PHP comes to use them, it will then fail later (as I discovered). I think the script should test for the correct capitalisation and fail if it's wrong. Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
