yes never use the context in your model.
if you have on your action
$object = $this->from->getObject()->setUserId($this->getUser()->getId());
$this->from->save();
the solution of gabriel is nice you can use the option of your form for
inject the user_id or guard user object.
good luck
2010/12/12
On Sunday, December 12, 2010 10:27:56 PM UTC+2, Javier Garcia wrote:
Yes, you are right, I have tried it and it gives me an error about the
permissions of the file. But, what is the "web process"? the www-data
user? You say also "depending n your setup", so is there any setup
process that allow to
On 12/12/2010 08:19 PM, Gabriel Petchesi wrote:
For me your proposal looks more complicated, think about the following
problems:
1. No write access to the security.yml files
Depending on your setup the web process may not access those file to
update them.
Yes, you are right, I have tried it
Hi,
It is a bug and has been fixed.
https://github.com/fabpot/symfony/commit/ddd05cfce4f4ff2863350f7051679725cda26cfcf
The bug was introduced after PR4, which is the version you should use
if you want to try out the framework.
On Dec 11, 7:30 pm, Gyula Sallai wrote:
> Hello everyone!
> I starte
For me your proposal looks more complicated, think about the following
problems:
1. No write access to the security.yml files
Depending on your setup the web process may not access those file to
update them.
2. Cleaning the cache after each update
You have to clear up the symfony cache after ea
Hi again, thanks for your responses.
What about just reading/writing each file security.yml looking for the
"credentials:" key ? Then I would parse each file looking for the line
where the "credentials:" key is and would add/remove credentials in
that line...
On Nov 26, 8:24 pm, pghoratiu wrot
Hi,
Issue Solved :)
I upgraded
PHP - 5.2.9 to 5.3.3 ,
MYSQL - 5.0.9 to 5.1.41 ,
PDO, PDO_MYSQL - 5.0.91 to 5.1.41 ,
and
APACHE to 2.2.14
Solved my Problem.
On Dec 7, 8:18 pm, Alex Pilon wrote:
> Hmm, well I do not know what might be causing this error as I have never
> myself received a
I'm answering to myself, but I found a way to handle this:
http://docteurklein.posterous.com/36073492
--
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 u
Although this solves the problem it is not the recommended way of doing
things.
Think about loading/importing data via fixtures, from the CLI, where
you have no session thus an invalid user_id will be inserted.
Also you may not want to automatically update this field when an object
is saved due to
Heyy!
After some searching I replace the line
$this->setUserId($this->getUser()->getGuardUser()->getId());
with
$this->setUserId(
sfContext::getInstance()->getUser()->getGuardUser()->getId());
And it works now!
On Sun, Dec 12, 2010 at 2:08 PM, khalid wrote:
> Hi,
> the relation name is guardUser
Hi,
the relation name is guardUser
$this->setUserId($this->getGuardUser()->getUser()->getId());
ps: The problem are you cannot set the user when the object is new ? this
line must be in the action not in your model. because you set the current
user_id, the guard_user_id it'sz$ différente of use
Thanks Francis.
I was missing the backslash :)
--
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 symfo
12 matches
Mail list logo
