[TYPO3-mvc] BE module controller in separate directory
Stephen Bungert
stephenbungert at yahoo.de
Mon Nov 26 13:10:36 CET 2012
It would be nice to be able to separate them. I also have an extension with
a lot of FE controllers. I started calling all the BE one BeSomething... so
that i can see whether it is a FE module or not. But it would be nicer to
be able to use the naming conventions to have them in a diffenet folder, or
maybe just in Controllers/Be or something if it has to be hardcoded.
Stephen.
"Stefano Cecere" <scecere at krur.com> schrieb im Newsbeitrag
news:mailman.1.1353665181.22705.typo3-project-typo3v4mvc at lists.typo3.org...
> On 23/11/12 10:52, Claus Due wrote:
>> Hi Kay, Stefano,
>>
>>> should work, if you keep an eye on the naming convention:
>>>
>>> Tx_extname_Controller_Be_Controller1Controller
>>>
>>> Should be in extname/Classes/Controller/Be/Controller1Controller.php
>>
>> Woldn't that be nice? :)
>>
>> Unfortunately that will not work. As Stefano has found out, it is simply
>> impossible to place controllers in other folders, regardless of the
>> naming convention. Extbase does not detect the Controller if it is in a
>> subfolder - the only exception to this rule is CommandControllers (which
>> are defined as a raw classname, bypassing possible detection issues).
>
> yes i tried all combinations (and permutations ;( before posting here
>
> my solution now is to name my BE mod controller:
>
> ModuleMycontroller.php
>
> so i have a little diff from the other (FE) ones
>
> it's not a sad situation.. we can live with it!
>
> (and i don't want to split into different exts, since it's a an integrated
> app)
>
>
> thank you and happy extbasing!
>
>
>
> --
>
> -- --- ----- -------
>
> Stefano Cecere
> KRUR studio - http://krur.com
More information about the TYPO3-project-typo3v4mvc
mailing list