A favourite of mine was a colleague who wasn't very literate (or
hygienic). When he spell checked his docs in Word, if a word wasn't
found, he'd add it to the shared dictionary. It wasn't found because
he'd spelt it so badly. Anybody else spell checking their work would
then have correct spellings
Another one for you $this->referer(), not cakes fault as it is a
widely adopted misspelling for the referring page.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to
That particular misspelling has bugged me for years. It was actually a
keyword in a language I used to use.
On Feb 16, 5:42 pm, WebbedIT wrote:
> Hi Leo,
>
> It certainly seems to be down to allowEmpty which the book states ...
>
> "When set to true, an empty field will skip *all* validation on
Hi Leo,
It certainly seems to be down to allowEmpty which the book states ...
"When set to true, an empty field will skip *all* validation on the
field"
Well spotted on the dependency typo, I have relied on spell checkers
too much in life and NetBeans does not catch those for me :o)
Paul.
--~-
I've just looked at some old code and I recall that I had to leave the
message string empty for it to work. I didn't have a problem with the
position of allowEmpty = true.
then in the form, I handles the message like this:
echo $form->label('title', __('TITULO_GA_BLOCS',true));
echo $for
I have a feeling that by assigning allowEmpty = true to my first rule
it then skipped all validation when the field was empty ... by moving
my second rule to be the first rule I seem to have overcome my
problem.
What are your thoughts on this? Should allowEmpty on one rule affect
all subsequent r
Also, you've misspellt dependency ;)
On Feb 16, 4:05 pm, leo wrote:
> Just a quick thought without really looking into it: try prepending
> the fields with the model name viz: Something.date_operational
>
> L
>
> On Feb 16, 4:00 pm, WebbedIT wrote:
>
> > Hi,
>
> > Can anyone spot what I am doin
Just a quick thought without really looking into it: try prepending
the fields with the model name viz: Something.date_operational
L
On Feb 16, 4:00 pm, WebbedIT wrote:
> Hi,
>
> Can anyone spot what I am doing wrong? I have read the book and a few
> blog articles on this and think I have ever
Hi,
Can anyone spot what I am doing wrong? I have read the book and a few
blog articles on this and think I have everything setup right but
can't get validation to apply more than one rule to a field (processes
first rule, ignores the rest).
Here is my validate declaration for the field in ques