[size="5"]SOLVED:[/size]
[i][font=“Times New Roman”]the app didn’t do anything wrong, I did.
I didn’t notice that urlmanager injected the /active/ diectory in the generated paths.
Working now on filtering it out.[/font][/i]
Hey!
Long time no see. So I have an application with an api module that works flawlessly on the production machines (virtual host based) but whose path formated urls resolve to the home page when deployed on the production machine inside a subfolder.
[size="5"]Development setup:[/size]
framework in:
webroot/framework-yii-git/1.1.12/yii/framework/yii.php
app in:
webroot/vhostroot/(protected/etc..)
api request:
http://vhost.c/api/controller/action
resolves to the correct route
[size="5"]Deployment setup:[/size]
farmework in:
webroot/theapp/framework-yii-git/1.1.12/yii/framework/yii.php
app in:
webroot/theapp/v0.1/(protected/etc...)
link
webroot/theapp/active -> webroot/theapp/v0.1
htaccess in webroot/theapp (is a basic forwarding script to the active application folder)
RewriteEngine on
RewriteRule ^$ active/ [L]
RewriteRule (.*) active/$1 [L]
htaccess in active (aka v0.1 directory)
is the base yii .htaccess file
in the deployment the basic urls
http://domain.net/theapp/<controller>/<action>
work as expected, the request is forwarded to to the ‘active’ directory which links to
the active application. So basic functionality is there.
The problem lies with the api module since
http://domain.net/theapp/api/<controller>/<action>
doesn’t resolve to the expected module>controller>action but just defaults to the default ‘home’ page…
Any ideas?