Re: [symfony-users] Routing problem

2011-06-17 Thread Gábor Fási
This should help:
http://www.symfony-project.org/more-with-symfony/1_4/en/02-Advanced-Routing

On Thu, Jun 16, 2011 at 10:30, Noussan goumbetti  wrote:
> Hi Everybody,
>
> I develop a project on symfony and I need to associate a module :
> "botte"
> to a subdomain adress "botte.domain.com", somebody know how can I do
> please ?
>
> thank you,
> have a good day.
>
> --
> 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 this group, send email to
> symfony-users+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en
>

-- 
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 this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en


[symfony-users] Routing problem

2011-06-17 Thread Noussan goumbetti
Hi Everybody,

I develop a project on symfony and I need to associate a module :
"botte"
to a subdomain adress "botte.domain.com", somebody know how can I do
please ?

thank you,
have a good day.

-- 
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 this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en


[symfony-users] Routing problem with Symfony

2010-11-27 Thread Djahid Bekka
I started to learn Symfony (http://www.symfony-project.org/jobeet/1_4/
Propel/en/03), but i am blocked on the lesson 3 (The data model).

I followed the instructions, and there are my settings file :

1) I am on Ubuntu 10.10
2) In /etc/apache2/sites-available/
I created the file jobeet : like this


  ServerName dev.jobeet.com
  DocumentRoot "/home/user/workspace/web/php/symfony/jobeet/web/"
  DirectoryIndex index.php
  
AllowOverride All
Allow from All
  

   Alias /sf /usr/share/php/data/symfony/web/sf
  
AllowOverride All
Allow from All
  


then I do this command :  sudo a2ensite jobeet

In the /etc/hosts  I added the line :
127.0.0.1 dev.jobeet.com

My problem is this :

I get the page http://dev.jobeet.com   as expected in the tutorial
Also I get the page http://dev.jobeet.com/frontend_dev.php as expected

BUT when i try this : http://dev.jobeet.com/frontend_dev.php/job I get
this error message :

The requested URL /frontend_dev.php/job was not found on this server.
Apache/2.2.16 (Ubuntu) Server at dev.jobeet.com Port 80

Of course I have already done this command :
php symfony propel:generate-module --with-show --non-verbose-templates
frontend job JobeetJob

-- 
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 this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en


[symfony-users] Routing problem for generate-admin with id: type string (128)...

2010-07-12 Thread PePe_el_Romano
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 description:
 For reasons of replicate Master - Master, which is necessary for my
system the identifier for each table it must be a varchar to type
"name_value" Zera_3 after generating modules to generate-admin, when I
give a save or update to an item, I get the error, let them then gave
me this error even for a show, for an edit, for each share of the
module, with the Xdebug I realized that the problem was that
routingColection generated for each module, and as an alternative, we
create a new routing for every action I leave an example here too with
sfGuardUser for
edit action.

routing.yml:
sf_guard_user_edit:
  url: /sf_guard_user/:id/edit
  class: sfDoctrineRoute
  options:
model:sfGuardUser
module:   sfGuardUser
type: object
prefix_path:  sf_guard_user
column:   id
  param: { module: sfGuardUser, action: edit}

Error:
Type: 404 | Not Found | sfError404Exception
Action "sf_guard_user/Zera_1" does not exist.
stack trace

* at ()
  in SF_ROOT_DIR\lib\vendor\symfony\lib\controller
\sfController.class.php line 202 ...
 199. $this->dispatcher->notify(new sfEvent($this,
'application.log', array(sprintf('Action "%s/%s" does not exist',
$moduleName, $actionName;
 200.   }
 201.
 202.   throw new sfError404Exception(sprintf('Action
"%s/%s" does not exist.', $moduleName, $actionName));
 203. }
 204.
 205. // create an instance of the action
* at sfController->forward('sf_guard_user', 'Zera_1')
  in SF_ROOT_DIR\lib\vendor\symfony\lib\controller
\sfFrontWebController.class.php line 48 ...
  45.   }
  46.
  47.   // make the first request
  48.   $this->forward($moduleName, $actionName);
  49. }
  50. catch (sfException $e)
  51. {
* at sfFrontWebController->dispatch()
  in SF_ROOT_DIR\lib\vendor\symfony\lib\util\sfContext.class.php
line 159 ...
 156.*/
 157.   public function dispatch()
 158.   {
 159. $this->getController()->dispatch();
 160.   }
 161.
 162.   /**
* at sfContext->dispatch()
  in SF_ROOT_DIR\web\administracion_dev.php line 13 ...
  10. require_once(dirname(__FILE__).'/../config/
ProjectConfiguration.class.php');
  11.
  12. $configuration =
ProjectConfiguration::getApplicationConfiguration('administracion',
'dev', true);
  13. sfContext::createInstance($configuration)-
>dispatch();

Greetings Rolian.

-- 
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 this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en


[symfony-users] Routing problem with sfGuardUserProfile

2010-03-10 Thread NOOVEO - Christophe Brun
I'm trying to use sfDoctrineApplyPlugin, I have been asked to display 2
backend pages : one to handle administrators, the other one to handle
other users. 
I have generated 2 modules on the backend side. 
 
In routing.yml, the 2 routes are identical : 
utilisateurs:
  class: sfDoctrineRouteCollection
  options:
model:sfGuardUserProfile
module:   utilisateurs
prefix_path:  /utilisateurs
column:   id
with_wildcard_routes: true
 
administrateurs:
  class: sfDoctrineRouteCollection
  options:
model:sfGuardUser
module:   administrateurs
prefix_path:  /administrateurs
column:   id
with_wildcard_routes: true
 
In both config/generator.yml, the params are also identical : 
(utilisateurs)
  class: sfDoctrineGenerator
  param:
model_class:   sfGuardUserProfile
theme: admin
non_verbose_templates: true
with_show: false
singular:  ~
plural:~
route_prefix:  utilisateurs
with_doctrine_route:   true
actions_base_class:sfActions
 
(administrateurs)
  class: sfDoctrineGenerator
  param:
model_class:   sfGuardUser
theme: admin
non_verbose_templates: true
with_show: false
singular:  ~
plural:~
route_prefix:  administrateurs
with_doctrine_route:   true
actions_base_class:sfActions
 
 
But the behaviour of the application is not the same : if I try to list
the 'utilisateurs' backend page, symfony throws a routing error : 
The "/utilisateurs/:id.:sf_format" route has some missing mandatory
parameters
 
An url like backend_dev.php/utilisateurs/6/edit throws the same error. 
Any idea of what I am missing here ? 

-- 
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 this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en


[symfony-users] Routing problem

2008-12-17 Thread Kostrowsky

Hi,

Can't seem to get a simple routing to work properly (Symfony 1.0.14)

http://localhost/index.php/index/language : does point to module
«index», action «language»

http://localhost/index/language: gives me the Symfony 404

When using the last URL, the log indicates that the routing rule used
is:

default_index:
  url:   /:module
  param: { action: index }

which tries to locate the module «language», action «index» (the
module «language» does not exist)

I have tried to specify, prior to all rules:

language:
  url:   /index/language
  param: { module: index, action: language }

But no match occures, and the default_index rule is wrongly used, with
the same log trace.

Thanks for any help.

--~--~-~--~~~---~--~~
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 this group, send email to 
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---



[symfony-users] Routing Problem with dynamic actions

2008-12-13 Thread lowshoe

hi all,

i'm quiet new to symfony. currently i'm fiddling around with mapping a
dynamic url parameter to the name of an action.
i have a module 'content' which i would like to use as default module
for a number of actions.
suppose i have te following actions:

"/company", "/products", "/contact"

per default, symfony thinks this all are module-names. but i want them
to be handled as actions of the same module. i would like to have an
entry like this in routes.yml:

content:
url:/:action
param:  { module: my_module, action:$action }
requirements:
action: "company|products|contact"

but i don't know how to hand over the :action as dynamic param to
param: {...}

any ideas?

regards, lowshoe

--~--~-~--~~~---~--~~
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 this group, send email to 
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---



[symfony-users] Routing problem

2008-06-17 Thread Centerax

Hello guys.

I've this problem:
in my dev environment I can access this url 
www.domain.com/frontend_dev.php/news.rss
but when I try to go to : www.domain.com/news.rss
I get 404, I don't know why, this never happened to me.

the Routing rule I have is
rss:
  url:   /news.rss
  param: { module: feed, action: lastNews }

thanks!
--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---



[symfony-users] routing problem

2008-02-02 Thread Jan-Peter Hagenmüller


No, I'm using 1.0.11. But now - on a fresh new day and mind :-)
I found the problem. I started a new project environment and
migrated all apps and plugins one by one. Everything worked
fine until the installation of the sfTCPDFPlugin...
It seems that the config for that plugin breaks the connecting
process of routes somehow - I did not spend more time on that,
so I removed it and everything worked fine. Unfortunately
this plugin came with several other plugins a few weeks ago,
so I did not remember all changes in detail.

Thanks for your reply!

jp







On Sat, 02 Feb 2008 12:21:31 +0100, Ian P. Christian <[EMAIL PROTECTED]>  
wrote:

>
>
>> 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 currently.
>
> >



--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---



[symfony-users] routing problem

2008-02-01 Thread Jan-Peter Hagenmüller


Hello,

I use to prepend routing rules in my plugin's config.php
There was no problem doing so until a few days, when I
made some major refactorings.

usually all routes including those prepended are "connected"
before sfRouting parses them all and finds the matching rule:

logs as expected for domain.de/login.html:
--
Feb 02 00:12:49 symfony [info] {sfRouting} connect "/message"(".html"  
suffix)
Feb 02 00:12:49 symfony [info] {sfRouting} connect  
"/notImplementedYet"(".html" suffix)
Feb 02 00:12:49 symfony [info] {sfRouting} connect "/login" (".html"  
suffix)
Feb 02 00:12:49 symfony [info] {sfRouting} connect "/logout" (".html"  
suffix)
...
Feb 02 00:12:49 symfony [info] {sfContext} initialization
Feb 02 00:12:49 symfony [info] {sfController} initialization
Feb 02 00:12:49 symfony [info] {sfRouting} match route [slUserAuthLogin]  
"/login"
Feb 02 00:12:49 symfony [info] {sfRequest} request parameters array  
('module' => 'slUserAuth',  'action' => 'login',)
Feb 02 00:12:49 symfony [info] {sfController} dispatch request


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.

logs now for domain.de/login.html:
--
Feb 02 00:50:43 symfony [info] {sfContext} initialization
Feb 02 00:50:43 symfony [info] {sfController} initialization
Feb 02 00:50:43 symfony [info] {sfRouting} match route  
[default_index]"/:module"
Feb 02 00:50:43 symfony [info] {sfRequest} request parameters array  
('module' => 'login',  'action' => 'index',)
Feb 02 00:50:43 symfony [info] {sfRouting} connect "/message" (".html"  
suffix)
Feb 02 00:50:43 symfony [info] {sfRouting} connect "/notImplementedYet"  
(".html" suffix)
Feb 02 00:50:43 symfony [info] {sfRouting} connect "/login" (".html"  
suffix)
Feb 02 00:50:43 symfony [info] {sfRouting} connect "/logout" (".html"  
suffix)
...
Feb 02 00:50:44 symfony [info] {sfController} dispatch request
Feb 02 00:50:44 symfony [info] {sfController} action "login/index" does
not exist


I can't find the place where something goes the wrong way. None of my
prepended plugin routes are found/connected anymore. Here is a set of
route defs
in my code:

$r = sfRouting::getInstance();

# slUserAuth
if(in_array('slUserAuth', sfConfig::get('sf_enabled_modules'))) {
$r->prependRoute('slUserAuthLogin', '/login', array('module' =>  
'slUserAuth', 'action' => 'login'));
$r->prependRoute('slUserAuthLogout', '/logout', array('module' =>  
'slUserAuth', 'action' => 'logout'));
$r->prependRoute('slUserAuthPassword', '/password', array('module' =>  
'slUserAuth', 'action' => 'password'));
$r->prependRoute('slUserAuthRegister', '/register', array('module' =>  
'slUserAuth', 'action' => 'register'));
$r->prependRoute('slUserAuthRejoin', '/rejoin', array('module' =>  
'slUserAuth', 'action' => 'rejoin'));
}


Does anybody have a hint or experienced a similar problem?

Thanks!

jp



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---



[symfony-users] Routing Problem

2007-08-31 Thread Yeray Rodriguez

Hi, I'm using Symfony 1.0.6 and i have a problem con routing

if i define this rule:

example:
  url:  /:mode/:category1
  param: { module: categories, action: show, mode: basic, category1:
1 }
  requirements: { mode: ^(basic|premium), category1: \d+ }

with this url: /premium/2

i get next:

$this->getRequestParameter("mode")  -> premium
$this->getRequestParameter("category1") -> premium (incorrect)

Debugging sfRouting (parse method)  i've found that :

if (preg_match($regexp, $url, $r)) 

$regexp = #^(?:\/((basic|premium)))?(?:\/(\d+))?$#
$url = /premium/2/
$r=Array ( [0] => /premium/2 [1] => ofertas [2] => ofertas [3] => 2 )

maybe regexp is not well defined?? any idea? Thanks.


--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---