We are attempting to make our Umbraco installation public today. However, when our Information Systems department applied host bindings to our Umbraco development area (to make the main URL path lead to the new website), the "Content" UI in Umbraco would not open pages below the root.
When a page below the root is selected (e.g., "/college" or "/college/finances") we get an error along the lines of: "Item 1472 has already been added."
When these host bindings were removed from the Umbraco server, I could again edit content in the "Content" UI.
We are running on IIS7, and Umbraco 4.7.0.
Has anyone come across this before? How can we make Umbraco receive the host bindings?
The Umbraco installation is in a subdomain (sub.domain.com), and we are trying to get the main domain (domain.com) to lead to the Umbraco site. When this path is applied to the Umbraco site, we get the error described above, and the "Content" UI becomes useless.
Rather sheepishly, I was able to fix the problem by declaring Host Names at the root level of the site. I hadn't looked into Host Names before, and hadn't realized how important they can be... The site is working well now.
Content UI fails when host bindings are applied to the Umbraco server
We are attempting to make our Umbraco installation public today. However, when our Information Systems department applied host bindings to our Umbraco development area (to make the main URL path lead to the new website), the "Content" UI in Umbraco would not open pages below the root.
When a page below the root is selected (e.g., "/college" or "/college/finances") we get an error along the lines of: "Item 1472 has already been added."
When these host bindings were removed from the Umbraco server, I could again edit content in the "Content" UI.
We are running on IIS7, and Umbraco 4.7.0.
Has anyone come across this before? How can we make Umbraco receive the host bindings?
Thanks,
Luke
I should clarify:
The Umbraco installation is in a subdomain (sub.domain.com), and we are trying to get the main domain (domain.com) to lead to the Umbraco site. When this path is applied to the Umbraco site, we get the error described above, and the "Content" UI becomes useless.
Hi Luke,
Can you paste the full exception?
I have seen a similar error but it's usually fixed by just recycling the app pool, have you tried that?
Also are you adding these bindings in IIS or Umbraco? IIS bindings shouldn't have any effect on an error like that
-Tom
Thanks for the response!
Rather sheepishly, I was able to fix the problem by declaring Host Names at the root level of the site. I hadn't looked into Host Names before, and hadn't realized how important they can be... The site is working well now.
is working on a reply...