On Fri, Sep 28, 2012 at 11:55 AM, Brad Giessing itsmer...@gmail.com wrote:
I created a function called list() in a controller and it freaked out. I
guess it doesn't like that, either.
That's a PHP thing.
--
Like Us on FacekBook https://www.facebook.com/CakePHP
Find us on Twitter
AM UTC-5, John Andersen wrote:
Hi all,
Is there reserved words in CakePHP, which I can't use when naming my
models?
For example collection and tag.
Enjoy,
John, Latvia
--
Like Us on FacekBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
I created a function called list() in a controller and it freaked out. I
guess it doesn't like that, either.
On Wednesday, April 15, 2009 5:22:14 AM UTC-5, John Andersen wrote:
Hi all,
Is there reserved words in CakePHP, which I can't use when naming my
models?
For example collection
15, 2009 5:22:14 AM UTC-5, John Andersen wrote:
Hi all,
Is there reserved words in CakePHP, which I can't use when naming my
models?
For example collection and tag.
Enjoy,
John, Latvia
--
Like Us on FacekBook https://www.facebook.com/CakePHP
Find us on Twitter http
If you replace Cake pages controller you _should_ use Page/Pages :)
On Apr 16, 8:52 pm, Grzegorz Pawlik grzegorzpaw...@gmail.com wrote:
Additionally You rather shouldn't name Your model/controller like
Object/Objects and Page/Pages ;)
On Apr 16, 12:52 pm, Mark (Germany)
Class names could be defined not to conflict with possible object
names, for example by always having class names prefixed with a T,
TAppController, TController, TObject etc.
Just a suggestion :)
John
On Apr 16, 4:52 pm, Grzegorz Pawlik grzegorzpaw...@gmail.com wrote:
Additionally You rather
yeah
i once proposed to change components into
$this-FileComponent-foo()
etc with Component attached to prevent this from happening
but they did not care about that much in the core team at that point
in time :)
PS: same with helpers (conflicts between vars from controller):
$poll (content
Additionally You rather shouldn't name Your model/controller like
Object/Objects and Page/Pages ;)
On Apr 16, 12:52 pm, Mark (Germany) dereurom...@googlemail.com
wrote:
yeah
i once proposed to change components into
$this-FileComponent-foo()
etc with Component attached to prevent this from
Hi all,
Is there reserved words in CakePHP, which I can't use when naming my
models?
For example collection and tag.
Enjoy,
John, Latvia
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post
Is there reserved words in CakePHP, which I can't use when naming my
models?
http://api.cakephp.org/classes
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
CakePHP group.
To post to this group, send email to cake
In addition to the classes - http://api.cakephp.org/classes, there are
also the global constants and functions -
http://book.cakephp.org/view/120/Global-Constants-and-Functions
-teh
On Apr 15, 5:22 am, John Andersen j.andersen...@gmail.com wrote:
Hi all,
Is there reserved words in CakePHP
Thanks Dardo and Teh, but it turned out to be a conflict between all
my models, when I loaded them all in an installations controller :)
Solved by loading the models only by request (ClassRegistry).
Enjoy,
John
On Apr 15, 5:14 pm, Teh Treag tehtr...@gmail.com wrote:
In addition to the
There can be also conflict between models and components names (not
classnames).
On Apr 16, 1:45 am, John Andersen j.andersen...@gmail.com wrote:
Thanks Dardo and Teh, but it turned out to be a conflict between all
my models, when I loaded them all in an installations controller :)
Solved by
Thanks Dr. Loboto,
That may be, but not in my case, as I don't use any components
together with my installations controller, and each model, loaded by
request, does not have any conflict with CakePHP or other parts, so to
sum it up, I am happy with that :)
Enjoy,
John
On Apr 16, 5:36 am, Dr.
14 matches
Mail list logo
