Maybe your problem is a bug, but..... Why do you want to use a simple inheritance. I don't think that it's usefull at all. I think that you can do what you want without it..
Tell us what is your goal. Maybe this article would be good to read (and also the comments) http://jasonswett.net/inheritance-with-symfony-and-doctrine-orm/ On 30 čnc, 21:55, Javier Garcia <tirengar...@gmail.com> wrote: > I created this ticket: > > http://trac.symfony-project.org/ticket/8922#preview > > Javi > > On Jul 28, 10:06 pm, Javier Garcia <tirengar...@gmail.com> wrote: > > > > > Thanks, but it didn't work. > > > On 07/28/2010 09:20 PM, John Kary wrote: > > > > This probably won't work, but try explicitly defining a different > > > field name for the slug using the "name" option: > > > > Usuario: > > > actAs: > > > Sluggable: > > > unique: true > > > fields: [nombre_apellidos] > > > canUpdate: true > > > name: 'myslug' > > > > On Jul 27, 10:57 am,JavierGarcia<tirengar...@gmail.com> wrote: > > >> On Jul 20, 12:00 pm, Tom Ptacnik<to...@tomor.cz> wrote: > > > >>> Maybe colision with inheritance? Try to move inheritance before actAs > > >>> (only guess) > > >> Yes there is a colision with inheritance. When i remove the > > >> inheritance it works ok. > > > >> I changed the position of inheritance but the field slug doesn't > > >> appear.. > > > >> Any other idea or should i consider this is a bug? > > > >> Javi -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
