Stylesheet doesn't work in firefox and IE - stylesheet

I'm loosing it right now because I have no idea why my stylesheet won't load in another browser than chrome !
This is the link to my page that need styling : http://peda.au-fil-du-temps.com/toutes-nos-offres/
Maybe I haven't seen something obvious, but I've tried and tried and tried... I don't get it.
Can one of you guys help me out with this ?
Cheers

Your sources are not linked correctly.
Failed to load resource: the server responded with a status of 404 (Not Found) http://peda.au-fil-du-temps.com/js/fitrify.min.js
Failed to load resource: the server responded with a status of 404 (Not Found) http://peda.au-fil-du-temps.com/js/fitrify.css
Failed to load resource: the server responded with a status of 404 (Not Found) http://peda.au-fil-du-temps.com/wp-content/themes/divi_theme_enfant/libel-webfont.ttf
Failed to load resource: the server responded with a status of 404 (Not Found) http://peda.au-fil-du-temps.com/wp-content/themes/divi_theme_enfant/libel-webfont.svg#libel_suitregular
Resource interpreted as Font but transferred with MIME type text/html:
etc....
hit F12 to open the dev console and investigate your url paths.

Related

apache gives 404 and failed on same resource

My server keeps crashing when i try to load a page with 404 images.
Theres about 10 misisng images, which should indeed just result in 404.
Sometimes the images however, return a failed status.
The same image will return 404 and after refresh return failed.
(failed)net::ERR_HTTP2_PROTOCOL_ERROR
It seems that this is crashing my server. Whas going on?

How to simulate a 500 http error on apache

I read about a lot of ideas about how to test the ErrorDocument 500 directive, but they don't work. If I put bad php code, I still get a page with my php error in it. If I create a bad htaccess file, I get the following error and not my custom error :
[an error occurred while processing this directive] The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a CGI script. [an error occurred while processing this directive]
I need to raise this custom error page to ensure that it works even though most applications will manage their own 500 pages.
Thanks
PHP errors aren't 500 errors. Apache is fine. PHP has encountered the error. This can be hidden in PHP.ini, but it results in a "white screen of death" instead.
On to the .htaccess problem. The .htaccess file controls the custom error pages for your site. If Apache cannot parse the custom error pages in this file it means there are no custom error pages set to display.

FineUploader Exception : XhrReadyState=0 and XhrResponseStatus=0

We're experiencing FineUploader exceptions with XhrReadyState=0 and XhrResponseStatus=0 on 5.4.1 in our production environment intermittently across browsers. We've checked out our CORS configuration for our S3 bucket and we do have the wild card origin header set.
Access-Control-Allow-Origin: *
Was looking at FineUploader CORS selectively working, and we do not set the sendCredentials value in our configuration.
Error from fine uploader is
XHR returned response code 0
The XHR response object contains the following values,
XhrReadyState=0
XhrResponseText=empty
XhrResponseType=empty
XhrResponseStatus=0
XhrTimeout=0
XhrAllResponseHeaders=empty
Update 1
So we captured a repro of this. It looks like one of our OPTIONS requests is getting a 403 randomly in the middle of the upload.
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) (a7db116d-26ec-4b45-9566-8697d42a7b4c.VOB, line 0)
[Error] Failed to load resource: Origin http://www.ourdomain.com is not allowed by Access-Control-Allow-Origin. (a7db116d-26ec-4b45-9566-8697d42a7b4c.VOB, line 0)
[Error] XMLHttpRequest cannot load http://ourbucket.s3.amazonaws.com/....
Origin http://www.ourdomain.com is not allowed by Access-Control-Allow-Origin.
Here is the screen grab from the Safari console. I was suspecting a network problem, but I wouldn't expect such a quick 403 response if a network issue was . Also, previous OPTIONS requests had just succeeded before and after the one that 403'd. We have configured CORS on our S3 bucket.
Status 0 indicates some issue either with your server or with the network. More specifically, it indicates that the response received was completely empty. This can be caused by CORS issues or even a temporary network issue. You'll want to examine these possibilities further in order to determine what is causing the issue for you.

prestashop theme MegaShop dose not uploading (shows) some photos

i'm using a prestashop 1.6 and MegaShop theme,
until yesterday everything worked properly,
pictures they displayed correctly, and everything was fine.
I didn't change nothing so it is strange.
I have deactivated the slider "Home Slider" and "Sub Banners on homepage" because of problem with photos.
This is what i got when the slider is activated:
so i get the errors in console like:
Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptnsubbanner/images/3fdef06374783c551eccda7f2cb336ff4f8eb649_Coffret%20cadeau%20de%20naissance.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptnhomeslider/images/1cb591825bb72f539ada3d5dab8e8f41fe2c865e_authentique.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptnhomeslider/images/1970776817102812dfdfe5bafb97a922f68b3508_Foutas-personnalisees.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptnhomeslider/images/345fc91dce74fb7b0f8ee69a5231e1c9737b2ed7_LINGE-DE-TOILETTE%20.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptnhomeslider/images/c9d990e33256b3d20c7f4850e4fed658b4a01c37_foutas-nids-dabeille.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptncolbanner/images/d813129dad7ed22e45ee4136a16c2f0a31918e9b_deco%20d%20interieure.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/tptncolbanner/images/636e73def62348d5bba09ab91885573b9f4bbadf_Les%20duos.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/smartblog/images/7-home-default.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/smartblog/images/6-home-default.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/smartblog/images/5-home-default.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
http://www.mille-et-une-fouta.fr/modules/smartblog/images/8-home-default.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
here's a picture with the console:
Here's is a link of my website:
http://www.mille-et-une-fouta.fr
I cannot upload photo to back office,
when im uploading the photos, i get the images with question mark like this:
Can you please help me with some advice
Thank you in advance for your reply and help Mike.
This is really strange after debugging i found that the image exist on the server but it is not showing correctly
You must permalink settings to default once , and again return to its previous state with this problem will be solved

How to debug a 404 error on apache server ( lamp )?

I came across 404 error a few times and i have difficulties in debugging this kind of problem.
What is the strategy and tools available to analyse such problems (firebug, logs...).
How to differentiate and fix the cause ?
page not existing ,wrong path , redirection and rewriting ,server problem ...
404 error code means that a file is not found for whatever reason.
Just check that the file exists and that the path you use is right.
You can analyse sent requests and received responses headers and body in your browser's developper console if you want more details about why some request failed.