I haven't worked very much with the forms part of symfony, so I don't know
if this is related to the problem. But why are you using
admin_input_file_tag instead of the normal input_file_tag? Unless it's in
the admin generator, i don't think there's any reason to use the admin_
helpers.
On Dec 30
I use the admin_input_file_tag to allow user upload an image. But i
can't check the file type. The validator file is:
methods:
post:
-"avatar{galleryid}"
-"avatar{image}"
names:
avatar{galleryid}:
required: true
required_msg: The Gallery is required
avatar{image}:
I'm thinking that would probably only work with propel, correct?
On Dec 30, 6:02 pm, Jonathan Franks <[EMAIL PROTECTED]> wrote:
> You can override doSelect in your peer class:
>
> public static function doSelect(Criteria $criteria, $con = null)
> {
>
> // by defaul
You can override doSelect in your peer class:
public static function doSelect(Criteria $criteria, $con = null)
{
// by default order by name
/// getOrderByColumns()
if(count($criteria->getOrderByColumns()) == 0)
{
Is there a way to set how both the available and the selected lists
are sorted? Currently the only way I can get them to be given is
sorted by id. I would like to have them sorted by a field called
name.
I am currently using symfony 1.0.10 and sfDoctrine 1.0
--~--~-~--~~
sorry guys, I am so used with sf*Validators and .yml files that I
hadn't noticed the validateAction() method...
I guess I should RTFM!
yome a écrit :
> Hello,
>
> I am dynamically generating my forms (let's say for example 1 to n
> select_tags depending on other data; let's say they are named fo
Hello,
I am dynamically generating my forms (let's say for example 1 to n
select_tags depending on other data; let's say they are named fooX
where X is a number) and I would like to perform some validation on
the generated form elements. Obviously, as I don't know at devel time
how many select ta
OK, here we go:
this is a somewhat semi-crippled finished app of mine that isn't using
sfGuard, instead relying on the deeper-level Symfony facilities. There
are 5 apps, each with a separate front controller (one of which is
no_script_name). Modules that needed to be shared between apps have
been
