I had the same problem. And every time, I had to correct the view script filename manualy.
There is one more problem (not sure if it is a problem): When you create a new controller within a module, the class name in the controller file does not have the module name as the prefix. For example, if you create a controller file named "gallery" under module "admin", the class name is given only as class GalleryController extends Zend_Controller_Action whereas it should be class Admin_GalleryController extends Zend_Controller_Action As I said not sure if it is a bug/problem but we have to correct the classname everytime we create a controller under a module. scs On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <umpir...@gmail.com> wrote: > Will use this topic to ask sth. > When generating controllers like TwoWordsController if you run zf controller > twoWords, view script folder gets name like twoWords instead two-words, > similar problem occurs with controller name when running zf controller > two-words. > Is this a bug? > > Regards, > Saša Stamenković > > > On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <ralph.schind...@zend.com> > wrote: >> >> I am tackling several of these features now, in preparation for the 1.10 >> release (this code is and will be in the incubator.) >> >>> Can anyone elaborate on the .zf.ini properties that are respected or what >>> one >>> needs to do to set up custom profiles? >> >> Custom profiles are pretty much completely, they mostly need documenting. >> Overall, the docs need to be better organized. Currently if you put a >> project file in your storage directory at (for example): >> >> .zf/project/profiles/custom.xml >> >> Then with 1.10 zf client, you'll be able to use it like >> >> zf create project -n custom ./directory >> >> This works on my system, but needs to be more throughly tested. >> >> >>> Ultimately id like to change the project layout a bit. But for now ill >>> settle for enabling certian things. For example these are the key things >>> i >>> want by default in every project: >>> >>> - Config file format should be XML not INI >>> - Data dir with log, cache, and uploads >>> - Public dir with images, js, css >>> >>> It seems like all this is doable with jsut certain attribs set on the >>> .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to >>> get it to work. >> >> These types of things can definitely be handled by a custom profile. TO >> that though, there are probably a few places where having attributes persist >> into the context object make sense (this would make it easier to customize >> things like the name of a directory or file). >> >> I'll keep you updated via the mailing list on the new features I'll be >> pushing out this week. >> >> -ralph > >
