Le 23/06/2011 03:18, Kevin a écrit :
Hey all,
I'm integrating the FOS UserBundle (many thanks to the bundle
developers, btw) into an application, and I'm trying to find the
cleanest way to integrate the bundle templates stylistically.
We have a base template that looks something like:
{#
Hi,
I'd really like writing somthing like:
foreach ($form as $name=$field) {
if ($field-hasErrors())
$field-setAttribute(attr, array(class = error));
}
But I can't because setAttribute is not implemented in the *
Symfony\Component\Form\Form* class (and $attributes is private).
1. Why
Thanks for the answer, it is now clear that why I get errors in the
application since I only cleared the dev cache using the command.
I also want to ask what does warming the cache up do?
On Jun 23, 12:51 am, Christophe COEVOET s...@notk.org wrote:
Le 22/06/2011 22:59, Ozzy a �crit : Hi,
I
Most of the time this error appear because of a bad initialization of your
object.
It looks like you do not have any constructor, so you don't seem to
initialize any collection which you should do if you have some. What is your
orm mapping ?
--
If you want to report a vulnerability issue on
Le 23/06/2011 09:40, Ozzy a écrit :
Thanks for the answer, it is now clear that why I get errors in the
application since I only cleared the dev cache using the command.
I also want to ask what does warming the cache up do?
It creates the cache instead of relying on the first request to do it.
Hi there,
Just replace the line:
return $this-renderComponent(product_comment, showComment,
array('comment' = $product_comment, 'class' = hidden));
with:
$text = $this-getComponent(product_comment, showComment,
array('comment' = $product_comment, 'class' = hidden));
return
Hi,
so if it's similar to the following XML, what's the getter property to
edit then for a repeated field?
class name=Acme\BlogBundle\Author
getter property=tokenValid
constraint name=True
option name=messageThe token is invalid/option
/constraint
/getter
Hi,
the current user can't be serialized apparently.
Changing private $usuario; to protected $usuario should solve that
issue. It must be done on related entities as well.
On Jun 23, 5:45 pm, Michel Salib michelsa...@gmail.com wrote:
Most of the time this error appear because of a bad
Le 23/06/2011 10:22, François CONSTANT a écrit :
Hi,
the current user can't be serialized apparently.
Changing private $usuario; to protected $usuario should solve that
issue. It must be done on related entities as well.
On Jun 23, 5:45 pm, Michel Salibmichelsa...@gmail.com wrote:
Most of
If that can help when I remove _slug in rooting.yml all work. (but i
hadn't anymore slugify URL for jobs)
PS: I hadn't repository cause I didn't succeed to did it, but I will
post my code in 3~4hours, I cant now.
--
If you want to report a vulnerability issue on symfony, please send it to
After an opinionated discussion
(http://groups.google.com/group/symfony-users/browse_thread/thread/ca3d1cd6662ca1d6/1372435731045ea0),
I've decided to create two new mailing-lists that are
*replacing* the current one:
* symfony1: http://groups.google.com/group/symfony1
* Symfony2:
11 matches
Mail list logo
