My website is: http://seompg.com/
There was definitely more to the website. It had a grayish background with more color schemes. Now since I migrated servers, it looks all blank. It almost looks like some CSS files are not loading. However, looking in console, everything seems to be loading just fine.
Am I missing something?
I see 403 Forbidden error on one of your theme files which might be related to custom styles?
http://seompg.com/wp-content/themes/3clicks/css/g1-dynamic-style.php
Please investigate that why this file is being given this error on the new server , I am sure you will get closer to solving the issue you are facing with custom styles.
Related
I was working on some CSS code and then suddenly the server stopped reflecting any changed made on the server. At first I thought it was a caching problem but I disabled caching on my browser and even tried using different browsers but still it's using the old version of my CSS file.
If I download my CSS file from the server and open in the text editor, it shows all the changes I made to the code but they don't reflect on my website at all. The site is using old version of the CSS file that doesn't even exist anymore on the server.
What on Earth is happening with my server? Can it be a router caching problem?
I can't answer this but try to add in your html, where you include the css this: ?v1.
Example: src="resources/yourDir/style.css?v1"
This will force everything to download the new css.
You can add after the ? everything you want. Like a timestamp, just a number or words. Whatever you like.
I'm trying to deploy a site to Heroku using node.js, and I've run into a bit of an issue. When I run my site locally, it looks as I expected it to. However, once I deploy it to Heroku, it seems that it does not recognize the CSS file I have included, despite the fact that it is using the same exact files and file structure.
I have confirmed that my HTML and CSS code is syntactically correct, and that the CSS file is being pushed through Git. I made a commit by changing one thing in the CSS to make sure that it was being pushed (it did).
Here's how I access the CSS file:
<link rel="stylesheet" type="text/css" href="css/style.css">
Here is an image of how the website looks locally (left) and deployed on Heroku (right) using the same exact code (the black boxes are just from me obscuring some personal details).
Website Comparison
Does anyone know why Heroku refuses to use my CSS? I've been racking my brain for 2 days on this can can't figure it out.
I had the exact same problem, it happend I miss one character in my whole code. Let me explain
When I heroku opened my project no css loaded, but interestingly enough jquery was working fine and the css that jquery was getting from the css file was just fine. The css file was not the problem.
Then I found that the browser was blocking some
content.
If you tell the browser to read the blocked content anyways, it will show the page no problem, but it will show a https with a horrible red line crossing it, not an option. Then I checked what content the browser was blocking
(blocked content)
it was my bootstrap link.
So I was linking my bootstrap with http and not https.
I added that letter s and it is working fine now.
I'm having a rough time with Magento. I spent a good deal of time going through the user guide on the Responsive theme, setting up Compass and editing SCSS files and whatnot, but was having the hardest time getting the changes to actually appear on the frontend.
I refreshed/flushed the cache, deleted contents of var/session and var/cache folders, I made sure the site was picking up the correct .css file under 'page source' in chrome.
It seemed like I could get the changes to apply if I changed 'merge css files' to yes, but even when the changes displayed if I made updates they wouldn't be pushed to the front end!
I changed the base URLs, however, and noticed that the secure URL for our site will load the correct .css and actually display the changes, while the unsecured URL says its loading the same .css file but NOT showing the changes.
I'm sure this is simple, but I'm going insane trying to figure out exactly what the problem is. Please let me know if you need more specifics from me!
Thanks a bunch,
Jesse
I'm downloading one page from reddit and saving it locally:
http://www.reddit.com/r/TheRedPill/comments/2uomrv/meta_sjws_are_reportedly_working_with_admins_to/
The HTML is identical in my test.html file, but when I open the local file in a browser, the page display is all messed up. Right Nav disappears, etc.
Normally I'd assume this is a CSS issue (and it definitely could be) but there are only three CSS files in the document, and they are all hosted remotely on www.redditstatic.com -- so they should still be working, right?
Is there something else I'm missing? Is redditstatic somehow smart enough to not serve CSS when I request it from my local machine?
What else could be causing the display issues? How should I troubleshoot?
Reddit uses external CSS, JavaScript, etc. to make it look as feel as it is. The website won't function correctly unless you download them all, even locally because the HTML doesn't know where to find the called file.
I have a site that I am working on and I've been running on dev mode, where it doesn't combine all the css files that I have into a single script. Everything worked totally fine. When running on prod, all of my css files is combined into a single file. This is using assetic to do so, however what happened is that everything breaks like crazy. Can anyone tell me why this is the case? Is assetic not combining the assets in the right order?
Just for reference, here's the site that runs on dev and here's the site that runs on prod
I think what is happening is that there is an error in the combined CSS file. Some errors affect parsing the rest of the stylesheet, so it just stops. It is why you aren't encountering it as bad in the individual files as it's not the entire styling of the page stopping however I do think there will be one or two declarations that are not loading in those individual files.
Have a look here at your Dev site's CSS validation. While a bunch of the errors are just straight from bootstrap and won't cause the parsing to stop altogether, there are some other errors that could affect the rest of the parsing of the sheet.
Things like this:
#order-history .
#order-history .data-block img {
That is line 73 of http://dev.shopious.com/css/3a76827_part_6_order-history_11.css
Just check through the validation results carefully and see what errors you find.