We recently started using Umbraco for a site we have and everything seemed to be working fine.
However we've come across a slight issue.
The site was developed locally and in a template we have a simple text property that's a URL, so for testing it was set to say http://www.example.local/.
To deploy it to production we published the site and simple backed up/restored the database onto the live server.
We then changed that URL to say http://www.example.co.uk/ and republished, bish bash bosh all is well...except at least once a day it reverts to the .local version. We have to constantly republish the updated item to restore it, and I'd love to know why, as I can't find where it's getting .local from anymore.
I've tried clearing older versions out in SQL, deleting the temp folder in App_Data etc to no avail.
Anybody got any suggestions? I'm really stumped now on what's causing this.
Have you changed the hostname for the homepage node by adding "Culture and hostname" when right clicking on the node and then selecting this item from the context menu?
Make sure that the hostname is unique on the live-site .
Hope this helps - Sorry if I misunderstand and you already have done this.
Yes I did have the .local bound in hostname, I have removed that however it still appears to happen.
I'll double check as I may not have republished after I removed it just to make sure.
I'm unsure why it would affect the property value though, the domain in the value isn't even relevant to the Umbraco site it's a sub-domain (should have been more accurate in the initial post), I just dump the value verbatim into a Razor page.
For example, site is on www.example.com on live, the property value is:
So why would live revert to the development value? Even if I republish it with the correct value, given 24 hours (I'm guessing, I only do it once a day) it will go back to the previous version.
Property reverts to old value
We recently started using Umbraco for a site we have and everything seemed to be working fine.
However we've come across a slight issue.
The site was developed locally and in a template we have a simple text property that's a URL, so for testing it was set to say http://www.example.local/.
To deploy it to production we published the site and simple backed up/restored the database onto the live server.
We then changed that URL to say http://www.example.co.uk/ and republished, bish bash bosh all is well...except at least once a day it reverts to the .local version. We have to constantly republish the updated item to restore it, and I'd love to know why, as I can't find where it's getting .local from anymore.
I've tried clearing older versions out in SQL, deleting the temp folder in App_Data etc to no avail.
Anybody got any suggestions? I'm really stumped now on what's causing this.
Hi Lloyd and welcome to our :)
Have you changed the hostname for the homepage node by adding "Culture and hostname" when right clicking on the node and then selecting this item from the context menu?
Make sure that the hostname is unique on the live-site .
Hope this helps - Sorry if I misunderstand and you already have done this.
Cheers, Jan
Hi Jan,
Yes I did have the .local bound in hostname, I have removed that however it still appears to happen.
I'll double check as I may not have republished after I removed it just to make sure.
I'm unsure why it would affect the property value though, the domain in the value isn't even relevant to the Umbraco site it's a sub-domain (should have been more accurate in the initial post), I just dump the value verbatim into a Razor page.
For example, site is on www.example.com on live, the property value is:
http://downloads.example.com/something/something/something.exe
On development it's:
http://downloads.example.local/something/something/something.exe
So why would live revert to the development value? Even if I republish it with the correct value, given 24 hours (I'm guessing, I only do it once a day) it will go back to the previous version.
Turns out this is because Umbraco.config was read-only so the content XML could not be copied in on publish.
Allowing the IIS user to write to this file fixed the issue.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion