In what way is it not working? Are you getting a 404? Are your images/stylesheets not being found? Is something else happening?

I confess that I am not expert when it comes to the twisty aspects of RewriteRules. In fact, that’s why I usually avoid some of these solutions and use my own solution, pushing all the ZF content into a protected _zf folder. Then I can use the “standard .htaccess at the root and only have to protect the _zf folder and change an include path.

Maybe try posting the question at either zfforums.com or stackoverflow.com. Both those places are populated with people much smarter than me.

I put this code on my folder /root/.htaccess and /root/public/.htaccess

referring on : http://www.alberton.info/zend_framework_mod_rewrite_shared_hosting.html

RewriteEngine On
RewriteRule ^\.htaccess$ - [F]
RewriteCond %{REQUEST_URI} =”/”
RewriteRule ^.*$ /public/index.php [NC,L]
RewriteCond %{REQUEST_URI} !^/public/.*$
RewriteRule ^(.*)$ /public/$1
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^.*$ - [NC,L]
RewriteRule ^public/.*$ /public/index.php [NC,L]

but my page was not running well, can you help me ?

bigfull thank’s

Nice thought.

I always try to change up background colors or skins in different environments. A simple example if you have a CMS pointing to a dev database vs. a prod database…you don’t want to make a test entry on prod by mistake.

But even in the absence of symlinking, your new info about baseUrl() really seals the deal. I’ll have to check that out.

Thanks, man!

It would be a problem for apps at a lower level url as you say, as Zend MVC will think the base url is still /, however the base url can be set manually rather than having to change the routes.

As for the conclusion, I agree :), although some shared hosting you can just cheakily delete the web root folder and symlink the app’s public folder to its previous location.

But there is a sticky point to this approach. Sure, the user will only see his requested url (say, /mypage) since the rewrite rule only uses the [L] flag and not the [R] flag. But the ZF app itself will see the url that Apache is serving, which is /public/mypage. That means that any defined routes would need to have the ‘public’ prefix in order to be matched. Isn’t that right?

We could certainly handle those, so it becomes a question of which adjustment (file paths or routes) you want to handle.

In the end, the conclusion I come to is: shared hosting sucks.
Thanks and cheers!

RewriteEngine on
RewriteRule ^.* /public/$0 [L]

This will give the effect of moving the web root into public/. e.g. requests to http://domain.com/application/ will actually be served from /public/application/, meaning even those directories are unaccessible.