We have umbraco installed in a custom directory, and have been using it successfully for a while. We are running umbraco 4.9.1 on asp.net 4.0, IIS 7.5
We now are tryign to install uCommerce 3 on top of that. With moving some files after the initial install, and some configuration changes, we have uCommerce running mostly fine. However, while testing with the Razor store backend, we ran into a '404' error trying to change an order status from 'new' to 'completed'.
Details:
The page brought up in the 'Change Order Status' dialog his housed here: "http://localhost:90/cmsdir/ucommerce/orders/changeorderstatus.aspx?id=169&rndo=50.5". Note the 'cmsdir', which is our custom directory and the value in web.cofig for key="umbracoPath".
When we hit 'Update Status', the order status is updated in the database, but we get the 404 error trying to show the next page: "http://localhost:90/cmsdir/cmsdir/ucommerce/orders/editorder.aspx". Note that it has two 'cmsdir' values added to the path.
'editorder.aspx' does exist on the server at "http://localhost:90/cmsdir/ucommerce/orders/editorder.aspx".
Is there a configuration or markup change that needs to be made to correct the routing? Or is the path to 'editorder.aspx' built in code?
I actually had it set it as "/cmsdir" because the '~' caused some RSS feeds we showed in the dashboard to fail.
However, i just tried modifying it to "~/cmsdir", and changing the order status still fails with the same error.
The Related Products dialog actually fails with a similar '404' error when attempting to save a 'related product' selection, or delete a related product.
The resource cannot be found. Description:HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Turns out that it's the Umbraco JavaScript API responsible for changing URL in the content frame that's deciding to prepend the CMSPath. I still have dig into it some more to figure out why it's doing that.
404 "The resource cannot be found" error when changing order status, editorder.aspx
We have umbraco installed in a custom directory, and have been using it successfully for a while. We are running umbraco 4.9.1 on asp.net 4.0, IIS 7.5
We now are tryign to install uCommerce 3 on top of that. With moving some files after the initial install, and some configuration changes, we have uCommerce running mostly fine. However, while testing with the Razor store backend, we ran into a '404' error trying to change an order status from 'new' to 'completed'.
Details:
The page brought up in the 'Change Order Status' dialog his housed here: "http://localhost:90/cmsdir/ucommerce/orders/changeorderstatus.aspx?id=169&rndo=50.5". Note the 'cmsdir', which is our custom directory and the value in web.cofig for key="umbracoPath".
When we hit 'Update Status', the order status is updated in the database, but we get the 404 error trying to show the next page: "http://localhost:90/cmsdir/cmsdir/ucommerce/orders/editorder.aspx". Note that it has two 'cmsdir' values added to the path.![]()
'editorder.aspx' does exist on the server at "http://localhost:90/cmsdir/ucommerce/orders/editorder.aspx".
Is there a configuration or markup change that needs to be made to correct the routing? Or is the path to 'editorder.aspx' built in code?
-e
Interesting.
What's your UmbracoPath set up to in web.config? "cmspath" or "~/cmspath"?
Does the "Related Products"-dialog work as expected?
I actually had it set it as "/cmsdir" because the '~' caused some RSS feeds we showed in the dashboard to fail.
However, i just tried modifying it to "~/cmsdir", and changing the order status still fails with the same error.
The Related Products dialog actually fails with a similar '404' error when attempting to save a 'related product' selection, or delete a related product.
Turns out that it's the Umbraco JavaScript API responsible for changing URL in the content frame that's deciding to prepend the CMSPath. I still have dig into it some more to figure out why it's doing that.
is working on a reply...