Assuming the controller was in /controllers/dashboard/myprofile/myfilea.php (not in a package) you would name your class


I should also mention that the concrete naming convention is to use underscores in file names. So you would probably want to call the file my_file_a.php. This wouldn't change the name of the controller though.

I don't believe there is any naming requirements for models. If you had a file: models/my_model_a.php you should be able to name the class whatever you want then load it in with



Hope that helps

if i give the name to my file

can i use controller class name
like this?
there is no case sensitive issue in it ?

Yes, that is the class name you would use. It has to be camel cased.

if i use the directory structure like this:

It my sub directory MyProfile already contains the camel case, and my file name (MyfileA.php) contains the alternate camel case...
In that case how can i use controller class name ?

I don't believe it would let you add two single pages named MyfileA.php and MyFileA.php.

If you had MyfileA.php and my_file_a.php their respective controller names would be:


And



Only the underscores are translated to camel case.

While this works, I would recommend you always use the concrete5 convention of naming your files with underscores. It will make life much easier for you.

ok... thanks for your clarification...

i have a little bit doubt in models directory...
if i use my view file in the directory path


i had a corresponding controller file in the directory path


How to place my corresponding model file...
is there is any restriction in directory path ?


i should use my directory path like this?
is this necessary ?
Please clear my doubt...

No, you can just have your your model right in the models directory. So


Then you would do:


However, if it works better for you to put it in a subfolder for organizational purposes you can certainly do that. So if you have


You can load it in with:


Does that help?

Thank you for your response...
And two more questions i have...

1. There is any restrictions in naming for class in concrete5 mvc...?
2. In concrete5, they follow any standardized directory structure...?

Crediting yourself with an 'answer' after getting help (which you acknowledged) is not nice nor in keeping with the open source community in which you both belong and benefit.

Please fix.