-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't Work with nginx #1
Comments
Forgive me for not understanding, isn't the point to remove "index.php" when rewrites are on? What you are describing sounds like it is working right. |
Right, I'm saying URL rewrites themselves work - for the front-end. In the backend, whether your extension's enabled or not, I still see the index.php. |
I've thought about it and there cannot be a problem with your nginx configuration since it works on the front end. Even though you have almost certainly tried the following please make sure you have cleared the cache, recompiled if compilation is enabled, checked permissions for this extension's files so PHP may read them. I have some experience with nginx so will attempt to recreate the same problem you see. |
If it helps, here's my nginx configuration file for that domain. So the URL rewrites seem to work on the front end, just not the backend. |
I have been trying configurations on nginx and have not yet come up with a scenario where backend rewrites are handled differently to frontend. I realise there is one thing I did not ask you to check. Go to System > Configuration > Admin > Admin Base URL then change Allow URL rewrites to Enable. |
Yeah, it's set to Enable. However, for example, when I'm on that page, the URL I get is: So clearly the index.php is still there. I'm not sure if this is just a problem with my configuration or not... maybe you could try the nginx configuration I provided and see if that causes the same problem I'm getting - if so, it's probably a configuration problem in nginx and I'd love to know how to fix it. |
I used your configuration as the basis for a test server which worked perfectly first time. I saw basis because, understandably, there were some environmental differences. BTW, you should check your denied files are actually being blocked because this section looks badly written:
A
Similarly The reason the page you look at has the URL Try manually deleting If there was an accident during install that file might have been left out so it never got copied into place. Or perhaps it exists but doesn't have read permission. Or perhaps another extension conflicts with that file because it also tries to override |
OK, so the page loads fine if I remove the index.php, but all the links still have index.php. Are you saying I should disable compilation, then install the extension? I have the compiler enabled. |
Since you have the compiler enabled you should run the compilation process again. |
Yeah, I used the Magento Connect Manager to install the extension with the compiler enabled and it still doesn't work. |
This used to work great for me when I used Apache with Magento Enterprise Edition, but since switching our HTTP daemon to NginX, it no longer works. I have the nginx configuration set to do URL rewrites of everything else - if I set them to "yes" in the admin panel, there's no index.php in the storefront, if I turn it off, the index.php shows back up.
I'd be happy to share my nginx configuration if that helps.
The text was updated successfully, but these errors were encountered: