I'm having issues publishing on Umbraco sites.
It would seem to me as if its a caching issue but I can't get to the root of the problem.
I have been able to recreate the issue but it does seem to be intermittent.
Example:
Create new page - populate data
Save & Publish page
View page in same browser, working fine and content correct.
View page in alternative browser and the page cannot be found.
I have:
republished the entire site
deleted the umbraco.config files
re-indexed the site
restarted the App Pool
None of these work.. But come back the next day the updates are working.
Umbraco 7, Hosted on Azure
Any ideas?
Azure Scaling was causing this issue.
Yes, disabling auto scaling in Azure 'DefaultServerFarm' was my solution too - but more specifically: after modifying that setting I made sure to set the number of instances to 1 ! Leaving it at 2 would result in the same issue.
Related
Recently none of the web content in the global site is showing up when selecting the web content in a web content display. Nor does the search find the particular web content I'm trying to use.
I assume it is an index issue, but I've reindexed everything I could think of that would be related - everything journal article related as well as document lib related - but nothing has worked. Restarting Liferay hasn't helped, nor has re-publishing the web content. Permissions are unchanged.
Any ideas? Can anyone tell me which indexing option should work?
Liferay 7 GA7
Thanks.
I did a restoration of the complete site collection using the stsadm restore into a new farm. The site as it is work good but I have one wiered issue that whenever I visit the root site I get the following error.
If I visit the sub sites directly this is what I see in the top navigation
Here is what I have found in troubleshooting it
If I do a app pool recycle or IISReset the issue is gone and site works perfect
The error comes back after few minutes of site usage
The different steps that I took after looking at few other places are
Deactivate and reactivate the SharePoint Publishing Infrastructure
Change the master page
Reset the blob cache, output cache and object cache (I doubt this was the fix, cause cache is not enabled)
Clear the sharepoint configuration cache as per this site
Please let me know your thoughts on how I can fix this and following in the farm details
Server - Windows 2003 x86
SharePoint - MOSS 2007 with build number 12.0.0.6656
Thanks
Deepak
Deactivating and reactivating the publishing site feature in the Site Collection and Web fixed it.
I created a SharePoint web-application, and a new site collection under it. I made it SSL Enabled. (Now I could view the site and modify/add content). I started modifying the landing page of the sites I created. Basically I created a copy of seattle.master and applied this new css file to my pages. Now suddenly, I see a blank page with no error information, on navigating to my site collection. I tried the LoopBack fix to no avail. I feel this is an authentication issue, but I am unsure where to go from here. Moreover, SharePoint Designer refuses to connect to the site as well (I am getting- SharePoint Foundation not installed on this server error, which is not the case). I have Sharepoint Server 2013, and the web server is on Win Server 2008 R2. Any ideas?
I had the same issue with my sites on all site collections under a web application.
I tested the other sites in the other site collection and they were coming up ok.
I checked the content database, took it off line and reset it, same issue. Checked log files, no errors in the log files, reset IIS and app pools same issue, checked permissions on the webapp in iis, same issue.
Solution.
Replaced the webconfig from yesterdays backup and it worked,
a solution that was deployed to the web application and activated on the site collection must added some entries and corrupted the file
I am publishing the site using VS 2012 Publish website option. But the site does not get updated. I have to restart the website from manage.windowsazure.com every time after publishing.
I have been running the website on both free and shared mode. Same situation in both mode.
Any suggestion how to update the website automatically after publish?
Mmm. If your change regards CSS and JavaScript, try browse your website by using Ctrl+F5. If it seems totally not being updated, you might need to check the deployment page of your website on azure portal to see if it's get updated or not, or something wrong.
HTH
While setting up a test environment I was attempting to set up many different types of sites for testing various things when I ran into a strange bug in SharePoint.
I was creating a subsite under a blank site template and saw the option for "News Site" so I selected it and got an error saying that the Publishing Feature was not enabled at the site collection level.
Fine. So, I went and activated it and then attempted to create the site again and I got the error:
The Web site address "/mpsite/news" is already in use
Ok, so the site must have been created anyway so I try to visit the URL and get:
The webpage cannot be found
Fine. So, obviously it errored in the middle of the site creation so I'll just delete it via STSADM. Wrong:
There is no top-level Web site named "http://server/mpsite/news/".
So, the site is listed in the sites and workspaces list, but doesn't really exist and can't actually be deleted.
How do I get rid of it from the Sites and Workspaces listing?
You've run into one of the lovely undocumented "features" of SharePoint - site templates get applied after the site gets created in a seperate, descrete step. This means that potentially, a site can "exist" (as far as the content database is concerned) without template, which leaves you with a site you can't browse to, but still sorta "exists" in SharePoint purgatory (I've actually written a couple of hacks that involve relying on this "feature").
It looks to me like you may have run into one such situation - when you went to go create your site, I'm guessing that you got the error before the template was applied to your news site.
The way I've fixed similar problems in the past has been to use SharePoint Designer to delete the sites - since it looks straight into the content database for what does and doesn't exist, it might do the trick for deleting your rouge news site.
Hope this helps!
Have you tried http://server/mpsite/news/_layouts/deleteweb.aspx ?
Or maybe the "Content and structure" (http://server/mpsite/_layouts/sitemanager.aspx) link from site actions?
I know this is old, but it may help somebody. In SP2013 running the Remove-SPWeb Powershell command with the url of the corrupted web worked perfectly for me.