Domain is www.gafep.org
Website ran perfectly fine for a month. Then yesterday I noticed that the formatting is screwed on IE and Mozilla but is working perfectly fine on Chrome. Today morning I found that chrome also has same problem. The footer comes up to the top. The div tags that are supposed to demarcate are overlapping. (I have made a call to footer through php include in all pages)
Most baffling part is I had not made any change to code from my side and the website automatically goes haywire.
Worst part is when I open the backups I had made 10-15 days back when the site was working perfectly, they show the same problem. They were perfectly formatted before, however they all look the same now.
I cant get a hold of why this is happening. I have used Dreamweaver for coding. Please help.
Most likely the problem is related to browser caching. You said the the site worked fine for a while, then after a period of time it started no to. What likely it happened is that the web browsers cached the good .js and .css files for a period of time (depending on the browser settings), and even if the latests .js/.css files are broken those browsers didn't picked up these files until recently.
This is why you didn't notice the problem before, and this is why the same browser and the same site no longer work, even if before they worked and no changes were made since then.
Related
I just introduced tinyMCE into my rails 4.2.8 site to let manage formatted text in articles. Everything works fine actually but now and then a warning message produced by tinyMCE comes up such as "failed to load content css: http://myurl/assets/tinymce/skins/lightgray/content.min.css" but if a look at the debug console in firefox I see that url has perfectly found and loaded content.min.css.
When the warning message is there I can't enter anything in the textarea but the situation is fixed by reloading the page, then the rich text can be nicely entered and the relevant data is loaded correctly into the backend DB via relevant input form.
I don't understand the reason why tinyMCE is signalling such a warning despite the fact that the css file was actually found.
Any idea? Thanks and kind regards
Vincenzo
**** update on June 8th 2017 ****
Now I can better explain what's actually going on.
1) the problem shows up in Firefox v.53, if I use Chrome everything works fine
2) I am using tinyMCE in three distinct forms: one for new articles, one for editing, one for comments.
3) If I insert a few new articles no problem appears, the problem shows up just chenging the form in use: i.e. after insertion an article I try editing it or another one or else I try to insert a comment after havine inserted a new article. After the error message has shown I can always recover by reloading the page and no error appears eventually.
I guess there is some caching problem specifically in Firefox since all works fine in Chrome. I will try Windows Edge too..
2017/06/10
Tried Windows Edge on Win10: it works fine too.
2017/06/14
In the meantime I opened bug 1371910 at https://bugzilla.mozilla.org/show_bug.cgi?id=1371910#c5 a few days ago and the result was:
QUOTE
Hi Vincenzo,
Thanks for sending us the link. Unfortunately this seems to be a problem with tinyMCE rather than Firefox.
The initial load of content.min.css works correctly, and no other attempts to reload it seem to be made.
If it works in other browsers it is probably due to the developers doing things differently.
If you still think this is a bug in Firefox, please reopen this bug, and send us a smaller test case.
PS. Others seem to be having the same problem as you: https://community.tinymce.com/communityQuestion?id=90661000000Qct9AAC
I hope you find a way to fix it.
UNQUOTE
What the Firefox support says makes sense since I too whatched the content.min.css file was actually loaded by the browser so in must be tinyMCE to misinterpret something. Anyway I am still in the soup...
Whoever might have some interest at this issue please hava a look at:
http://vinloren-learn-rails.herokuapp.com/articles accessing this endpoint with Firefox v52..v54 the click show any article then going back via the 'back' link at the end of the article's content.
So i just finished up my website and uploaded it (New-ish web dev, please don't be to harsh). It works fine on all browsers except IE8. The website has a lot to load (images, etc.) so it is white screen for 1 - 2 seconds then fades into the actual site. On IE8 (IE9 + works just fine) the page stays on the white 'loading' screen forever. I have a lot of code here and I'm just wondering what you professional web developers here think i should do!
Website URL: http://cydronix.kkhorram.info/
There is two options: forget about IE8 or make it work on IE8.
Sounds like you have a problem with your javascript. To debug javascript on IE8, read this How to debug Javascript with IE 8.
I think one of your included .js files causing the issue. Check for the compatibility of your used javascript files
You said you uploaded the site - could you post the link if its live - otherwise without seeing some code the issue if difficult
I have been fixing up a sites JS, moving it to the bottom, minifying, etc. And it's all gone okay except on the blog (of an e-commerce site), as the page loads it's causing the header to be un-styled for a second or so, but it isn't happening on any other part of the site, even though they share the same CSS/JS. The blog is image heavy, but with images disabled (and I've tried disabling scripts too), it still happens. It's only happened since I've made changes, which I can't revert simply, but the changes are all positive and should help if anything. I can't see any JS causing it (as I removed the scripts to see if it was in there) and it doesn't happen in FF.
I would share a link but it's behind a closed staging server. And I could provide code but I'm not sure what, and there's a lot.
So, I had hoped I could use Dev tools to figure out what's happening, possibly the timeline view or something. I just don't know how I'd go about doing that.
Any advice?
Ed: I used the network tab on both the staging and the live site, as you can see from the image, they're identical, the css is the first thing loaded after the actual page, and on the live site it's actually ga.js. So it's even more of a puzzle now...
Don't worry, figured it out... It was the Stylebot Chrome Extension.. No idea why it was causing it now after making those changes though, and why it didn't affect the live site. I had no styles defined in it for this domain. A bug I guess.
Cheers all the same :)
Timeline tab in the dev tools is for benchmarking / site performance testing. If you want to know what's happening as in what content is being loaded, when and where, you can use the network tab for that.
It's also a common practice to stuff console.log() everywhere with some relevant message so you know when some part of code is being run.
I'm in charge of a website that is using a jQuery slider called "Accessible News Slider" and can be found # https://github.com/rip747/Yahoo-style-news-slider-for-jQuery. The website is http://thebright.com. When viewing the site on Firefox or IE, the slider works just fine, but when viewing in any webkit browser, the images for each slider load slowly and makes it look like they're falling from the top.
I'm not sure whether this is an actual bug in webkit or if this is something that I am causing by trying to gzip the images so the website will load faster. If anyone else has experienced this problem and knows how to fix it, I'm all ears. I'd also like to know if anyone else has seen this problem, but hasn't been able to fix it.
Thank you.
First : Optimize all the images. As per Google Page Speed (http://thebright.com), you can reduce another 233 KB, which will make your site fast.
Second : The issue that you mentioned - When you check the network tab in Google Chrome, clearly, there is some issue with the Cache Expiry header. Some how it is not setting Expiry header properly. So, every time you go to a page, it is loading the image once again even it was loaded previously. The current value that it is showing is : Expires:access plus 1 month. Seems Apache HTTP Server is not handling this header properly.
I am unable to replicate the problem when I want to but it seems like every now and then, my site using FCKeditor will load the interface but not the content (Clicking the buttons don't do anything). No javascript errors show and once it starts doing it, it usually is tough to get back to normal. The way I found to work best is to click the refresh button multiple times in a row, then the FCKeditor loads correctly. I have only seen this in Firefox
Has anyone else run into this problem or know a solution. It is a little annoying for me but I am afraid my client would be really confused
I have experienced the phenomenon you describe in FCKEditor's successor, CKEditor. Somehow, the IFRAME that contains the WYSIWYG content doesn't get loaded. What always helps is switching to source code view and back, but that's no solution.
I have seen the problem described on the Internet but with no solution.
Caching is not the problem, I think. Sometimes, if you press "reload" 20 times, it will break at the 21th time, and work again on the 22nd time.
What minimized the number of occurrences for me was to activate the thingy to the editor's bottom that shows the element path (body > p > span, I forgot it's name). I don't now why but since I turned it on, it very rarely breaks any more.
I have had this problem. I solved it by pre-loading FCKeditor in a hidden iframe during the login process so that when it got to the pages where it was used it was already in the cache.
i would strongly advise to upgrade to CKEditor which can not only be spelled out verbally without offending anyone, but also optimizes the loading time to minimal. I find it much more responsive than his F- friend.
I encountered this problem with firefox (not reproducible) and chrome (reproducible).
The solution that worked quite well in both cases was to wait for some milliseconds before initializing CKE :
setTimeout(function() {textarea.ckeditor({customConfig : 'custom/schnonfig.js'})} , 100);