Home > Cannot Make > Cannot Make A Cache Safe Url For 1033/styles/portal.css

Cannot Make A Cache Safe Url For 1033/styles/portal.css

Copyright © 2016 EnjoySharePoint.com SharePoint Hosting About Us Contact Us Advertise skip to main | skip to sidebar Sohel's Blog Pages Home About Me Tuesday, November 9, 2010 SharePoint 2010 Error: How do fonts work in LaTeX? Signup Follow @EnjoySharePoint Win prizes like Hard Disk, Pen drives, T-Shirts etc. Not the answer you're looking for? Check This Out

It worked like magic…. Watch a video on how to optimize your support resource searches and check out more tips on the blogs. Unfortunately, it is still not working on my server. And OK, OK, I cheated a little bit with the article title - in fact the problem is not unique to SharePoint's "layouts" folder (or even IIS), and when I say http://stackoverflow.com/questions/18625278/cannot-make-a-cache-safe-url-for-14-1033-styles-themable-corev4-css-file-not

Users do not see the Javascript/CSS changes until they do a hard refresh (CTRL + F5). Toggle navigation Questions and Answers Azure development Sql Azure C# Sharepoint WebPart CSS applied in Debug but not when deployed Category: sharepoint 2010 programming Question GMSteele on Thu, 27 Sep 2012 See other lastest posts sharepoint 2010 customization Dataview of multiple InfoPath forms Infopath repeating table edit data to sharepoint list...

Thanks again to Hiren Patel! Kind regards, Stanimir the Telerik team Instantly find answers to your questions on the new Telerik Support Portal. This scenario typically results in the oft-heard question "Hmm, what happens if you do a CTRL + F5?". To increase scalability I have seen sites where expiration was set in the region of days which severely affected the ability to upgrade the application.Changing IIS caching directives in the run

I have not changed anything in the config.xml file or the tools file. What would be ideal is if all this could take care of itself on every release! It works for me! What I thought was a firm-standard font is not.

Anyway, we can check whether the file is existing at first. ScriptLink control or plain script tag) BLOB caching does not make any change Sandboxed or farm solution does not make any change Note - tested on SharePoint 2010 RTM (old) and It WILL, however, if you store them in a library and do not recycle IIS every time the file changes - something that should happen automatically for a WSP deployment to Would using blob cache and explicitly setting a max-age timeout get around this issue?I mean say you only deployed at night and your max-age was set to a day.

Here is the relevant code: //Literal css = new Literal(); ////This URL needs to be absolute when it goes to production //css.Text = ""; //this.Controls.Add(css); CssRegistration cssReg Thanks!GMSteele on Fri, 28 Sep 2012 16:06:50 OK, I found it. If not presented there you can put there and check.- Sometimes you will get the error as "Cannot make a cache safe URL for "1033/sp.debug.js", file not found. G.

How do I handle this? his comment is here What physical evidence exists that shows motor proteins "walking" within a cell? Sean Hudson 14 posts Member since: Sep 2009 Posted 18 Dec 2009 Link to this post Stanimir, Here is the code you have requested. Restored was successful.

Watch a video on how to optimize your support resource searches and check out more tips on the blogs. I did actually go digging in Reflector to find the source of this behavior, but didn't find it. In production, it's certainly not fine for the rest of the organisation - strangely enough, asking 30,000 information workers to do a CTRL + F5 does NOT go down well in this contact form Can any one help ?

I haven't spent too much time on this, but in our project we do use a solution for CSS files at least. For JavaScript files, it doesn't matter how the file is added to the page (e.g. Making sure the client browser is a) IE 8 or higher; and b) has access to the fonts you are using is the other half.

RepliesGeetanjali Arora on Sat, 29 Sep 2012 19:43:10 See if the following link helps http://bernado-nguyen-hoan.com/2010/12/13/cannot-make-a-cache-safe-url-for-1033sp-js-file-not-found/Bjoern H Rapp on Sat, 29 Sep 2012 20:13:40 Hi Did you use mapped folders to LAYOUTS

Sean Hudson 14 posts Member since: Sep 2009 Posted 17 Dec 2009 Link to this post Hi Stanimir, Yes I have upgraded the MOSS site as the articles suggest. Please verify that the file exists under the layouts directory. " For this you can copy the sp.debug.js file and put it inside C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033.- Another solution In many cases though, this means remembering to do a find/replace in Visual Studio on all the locations which have links to these files before every deployment. Then I download the language pack from MSND and refreshed the browser.

This makes sense in fact, because what matters are the headers when the file was initially served (however long ago this was).Cheers,Chris. 4 December 2011 at 16:06 Chris O'Brien said... @Mel,Nice. Then when your users came in next day their browser cache would have expired?Just thinking of an OOTB way of getting around the issue. 1 December 2011 at 13:21 Mel Lota Thanks, Sean page-capture.png Sean Hudson 14 posts Member since: Sep 2009 Posted 18 Dec 2009 Link to this post Stanimir, I removed the user controls that were causing the javascript errors navigate here Well, here's where we hit the snag - unfortunately Microsoft.SharePoint.WebControls.ScriptLink (the equivalent control for JavaScript links) is sealed, so we can't use the same approach.

As far as I can tell, if you do this to the top level of your site collection there is no way to fix your site without using some custom code In addition you can check if there is some problem with the request for the editor's resources by using debugging program such as fiddler (review the provided screen shot) . Thank you. When I run the solution in debug or releasemode in VS2010, the styles are applied, but if I deploy a release to the server, it is not applied.

Sean Hudson 14 posts Member since: Sep 2009 Posted 18 Dec 2009 Link to this post Stanimir Yes there are javascript errors, I will try removing the references to these script I had to take backup from my client's production site to make some analysis in my local server. Then run stsadm -o copyappbincontent to update existing web application with new resources.