Take a look here:
http://www.codemassacre.com/2009/04/27/symfony-12-admin-with-custom-primary-key/
Daniel
On Jul 12, 9:06 am, PePe_el_Romano wrote:
> Good dear group:
> I am writing to see if someone has this same error occurred and has
> solved, or if they are aware of it.
>
> Problem descrip
How is possible that if you list a utilisateus the url is "/
utilisateurs/:id" . It should be only /utilisateurs , right?
On 10 bře, 09:33, "NOOVEO - Christophe Brun" wrote:
> I'm trying to use sfDoctrineApplyPlugin, I have been asked to display 2
> backend pages : one to handle administrators,
For all people interested in this issue:
The darn virtual host directive contained a «Multiviews» option in its
directory subdirective. Got rid of it: bingo! 3 days of idleness
NameVirtualHost 127.0.0.1
ServerName localhost
DocumentRoot C:\yadiyada
Op
routing.yml:
homepage:
url: /
param: { module: indexsplash, action: index }
default_symfony:
url: /symfony/:action/*
param: { module: default }
default_index:
url: /:module
param:
Could it be that your .htaccess file is messed up? Could you maybe
post that file, the contents of your routing.yml and that of
settings.yml here? Otherwise it's quite hard to help you.
Bernhard
--~--~-~--~~~---~--~~
You received this message because you are subs
On 18 déc, 01:18, "Bernhard Schussek" wrote:
> Hi,
>
> Is no_script_name turned on for the given environment in settings.yml?
>
> Bernhard
Hi,
Yes, it's turned on in all envs.
My difficulties are getting worst: even though I commented out the
language action of the index module, and got rid
Hi,
Is no_script_name turned on for the given environment in settings.yml?
Bernhard
--~--~-~--~~~---~--~~
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@googleg
thank you ant,
you led me the right direction. in my code i still had named :action
as :test
so the following works:
content:
url:/:action
param: { module: content }
requirements:
action: "company|products|contact"
regards, lowshoe
--~--~-~--~~~-
You dont need to define action if that symbol will always be there.
/:action means thats the action name since you defined the module i
think it should work.
did you try leaving out the action in the param entry?
lowshoe wrote:
> hi all,
>
> i'm quiet new to symfony. currently i'm fiddling ar
Thanks a lot Lee!
That worked great.
See ya
On Jun 17, 4:44 pm, Lee Bolding <[EMAIL PROTECTED]> wrote:
> You need to modify your .htaccess to skip routing rules for files
> ending .rss
>
> Add : RewriteCond %{REQUEST_URI} !\.rss$
>
> after the line with !\.html$ in it.
>
> On 17 Jun 2008, at
You need to modify your .htaccess to skip routing rules for files
ending .rss
Add : RewriteCond %{REQUEST_URI} !\.rss$
after the line with !\.html$ in it.
On 17 Jun 2008, at 20:28, Centerax wrote:
>
> Hello guys.
>
> I've this problem:
> in my dev environment I can access this url
> www.d
> The problem now is that matching is done before connecting
> all the prepended routes (seems so) which ends in matching one of
> the default routes from routing.yml - only these are available
> for the parser in sfRouting at this point.
Are you using sf1.1? If so, this is a known problem curre
the problem is that this routing rule is only a simplified example of my
routing rules, which are more complex. If i don't find a solution it means a
lot of routing rules (very slow) :S
Thanks.
On 8/31/07, David Brewer <[EMAIL PROTECTED]> wrote:
>
>
> Oh, I see. I don't know if the routing rules
Oh, I see. I don't know if the routing rules work that way or not, I
always thought that anything you defined specifically under param
would override anything that came from the url.
When I've wanted to do things like this in the pass, I would use two
or more different rules:
url: /:mode
param
Hi David,
thanks for your answer. I defined category1 under param to give it a default
value to avoid another routing rule when there isn't category1 on the url.
On 8/31/07, David Brewer <[EMAIL PROTECTED]> wrote:
>
>
> Try this variation on your routing rule:
>
> url: /:mode/:category1
> param:
Try this variation on your routing rule:
url: /:mode/:category1
param: { module: categories, action: show }
requirements: { mode: ^(basic|premium), category1: \d+ }
You don't need to define settings for the category1 or mode parameters
under 'param' as since they are part of the URL, they will
16 matches
Mail list logo
