This is a known Issue. There are several key words like Module, Action, and
Request, that Symfony requires to operate. Fabien has stated that this will
be changed in future versions.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
On Behalf Of Martin Kreidenweis
Sent: Friday, December 22, 2006 9:52 AM
To: [email protected]
Subject: [symfony-devs] Re: Admin Generator problem with table named
"action"
Hi.
As explained in the title, I have (unfortunately) a DB table named
"action". And that upsets the Admin Generator when I try to save an
edit form. I get a 404 error with the following notice at the very
start:
Array to string conversion in /lib/controller/sfController.class.php on
line 117
The symfony routing/controller provides a request parameter named
"action", that contains the action to be executed.
And an admin generator for the model class "Action" tries to pass the
object data in a request parameter called "action", too.
So this object data array overrides the real action, which is lost. The
controller then tries to call the action "Array", which results in the
404 you get. (You can't pass parameters called "module" either.)
IMHO the internal module parameter should be renamed to something like
"sf_action" to get rid of this limitation, but that might break BC...
Martin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "symfony
developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
