Now that Doctrine 2.1 Beta has been released can we use the MongoDB
bundle with Symfony 2.0 if we update as described here?
Andras
On máj. 11, 08:46, jarod chiang...@gmail.com wrote:
I found this very help to me on how tomongodbin symfony2Beta1
On 17 май, 23:12, Carl carl.par...@gmail.com wrote:
I think roles would make more sense when it comes to accomplishing what you
want to do here. After the object has been created and the ACL has been
updated, then you can check to see if the user has permission to view the
object.
Then why do
Job Description:
We are looking for people who are interested in developing their
career with us. Successful candidates should enjoy working in a well-
managed team environment have the enthusiasm and ambition to complete
projects to the highest standard and want to be part of an
organization
+1
--
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
+1
On Wed, May 18, 2011 at 3:11 AM, Alan Bem alan@gmail.com wrote:
+1
2011/5/18 realmfoo konstantin.leb...@gmail.com
+1
--
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
+1
On 05/18/2011 10:12 AM, Zolzaya Erdenebaatar wrote:
+1
On Wed, May 18, 2011 at 3:11 AM, Alan Bem alan@gmail.com
mailto:alan@gmail.com wrote:
+1
2011/5/18 realmfoo konstantin.leb...@gmail.com
mailto:konstantin.leb...@gmail.com
+1
--
If you
+1 since only interested of SF2
-Leo-
From: symfony-users@googlegroups.com [mailto:symfony-users@googlegroups.com] On
Behalf Of Marco Pivetta
Sent: 18. toukokuuta 2011 10:39
To: symfony-users@googlegroups.com
Subject: Re: [symfony-users] Re: Any chance of creating a new Google group for
hi
any ideas please
for the first error i added a column slug manually in the table sfguard user
but i have new error
500 | Internal Server Error | Doctrine_Record_UnknownPropertyException Unknown
record property / related component permissions on sfGuardUser
if i refresh the page i'm logged in
(symfony 1.4.10 doctrine 1.2)
Hello,
Given the following method, I use a foreach loop in the template to
show students and their group (Regroupements here). I would like to
avoid an extra query inside the loop for the group.
EtudiantTable.class.php :
===
public function
I have a wizard of few steps. Each step manage separate doctrine
entity, save it in session and proceed to next step. On one step I
have address data, and using EntityChoiceList to display countries
from database in choice (select) field.
Problem is, when I go back in my wizard, I load entity
$myEntity = $entityManager-merge($entity); //does the job :)
Marco Pivetta
@Ocramius http://twitter.com/Ocramius
http://marco-pivetta.com
On 18 May 2011 15:25, umpirsky umpir...@gmail.com wrote:
I have a wizard of few steps. Each step manage separate doctrine
entity, save it in session and
Hello,
I'm overriding the templating.helper.assets class in my config.yml
file and have to replicate the following constructor argument from
templating_php.xml:
argument type=service id=request strict=false /
Trying it the following way:
templating.helper.assets:
class:
Le 18/05/2011 15:48, Valera a écrit :
Hello,
I'm overriding the templating.helper.assets class in my config.yml
file and have to replicate the following constructor argument from
templating_php.xml:
argument type=service id=request strict=false /
Trying it the following way:
I'm using money field on a form and ran into a peculiar problem. If
I enter in a plain zero, 0, I get no error or exception, but the field
is not updated in the database. Any other integer value works, and
entering 0.0 works, but the plain 0, not so much. My boss is not
pleased.
I can work
my.service is just a service class defined like the following
my.service:
class: Acme\AcmeBundle\Service\MyService
Removing the setter injection does not have any effect - the same exception
is still shown.
---
WBR, Valera
On Wed, May 18, 2011 at 17:00, Christophe COEVOET
Le 18/05/2011 16:06, Valera a écrit :
my.service is just a service class defined like the following
my.service:
class: Acme\AcmeBundle\Service\MyService
Removing the setter injection does not have any effect - the same
exception is still shown.
Ah sorry, it was for the request
Le 18/05/2011 16:18, Valera a écrit :
Unfortunately, no luck anyway... With the following config:
request:
class: Symfony\Component\HttpFoundation\Request
templating.helper.assets:
class: %templating.helper.assets.class%
arguments: {type:service, id:@request,
I'm working on an SF2 app (my first) and am looking for some guidance
wrt. access controls. I don't think ACLs fit the requirements so I
thought I'd ask around and see if someone has run into something
similar and has some thoughts to share.
The purpose of the application is to manage Log
Hey folks!
With symfony 1.4, I used sfFeed2Plugin quite a bit.
With Symfony2, there is SF2-FeedImportBundle, but it doesn't look like
it's received much attention.
How do people like to handle RSS and Atom with Symfony2?
--
If you want to report a vulnerability issue on symfony, please send
I think you could filter the available pool of widgets/logs when you select.
At the user level, where they can edit their logs, they would be owner of
the entity in the acl.
Any higher role bypasses the ownership check, or you could assign a user
with these roles a
class-scope permission.
Hi,
I'm getting this error:
Declaration of PayPal::raiseError() should be compatible with that of
PEAR::raiseError()
These are PayPal::raiseError() and PEAR::raiseError() respectively:
function raiseError($message = null,
$code = null,
Le 18/05/2011 20:48, Javier Garcia a écrit :
Hi,
I'm getting this error:
Declaration of PayPal::raiseError() should be compatible with that of
PEAR::raiseError()
These are PayPal::raiseError() and PEAR::raiseError() respectively:
functionraiseError($message = null,
Hi Benjamin,
You can use the collection constraint for this.
use Symfony\Component\Validator\Constraints\Collection;
use Symfony\Component\Validator\Constraints\NotNull;
$defaults = array('foo' = 'bar');
$form = $factory-create('form', $defaults, array(
23 matches
Mail list logo
