I built and deployed an Umbraco 4.0.2.1 site for a client
back in May.Recently the client has
started reporting that they have problems publishing content from their
network.They reported that after
editing content and publishing it, that the change is not appearing on the respective
front end page.Furthermore, they
reported that the CMS editor does display the recent change and also that
clicking one of the preview links from the content node property tab also displays
the change.
I have met with them to review the issue and have seen firsthand
the problem that the client is experiencing.The strange thing is that from my office network and other client’s
networks as well as my home, the project manager’s home and even our network
manager’s home, we cannot duplicate the problem.Publishing from anywhere outside the client’s
network is successful.
At this point I can only assume that because publishing
works outside the client’s network, that there must be an issue in the client’s
firewall or specific software running on their PCs.The site is hosted by the company I work for
and we have never had a problem like this before with any of our Umbraco sites.Does anyone have any suggestions concerning
what could be causing this problem within my client’s network?I’m open to any suggestions and advise.
I have the same problem in an environment that I don't have any control over. The web filtering server at this client's site is caching pages, even dynamic ones. And it doesn't respond to no-cache requests, it will just send the cached version back again.
The only thing you can do is advise them to set exceptions in their web filtering / firewall server. Luckily, this is definitely not an Umbraco problem. :-)
It turns out that the issue was not with the client's web filtering server, but the URL that the client was using. The web site was originally launched with a temporary URL that was later replaced with the client’s permanent domain. I failed to remove the temporary URL from the managed hostnames and then proceeded to set up a test site on the same server with the same managed hostname. The client was continuing to use to temporary URL to access the Umbraco content manager, so they were seeing the actual production site content, but when they published changes, they were published to the test site. I simply removed the temporary hostname from the production site and asked the client to access the Umbraco content admin using the permanent production URL.
We are having exactly the same problem. And it is driving us nuts !!!! I've got some tips but no absolute tip or explanation.
I was showing the new site to the client ( me in my office, him in his office ). I was accessing the site at the same time as the client. (we both logged in with the same ID (not sure if this is important)). I made some changes but I could not see them on the site ? ( rather embarassing ).
So I said I would look at them by myself ... the client hung up and I continued to scratch my head.
After a bit of googling I found that you can edit one of the config files to stop umbraco caching. config/umbracoSettings.config <XmlCacheEnabled>False</XmlCacheEnabled> <ContinouslyUpdateXmlDiskCache>False</ContinouslyUpdateXmlDiskCache> this is the thread I got it from http://our.umbraco.org/forum/getting-started/installing-umbraco/5267-Content-Caching-Issue
So when I edited umbracoSettings.config the site showed the changes I made ... but took about 30 seconds to save a tiny change. This however is the most bizarre bit, I re-edited the config file, the site immediately became quicker, but I was shown some pages from when I had first started the exercise (that was about 2 hours ago).
But here is the equal top bizarre bit ....after another 40 minutes knocking my head agains the desk, it suddenly starts working fine ?!!?! I mean, it is fast and it shows my latest changes.
So the next day, I test the website a couple of times and it is quick and I can see changes that I make. So I feel confident when I ring the client. But guess what ?!! When he does the updates, he can't see the updates ? I can do updates fine and see them, I can even see changes he makes .... but he can't see his own changes.
My current line of enquiry is to ask the network suppervisor to stop network caching specifically for this website ( make an exception ).
Problem publishing from within a specific network
Hello Everyone,
I built and deployed an Umbraco 4.0.2.1 site for a client back in May. Recently the client has started reporting that they have problems publishing content from their network. They reported that after editing content and publishing it, that the change is not appearing on the respective front end page. Furthermore, they reported that the CMS editor does display the recent change and also that clicking one of the preview links from the content node property tab also displays the change.
I have met with them to review the issue and have seen firsthand the problem that the client is experiencing. The strange thing is that from my office network and other client’s networks as well as my home, the project manager’s home and even our network manager’s home, we cannot duplicate the problem. Publishing from anywhere outside the client’s network is successful.
At this point I can only assume that because publishing works outside the client’s network, that there must be an issue in the client’s firewall or specific software running on their PCs. The site is hosted by the company I work for and we have never had a problem like this before with any of our Umbraco sites. Does anyone have any suggestions concerning what could be causing this problem within my client’s network? I’m open to any suggestions and advise.
Thanks in advance.
I have the same problem in an environment that I don't have any control over. The web filtering server at this client's site is caching pages, even dynamic ones. And it doesn't respond to no-cache requests, it will just send the cached version back again.
The only thing you can do is advise them to set exceptions in their web filtering / firewall server. Luckily, this is definitely not an Umbraco problem. :-)
Thanks Sebastiaan,
It turns out that the issue was not with the client's web filtering server, but the URL that the client was using. The web site was originally launched with a temporary URL that was later replaced with the client’s permanent domain. I failed to remove the temporary URL from the managed hostnames and then proceeded to set up a test site on the same server with the same managed hostname. The client was continuing to use to temporary URL to access the Umbraco content manager, so they were seeing the actual production site content, but when they published changes, they were published to the test site. I simply removed the temporary hostname from the production site and asked the client to access the Umbraco content admin using the permanent production URL.
Thanks for your help.
We are having exactly the same problem. And it is driving us nuts !!!! I've got some tips but no absolute tip or explanation.
I was showing the new site to the client ( me in my office, him in his office ).
I was accessing the site at the same time as the client. (we both logged in with the same ID (not sure if this is important)).
I made some changes but I could not see them on the site ? ( rather embarassing ).
So I said I would look at them by myself ... the client hung up and I continued to scratch my head.
After a bit of googling I found that you can edit one of the config files to stop umbraco caching.
config/umbracoSettings.config
<XmlCacheEnabled>False</XmlCacheEnabled>
<ContinouslyUpdateXmlDiskCache>False</ContinouslyUpdateXmlDiskCache>
this is the thread I got it from http://our.umbraco.org/forum/getting-started/installing-umbraco/5267-Content-Caching-Issue
So when I edited umbracoSettings.config the site showed the changes I made ... but took about 30 seconds to save a tiny change. This however is the most bizarre bit, I re-edited the config file, the site immediately became quicker, but I was shown some pages from when I had first started the exercise (that was about 2 hours ago).
But here is the equal top bizarre bit ....after another 40 minutes knocking my head agains the desk, it suddenly starts working fine ?!!?! I mean, it is fast and it shows my latest changes.
So the next day, I test the website a couple of times and it is quick and I can see changes that I make. So I feel confident when I ring the client. But guess what ?!! When he does the updates, he can't see the updates ? I can do updates fine and see them, I can even see changes he makes .... but he can't see his own changes.
My current line of enquiry is to ask the network suppervisor to stop network caching specifically for this website ( make an exception ).
Any thoughts / input / sympathy much appreciated.
Hugh
is working on a reply...