anmalee1
09-14-2011, 01:40 PM
I'm at the end of my rope trying to figure out what's wrong with this. I'm creating a website for a friend who is planning to create a music CD later this year. I'm creating the website, but she is going to maintain it once it's finished, so I'm using Weebly (www.weebly.com) to build the site. Weebly has drag and drop functionality, so it will be easy for her to update it once I have the site finished. I can also add some features extremely easily without having to code it all from scratch, like a blog feature.
Weebly does give access to CSS (one sheet for the site) and HTML for each page, so I can customize a lot of things as well. After a lot of tweaking, I was able to get most of the site done the way she wants it, but I'm having some major trouble with the alignment of the blog sections in Firefox.
IE and Chrome are displaying the blog with no problems, but in Firefox, each page that has a blog has the blog content shoved way off to the right side of the page.
The problem is that the code that controls the blog content is Weebly generated code. I didn't write it. So I've spent hours looking at it with Firebug and trying to see what is making it get shoved to the right side. I don't know if it's a problem with their code or if it's something that I wrote in the custom code that is interacting problematically with their code.
If any of you more experienced coders are up to a challenge, I would love help trying to figure out what is making Firefox freak out with this blog content.
The site is published at:
http://bethanystarhughes.weebly.com
The alignment on the home page seems to work fine in Firefox, IE and Chrome, so no problems there. The pages with blogs on them that are having issues are:
News, Reflections, and Guestbook
I obviously haven't done any other aesthetic things to these blog sections yet (i.e. making the background behind it lighter and readable), because I figured that I should get this major issue of the alignment sorted out before I dive too much more into coding the finer details.
Through the custom CSS sheet, I should be able to override any of the automatically generated blog code from Weebly, so if I can just find the issue, it should be simple to fix it by overriding it.
Thanks in advance to anyone who can help! Also let me know if you need any other information that you can't pull from the code that is published on the live site.
Weebly does give access to CSS (one sheet for the site) and HTML for each page, so I can customize a lot of things as well. After a lot of tweaking, I was able to get most of the site done the way she wants it, but I'm having some major trouble with the alignment of the blog sections in Firefox.
IE and Chrome are displaying the blog with no problems, but in Firefox, each page that has a blog has the blog content shoved way off to the right side of the page.
The problem is that the code that controls the blog content is Weebly generated code. I didn't write it. So I've spent hours looking at it with Firebug and trying to see what is making it get shoved to the right side. I don't know if it's a problem with their code or if it's something that I wrote in the custom code that is interacting problematically with their code.
If any of you more experienced coders are up to a challenge, I would love help trying to figure out what is making Firefox freak out with this blog content.
The site is published at:
http://bethanystarhughes.weebly.com
The alignment on the home page seems to work fine in Firefox, IE and Chrome, so no problems there. The pages with blogs on them that are having issues are:
News, Reflections, and Guestbook
I obviously haven't done any other aesthetic things to these blog sections yet (i.e. making the background behind it lighter and readable), because I figured that I should get this major issue of the alignment sorted out before I dive too much more into coding the finer details.
Through the custom CSS sheet, I should be able to override any of the automatically generated blog code from Weebly, so if I can just find the issue, it should be simple to fix it by overriding it.
Thanks in advance to anyone who can help! Also let me know if you need any other information that you can't pull from the code that is published on the live site.