Guys I need your help. Everything is broken on my site. Don't know what happened, pushed some new changes to the server and now everything except for chrome on mac is rendering it like a teenage girl's bedroom wall of magazine clippings.
Everything is broken on my site. Don't know what happened,
Yes, you do:
pushed some new changes to the server
So, the best idea would be to roll back those changes to the last working version. Then, trying to fix it all won't be such a "panic" situation.
If rolling back is not possible, you're going to need to look carefully at what changes you made and do some good ol'fashioned troubleshooting. Then, you should look into using a version control system (or, at the very least, making backups before you update something).
@traq I would appreciate help fixing the problem. Yes, I obviously did something incorrectly in my last batch of changes. However I don't know what it is, so unless you would like to help find the rotten apple, don't waste your energy on this issue.
I'm not 100% sure what the problem is that your having can you give a little more detail please. Only thing I can see is that the images aren't loading and that's because you have linked them from the root and not relative but yet again i'm not 100% sure what the problem is that you are having.
@Blackhawkso When not viewing in Chrome, everything seems to be broken. Mozilla is a good example. Open a window in chrome as well as another browser to see what it is supposed to look like.
Divs are out of place, things aren't positioned anywhere near where they are supposed to, etc.
I am not at all worried about the images right now. All of my problems have to do with position. I know that they images are going to bring errors because i took all the files into another folder to keep away from public view.
@matt_sanford Just to make you aware it seams to be a problem with firefox. I've checked your site on both Chrome, safari and IE10 on win8 and it is working fine. I know this probably don't help a lot but it something i've never come across before and thought that any information could be useful.
Before brushing off what @traq had to say because he wasn't doing the work for you, he actually had the right suggestion. When you work on a large scale site and this happens, it's exactly what you'll have to do to debug the issue.
indeed. I wasn't trying to "dump" on you, @matt_sanford. It was sincere advice.
At the time, I was "out and about" and didn't have the capability of troubleshooting (only one browser, and not the one you stated had a problem).
There was also the possibility (unlikely, I thought, but still possible) that you did have backups somewhere, and hadn't thought of that approach. I was hoping that, even if you didn't, you would be able to learn from the experience and plan for this sort of problem "next time."
I'm glad it's sorted now. Good luck with your future coding.
+1 on what @chrisburton said. There is nothing more annoying than people that pretend to ask for help and guidance when in fact they're looking for someone else to do the hard work for them.
I'm surprised you even received help on this thread after blowing @traq off like that...
I didn't see it that way, words can easily be misinterpreted so I didn't think too much of that comment (though he did seem to fail to see traq was already helping) :)
Thanks, folks, though I wasn't offended. This is a very common situation for web help forums - sometimes a person really is "just being lazy," but more often, they've honestly been trying and cannot solve the problem on their own. The real issue is that they may be expecting to be "attacked" or ridiculed, and so are defensive before even reading responses - and it's easy to misinterpret the "tone" of plain text. Combine that with the fact that a person may already be quite frustrated with a problem they can't solve on their own, and it's not surprising that anything that is "not a solution" is interpreted as "what an *******, I'm asking for help, not to feel stupid."
Not saying that that's the correct attitude/interpretation, of course, but it takes experience and patience to successfully ask for and accept help in an online forum.
@traq You got right on the head. I was fiercely frustrated with that issue and I was really just looking for a direct answer. However you gave sound advice indeed which I will be using in upcoming projects. So thanks!
It Is hard indeed to interpret plain text in any sort of tone , but I most certainly should have done a better job at trying to convey a more thankful tone rather than indifferent and defensive. My most humble apologies to you and whoever else felt offended by my comment earlier.
Guys I need your help. Everything is broken on my site. Don't know what happened, pushed some new changes to the server and now everything except for chrome on mac is rendering it like a teenage girl's bedroom wall of magazine clippings.
here is the link. Please help!
There is an extra closing div on line 182 that isn't needed, maybe that's it?
Yes, you do:
So, the best idea would be to roll back those changes to the last working version. Then, trying to fix it all won't be such a "panic" situation.
If rolling back is not possible, you're going to need to look carefully at what changes you made and do some good ol'fashioned troubleshooting. Then, you should look into using a version control system (or, at the very least, making backups before you update something).
@traq I would appreciate help fixing the problem. Yes, I obviously did something incorrectly in my last batch of changes. However I don't know what it is, so unless you would like to help find the rotten apple, don't waste your energy on this issue.
I'm not 100% sure what the problem is that your having can you give a little more detail please. Only thing I can see is that the images aren't loading and that's because you have linked them from the root and not relative but yet again i'm not 100% sure what the problem is that you are having.
@Blackhawkso When not viewing in Chrome, everything seems to be broken. Mozilla is a good example. Open a window in chrome as well as another browser to see what it is supposed to look like.
Divs are out of place, things aren't positioned anywhere near where they are supposed to, etc.
Check the console:
And since you seem to rely a lot on background images... I think either you moved tour image folder, or you deleted image files.
I am not at all worried about the images right now. All of my problems have to do with position. I know that they images are going to bring errors because i took all the files into another folder to keep away from public view.
Try removing
display: -moz-inline-stack;from summit.css line 162 and 291@matt_sanford Just to make you aware it seams to be a problem with firefox. I've checked your site on both Chrome, safari and IE10 on win8 and it is working fine. I know this probably don't help a lot but it something i've never come across before and thought that any information could be useful.
@matt_sanford
I've just tried that in firefox and it has worked
I've edited my comment, there is another one on line 162 that needs removing too :)
@CrocoDillon Thanks! Any guess as to why that was messing things up?
@Blackhawkso Yeah don't worry about it. I appreciate it though!
I didn't know about the -moz-inline-stack display value but apparently it stacks up child elements on top of each other :P
Edit: I've actually seen it before here http://blog.mozilla.org/webdev/2009/02/20/cross-browser-inline-block/
As a FF2 fix, wonder if that ever worked. But 1, it needs to be before
display:inline-blockand 2, FF2 is dead so just drop it and you're fine :)Before brushing off what @traq had to say because he wasn't doing the work for you, he actually had the right suggestion. When you work on a large scale site and this happens, it's exactly what you'll have to do to debug the issue.
indeed. I wasn't trying to "dump" on you, @matt_sanford. It was sincere advice.
At the time, I was "out and about" and didn't have the capability of troubleshooting (only one browser, and not the one you stated had a problem).
There was also the possibility (unlikely, I thought, but still possible) that you did have backups somewhere, and hadn't thought of that approach. I was hoping that, even if you didn't, you would be able to learn from the experience and plan for this sort of problem "next time."
I'm glad it's sorted now. Good luck with your future coding.
+1 on what @chrisburton said. There is nothing more annoying than people that pretend to ask for help and guidance when in fact they're looking for someone else to do the hard work for them.
I'm surprised you even received help on this thread after blowing @traq off like that...
I didn't see it that way, words can easily be misinterpreted so I didn't think too much of that comment (though he did seem to fail to see traq was already helping) :)
Thanks, folks, though I wasn't offended. This is a very common situation for web help forums - sometimes a person really is "just being lazy," but more often, they've honestly been trying and cannot solve the problem on their own. The real issue is that they may be expecting to be "attacked" or ridiculed, and so are defensive before even reading responses - and it's easy to misinterpret the "tone" of plain text. Combine that with the fact that a person may already be quite frustrated with a problem they can't solve on their own, and it's not surprising that anything that is "not a solution" is interpreted as "what an *******, I'm asking for help, not to feel stupid."
Not saying that that's the correct attitude/interpretation, of course, but it takes experience and patience to successfully ask for and accept help in an online forum.
@traq You got right on the head. I was fiercely frustrated with that issue and I was really just looking for a direct answer. However you gave sound advice indeed which I will be using in upcoming projects. So thanks!
It Is hard indeed to interpret plain text in any sort of tone , but I most certainly should have done a better job at trying to convey a more thankful tone rather than indifferent and defensive. My most humble apologies to you and whoever else felt offended by my comment earlier.
No problem, as I said, I wasn't offended. But now that I know, I'll be sure to help you again next time. :)