I have a HTML file, which I've uploaded as a web resource and linked to via an activity's form designer in an IFRAME. So far, so good.
Then, when I edited the source file locally and uploaded it (browse-save-publish, of course), I got no difference in the appearance on the screen. Here's the weird part. When I open the uploaded file in the editor, I can see the changes to my source code. On the RTF tab I can also see the change in colors of the background.
However, reloading the "create new"-form doesn't bring those changes to the client! I've tried restarting the window, restarting IE, clearing the cache. Nothing helps.
When I entered the very same page from a different client, I got to see the updated version. But after that, the subsequent changes are not updated either. It's like if IE thinks "oh, matey, ya wanna cache that for life, I see". Well, I don't. I'd like to see my edition in action pretty much directly and without creating a new account with a new client. :)
After a while, the update seems to go through and I get to see a new version but not in all browsers.
What is causing it?! How do I kill it?
(Win8/IE10/CRM11OL)
I have seen CRM do some weird IIS Caching. I'd assume this is a server side issue, but your using crm online, they won't let you run an IIS reset now will they? :) Have you tried running it on a new client in private browsing mode, deploying your change, and opening a new private browser to test if it is a client caching issue or a server caching issue?
Related
There are a several factors here (Heroku, Node, expressjs, react) as I'm working with a few technologies newer to me, so I'm not sure what the missing piece is.
I have a react/node app that is working for me in my local dev environment (using create-react-app).
My "/" route returns a list of documents, from which I create a list of links. When you click on one, it calls a route that returns a PDF.
This works great locally.
I've deployed it to Heroku and get the following behavior:
Click on link
Instead of opening the PDF, it opens a new tab with the correct URL, but the response is the list of documents instead of the selected PDF.
If I do a hard-reload, I get the same thing.
If I open dev tools in Chrome, I get the same thing.
If I open dev tools AND THEN do a hard-reload, I get the attachment to render!!
If I then do a reload again, it reverts back to showing me the list.
In Edge, I don't need to have dev tools open. Just a hard-reload will render the attachment, but clicking refresh after, brings the list back instead.
Things I've considered:
+ If it were a caching issue, I would expect subsequent reloads to render the PDF, despite whether the Control key were down or dev tools open. Both requests are returning 200, although the one that is not working as expected is returning 200 (from ServiceWorker). The Remote Addresses are also different.
+If it were a routing issue, I wouldn't expect the PDF to ever get rendered properly.
Things I've noticed in hunting this down:
+ The requests are differing
Any guidance is greatly appreciated!
Okay, I've figured it out. The rubber duck helped me :-)
If I don't use https, all is working fine. I'm not sure, however, why dev tools + hard reload allows me to make the request properly.
I just ran into a problem, While I was updating the js and css files for my website on a server, I do not see the immediate change. However, if I were to edit these files on a local computer or go on incognito mode on chrome, I see the change right away.
let's say I have:
div{width:100px}
after I change it to div{width:200px}, when I pop open the developer tool, it still reads div{width:100px}.
I feel like I need to clear something for the broswer, any explanation for this?
Check the caching headers you are using for static resources. The browser is likely using a cached version.
I'm having a very bizarre issue. I have been building a website locally on my linux box and all was well until I uploaded the site files to a place where i have some hosted space. Everything renders exactly the same except one element in my footer which i think is affecting some jquery animation i am using. I thought maybe I was missing files or hadn't uploaded the latest versions of everything, so I deleted the server directory and re-uploaded everything exactly as is from my local copy. And yet, the problem remains. I'm not sure how this is happening. Has anyone seen this before, or does anyone have an idea what could cause this? I'm baffled! Thanks everyone!!! I am attaching screen shots.
Seems to be a cache problem. Try to force a refresh with F5 or CTRL+F5.
Try clear your cache in your browser settings.
If that don't work, use Firebug (an Firefox browser addon) to check actual css at your footer. This will show the problem.
BTW: don't use spaces in your URL if you can. Don't use spaces in your filenames/folders.
I have two servers with virtually identical setups (the second that is working has been around longer than the other). For my newer server when I just put an address to a PDF in the browser it launches a download dialog. If I put the same address (just changing the server name) in the browser to my older server it displays in the browser just fine. There is no difference between the files themselves. The issue is I want to display these pdfs in an iframe on a page and the same thing is happening with the iframe (the new server launches a download instead of the pdf just showing in the frame).
Any ideas would be most appreciated!
Once I started looking into SP 2010 as being the cause I found that there is a default setting for all new 2010 sites that causes this issue. The following blog post had the most complete information on the subject:
http://nerdtastictips.blogspot.com/2010/08/sp2010-forces-users-to-save-pdfs.html
Please indicate web server your are using
Initial suggestion may be this has to do with MIME-TYPE setup
Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.