Well, that's an authentication issue, which is certainly a topic in itself. I don't really have any recommendations (there seems to be a number of authentication modules for cake, in various stages of development). So far I have just stored the PK in the session when the user is authenticated, and it uses that when saving.
But no, the Save function does not care where you call it from. I personally see this as a benefit :) [EMAIL PROTECTED] wrote: > Thanks first, > Whether you disable the primary key input field or use a hidden > field,the users can make a html file by view the source of you file > and then modify it(cancel your disable property or changes the hidden > filed to visible input).after make a file ,he login in,choose the data > which has the PK value he want to edit,then open the html doc he > modified from IE's file menu... > > I thought that the save method will judge if it was called by 'Edit' > action it only do a update query,if it was called by 'Add' action then > it do insert query,but it does not do such a judgement. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
