I have a site who needs to be pointed to: inetpub\wwwroot\cakephp\app\webroot\
If I point the "Default Web Site" to that directoy, my web application works perfectly.
Now, as I want to add more sites to that same computer, I am pointing the "Default Web Site" to inetpub\wwwroot\ and the concrete folder for my web application (cakephp) to the previous path inetpub\wwwroot\cakephp\app\webroot\.
When I do this I have noticed it doesn't even execute the index.php file located inside inetpub\wwwroot\cakephp\app\webroot\ contrary as it should. It only does it when accessing directly to the root of the site.
To clarify it:
www.myweb.com/cakephp/ executes inetpub\wwwroot\cakephp\app\webroot\index.php
www.myweb.com/cakephp/actionName/ does NOT executes inetpub\wwwroot\cakephp\app\webroot\index.php
Why is this happening? Why it doesn't recognize the given path when I add any parameter to the URL?
It tries to list the folder content instead...
Thanks.
Have you tried this:
http://www.myweb.com/cakephp/index.php/Controllername/
For example:
http://www.myweb.com/cakephp/index.php/pages/home/
if that is working, then 'URL rewriting' isn't working.
URL Rewriting doesn't work out-of-the-box on IIS, but can be configured with the instructions in the documentation:
http://book.cakephp.org/2.0/en/installation/advanced-installation.html#url-rewrites-on-iis7-windows-hosts
However, your setup may need to be slightly different than the documentation because you've installed your website in a subdirectory
Related
I built a tiny application for a client using cakephp on my local machine running xampp over windows [in a folder "cake" inside htdocs]. Today i created a new folder on my client's live server named "cake" and uploaded the contents of "cake" folder on local machine to "cake" folder on live server for testing. I fired up my app using url: http://kianaretail.com/cake and I got an internal server error 500.
I went through several people suggesting addition of RewriteBase to .htaccess files in root, app and webroot folders pointing to the location. In my case it was "RewriteBase /cake" in root, "RewriteBase /cake/app" in app and "RewriteBase /cake/app/webroot" in webroot. But it did not work still. The problem still persists.
The same application runs fine on my local machine. Just messes up on live server.
Please help.
if the application runs fine in the local machine but has problems in the live server, you could also try to investigate which configurations are different between the servers to try to get some hints as to what might be causing the problem.
I would guess that the live server doesn't have mod_rewrite enabled, and so a .htaccess with RewriteBase could be causing the trouble. You can try to comment the .htaccess and see if it runs fine in the server and then re-enable the configurations one at a time to try to figure things out.
Also, as Dave mentioned, checking the error logs would probably give you more information as well.
Hope that helps.
I have followed this article to configure CakePHP over II6:
http://bakery.cakephp.org/articles/jamesmking/2008/04/12/cakephp-on-iis6-with-fastcgi-sql-server-2005-and-isapi_rewrite
But i want to change the "Local Path" from "C:\Inetpub\wwwroot\CakePHP\app\webroot" to "C:\Inetpub\wwwroot\" in order to be able to execute different web applications and not only the CakePHP one.
I have tried it changing the "local path" on the IIS manager but i doesn't work. I guess it should be something related with the ISAPI Rewrite and its conditions.
Do you know how could I make the needed changes in order to make it work?
Regards.
Move the .htaccess file in the root of the site's root folder.
I'm running into this problem and its driving me crazy.
Also, we are not allowed to update the version of IIS.
The content on the server (asmx files holding WCF webmethods called via SOAP) exists and I can freely browse in inetmgr to the virtual directory that contains this data. The files all exist all on the file system and the virtual directories all point to the correct spot and have the correct ACLS, but when I go to their URLs all I get is a 404 message.
I have reset IIS, I have rebooted the server, and I have done everything I can think of.
The IIS logs simple return "404 - -" as the entire line contents, with no other data in the line.
The event logs show nothing, and ASPNET is not dying or anything like that.
With no event logs, and minimal logs in IIS , I have no idea what to do and was hoping that others had run into this before.
In IIS logs there should some codes along side the 404 error which will help find the issue.
Check IIS has the correct version of .Net installed using aspnet_regiis command line tool. Also check that ASMX extensions are mapped to the .Net ISAPI filter as they are with ASPX pages.
I have a website that used to have .dsp file extensions for all pages. There are alot of other sites referencing mine that reference the pages like that, but my pages are all actually .aspx pages. In IIS5, I was able to configure this to work.
My problem is I've recently switched from IIS5 to IIS7, and I have no idea how to map these requests (.dsp) to the real file (.aspx) without the server telling me the file doesn't exist.
In the IIS go to Handler Mappings under you website/application/vdir and add a new managed handler.
Tell you extension (.dsp) and the Executable (in this case the same of asp.net which is %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll for ASP.NET 2.0 64 bits).
I hosted one DotNetNUke Application to my production server, and locally it works perfectly. But, when browsing it redirects to the error page.
How do I set the default.aspx as my application default page? I am getting the error as below:
DotNetNuke Error
--------------------------------------------------------------------------------
Windows Vista
Return to Site
Can anyone can help me, please? Will be appreciated.
UPDATE:
Hi, I changed the Path in the PortalAlias table to the server url and default.aspx as the starting page, but it displays the error.aspx as default page.
Please help me resolve this problem..
So, the application works perfectly locally, but not when you put it on the server. Is that correct?
Make sure that your portal alias is valid. If the site is hosted at
http://www.mysite.com
then www.mysite.com needs to be listed in the PortalAlias table
If you open that table in SQL Mgmt Studio, you'll probably see an entry attaching the portal to your local DotNetNuke folder (ie. localhost). Just add a new entry that points to the same PortalID, but with the correct URL for your production server.
Assuming your DNN installation is at "mysite.com", if you navigate to
http://www.mysite.com/default.aspx
do you still get the error page? If so is any error listed?
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have to correct machine key and connection strings. This is my last resort something is really strange procedure.