I had to do the very same, but instead of displaying to me the "Call to protected method Model::_deleteDependent() from context 'SoftDeletableBehavior' " it tried to execute the query "_deleteDependent"....
On Monday, September 19, 2011 9:52:14 PM UTC-5, #2Will wrote: > > ok, so i wrapped the protected methods in the appModel. Surely this > is a hack? now the behaviour isn't very self contained and the methods > that clever core devs protected are now exposed by me. > > so anyway, its working. i forked marianos code on github. but i > doubt its the best way. > > will > > > On Sep 19, 6:49 pm, "#2Will" <[email protected]> wrote: > > Thanks for replies, appologies for the multiple posting. > > > > > Well, you can just use the public method `public Model::delete($id = > > > null, $cascade = true)`, which will call `protected > > > _Model::_deleteDependent($id, $cascade) > > > > The behaviour is skipping delete in favor of making the record as > > deleted = 1 so that records can be un-deleted or whatever. so i > > don't think i can call delete. > > > > > Why declaring a function protected if you want to use it outside of > > > descendant classes. > > > > I'm not: the method is in the core. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
