I have a link on the site I'm working on that is giving me issues in chrome. In firefox and ie (I will never say this again) is working as it should, but chrome is showing me this message.
And it's not quite making sense. There is only one redirect going on after you click on the site. Is there anyway to fix this in Chrome? I have cleared my history/cookies/cache.
I will provide as much info as I can, but at this moment I'm not sure what to include to help.
Related
I am using this embed code for a site. The site is a Django site. I apologize if my terms are wrong, I'm not a developer. . Periodically I return to the site and the graph will not display, but the logo from the host site does. I suspect that it's a caching issue. I tried "no-store" but I'm not sure if I pasted it in properly.
I want to add a random number generator to the embed code. In my mind that would be similar to a refresh - again, not a programmer. Django strips css and possibly more. Can anyone either solve my problem or write the random number generator to make the "border-width" 1, 2, or 3? Here is my site with the bug. https://www.twelvebridges.com/twelve-bridges-market-report/. I encounter the bug on Chrome on a macbook. Never the first visit and a refresh solves it every time.
I tried "no-store" but probably in the wrong place. I tried Classic Cache Killer as a Chrome extension on my site. I added a gif on the site even though I cannot really articulate what I thought that would accomplish.
First post on StackOverflow, so please forgive any protocol lapses!
I've found similar problems to the one below elsewhere on SO, but none that's an exact match, nor a solution that hits the spot.
I have a client site with FB Share and Like buttons, all of which work perfectly on straightforward named pages. In the case of the shop and blog pages I need to use a querystring, which works perfectly on other sites, but not this one! I've run the FB Debugger on the affected pages and all looks hunky dory.
Here are two example pages with the problem:
http://www.fabniki.com/productdetail?pid=251 and http://www.fabniki.com/blogdetail?id=327&p=1.
In the case of the shop item, the text Facebook is showing isn't even on the page. I've tried clearing cache, forcing an FB cache refresh etc.
My own site uses a similar querystring system for my blog, and this works absolutely fine with Facebook shares and likes.
I'd be very grateful for any suggestions!
OK, the problem was - unsurprisingly - entirely of my own making. I'd allowed myself to get bogged down in the debugger, which looks at the exact URL you paste into its input field. If you're sufficiently idiotic, it may not occur to you to check if this is the actual value being passed to FB by your Like and Share buttons. Doh!
Thanks to some excellent support from FB developers, the problem was spotted and corrected with only minor dents to my ego.
I wanted to answer my own question, a) to avoid wasting people's time and b) to give Facebook Support a bit of appreciation for a change!
I have a CF9 site set up locally on OSX Snow Leopard, and it's started to behave very strangely - probably about 1 out of every 5 times I load any page in the site, it will throw a 'Cannot find CFML template for custom tag' error. I just refresh the page and then everything works fine. It can happen on any page, but it never happens consistently with any one page. Furthermore, this doesn't happen at all on the live server when the code is checked in through SVN, so I figure it has to be some kind of configuration problem on my local instance. I can still do my work, but it's pretty annoying having to refresh pages ALL the time. Has anyone run into similar difficulties?
Try using <cfmodule template="pathTo/yourTag.cfm"> rather than <cf_yourtag>, so you can specify the exact location of the template (in case the server is getting confused as to where it resides).
FYI, this is based on a tip from Raymond Camden's blog post: http://www.raymondcamden.com/index.cfm/2006/8/17/ColdFusion-Custom-Tag-Tips
Chris, odd that I should run into your question now, as this just started happening to me last night. I have all of my CF errors being emailed to me, and I am seeing that similar problems are happening across multiple sites that all run the same software, some of which haven't been touched in a long time. That got me thinking, it's probably a corrupt compiled template in the CF cache. You can recompile the template by making a slight change to it, say add an extra line or a comment or something, then access the site again. Or, purge the whole cache and let CF rebuild everything, which is likely what I'll do since who knows what else might be affected.
Clearing the Cache in Coldfusion Production server
Anyone else ever have the Firefox toolbar "refresh" button not work for a particular page? Works everywhere else. Firefox 3.6.15. Any clues?
EDIT: For what it's worth, I later set network.http.use-cache false, and the problem went away. No idea whether that was much more than coincidence, though.
There is not a lot of detail to go on in your question, but what will often happen is that firefox will cache certain elements of the page and not actually re-fetch them from the server. Try using the TamperData Add-On for firefox to see exactly what data is being transferred from the web server.
You can also just try a Ctrl-F5 to do a force page reload.
While I can't say that I have had that problem, most "weird" behaviors I've run into were due to extensions. You might try disabling some of the more intrusive ones. Greasemonkey perhaps?
A while ago, I worked on an application where a manager can approve/deny xxx applications. When some body selects an action from a drop down, it opens a cfwindow and loads cftextarea richtext="yes" in there, so that they could enter reasons for approval/denial.
Now the culprit is that in production, the fckEditor has a ton of funky chars in IE8. Same thing won't happen in FireFox. Also, the IE8 does not show the same stuff in dev.
I have looked at the scripts in /cf_admin/CFIDE/scripts/ajax/FCKeditor, they are all the same.
Since this wasn't an issue before, I am not sure where to look at. Something got updated on the server which probably causes this problem. Does anybody know what could be the problem?
It turns out the vp put the header X-UA-Compatible: IE=IE7 in IIS to force IE8 emulate IE7. When I made them change this to X-UA-Compatible: IE=EmulateIE7, everything started to work perfectly again. For more details see Introducing IE=EmulateIE7.
Hope it helps others. Thanks.