I guess you can only provide what the Protocol supports.
Have you had a good look through the RFC For v4rev1 ?
http://tools.ietf.org/html/rfc3501
Interested to see how you go with it.
Cheers.
On Oct 2, 12:58 am, "Siegfried Hirsch" <[EMAIL PROTECTED]>
wrote:
> Hi everybody
>
> I am just lookin
Hi everybody
I am just looking into the imap skeleton, that was provided by gwoo in the
bin some time ago. So far I have implemented some basic read functionality.
But now I am thinking about the further implementation of the imap
datasource.
Here are some questions, that I am not sure about:
- s
Grant, I'm wondering how you can encorporate this functionality in all
your controller actions. For instance, if i have an edit action,
then the id gets passed in to that function as its in the url.
However, in an add operation there is no current id yet.
Thus, i can't call this user defined funct
http://cakebaker.42dh.com/2007/01/03/validation-with-cakephp-12/ <<
Assuming that you're working in 1.2, this describes how you can do multiple
validation rules in 1.2. you define the validation in each model. if you
have a custom validation function that you want shared across all models, i
would
best place for validation of data is in models, but it's flexible
enough ;)
look for $validation member in Model class, and also beforeValidation
callback
On 20 juin, 09:35, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Ok one more question.. If i have multiple controllers that i want all
> t
Ok one more question.. If i have multiple controllers that i want all
to use some validation method, where would be the best place to put
the validation method?
On Jun 17, 5:28 pm, Grant Cox <[EMAIL PROTECTED]> wrote:
> I would keep the functionality in separate controllers, not bloat your
> User
Thanks for the suggestions. I'll have to try that out when i get out
of work.
On Jun 17, 5:28 pm, Grant Cox <[EMAIL PROTECTED]> wrote:
> I would keep the functionality in separate controllers, not bloat your
> Users one just because you want to access the User model. To ensure
> that users canno
I would keep the functionality in separate controllers, not bloat your
Users one just because you want to access the User model. To ensure
that users cannot view/edit someone elses data you just need to
incorporate this into whatever ACL you use. For our application I
have a function in app_mode
Ok so i am making a website where one can monitor energy usage for
there home (or homes)
The database design is as such:
Users have many homes. Homes have many rooms.. Rooms have many
appliances.
Now the main view for the users shows all of this at once. Now what i
want to do is create the forms f
Thanks Grant. Appreciate your thoughts.
On 1/23/07, Grant Cox <[EMAIL PROTECTED]> wrote:
>
> Well, it is debatable. Since controllers are the users interface to
> your application - what are the users trying to achieve? Are they
> aware of Orders being separate to Practices, and will they want
Well, it is debatable. Since controllers are the users interface to
your application - what are the users trying to achieve? Are they
aware of Orders being separate to Practices, and will they want to
access methods specifically to Orders? If so, it should have its own
controller.
If you have
Hello world,
I am new to CakePHP and getting around the framework quite quickly. If
some of the developers watch this list, my compliments for the recipe.
Now I have been actively using the hasMany and hasAndBelongsToMany
feature to model my data, in my example a Medical Practice has many
users
12 matches
Mail list logo
