WordPress.org

Ready to get started?Download WordPress

Forums

Problem with Impact Theme - Browser Issue (23 posts)

  1. gsu90
    Member
    Posted 8 years ago #

    This is driving me crazy!!! I have no idea how to fix this problem. Please view my site

    http://www.tspndaily.com

    If you are using fire Firefox. There is no problem. However, as you scroll down that index page using IE or Opera, the text (towards the middle and down to the bottom of the page) gets larger. It is even affecting the footer.

    Can anyone tell me where to look to fix this?

  2. Nazgul
    Member
    Posted 8 years ago #

    Try fixing your XHTML validation errors. That usually fixes these kind of things.

  3. gsu90
    Member
    Posted 8 years ago #

    I guess I am screwed...

  4. whooami
    Member
    Posted 8 years ago #

    I guess I am screwed...

    Thats the spirit!!

    Its an unfortunate fact of Internet life that one cant toss up any ole thing and expect it to look just fine regardless of what browser someone happens to be using -- sometimes it actually takes some thought, patience, and work to make this stuff presentable :)

  5. gsu90
    Member
    Posted 8 years ago #

    Yes, I understand your point. It's just that I know my limits...and when it comes to coding issues such as this, my knowledge is limited. I then become frustrated because it will likely cost me money to fix the problem.

    Can anyone (with a little paitence) help a guy out?

    Thanks in advance.

  6. yosemite
    Member
    Posted 8 years ago #

    I guess I am screwed...

    Thats the spirit!!

    LOL!

  7. gsu90
    Member
    Posted 8 years ago #

    OK...can someone take a look at this and tell me how to correct the first first few errors. I can make the changes if someone can just tell me what to change them to.

    http://validator.w3.org/check?url=http://www.tspndaily.com/

  8. gsu90
    Member
    Posted 8 years ago #

    Still waiting...

  9. gsu90
    Member
    Posted 8 years ago #

    WOW...so much for support.

  10. Chris_K
    Member
    Posted 8 years ago #

    Problem is, you don't want support. You want someone to do everything for you. That's a bit different than helping someone with a WordPress question.

    And it means you need to be a bit patient until some charitable individual wanders by and decides to take on your task.

  11. moshu
    Member
    Posted 8 years ago #

    On that validation page if you check the box "Show Source" and click Revalidate - all the line numbers where the errors occur will become clickable links that will take to you the exact line in the source code where the error is. In that way you can figure out where in the code or the post the error is - and start correcting them.

    None of us was born with (X)HTML knowledge, but we learned. Personally, I've found this site quite useful:
    http://www.w3schools.com/default.asp

  12. yosemite
    Member
    Posted 8 years ago #

    WOW...so much for support.

    These are not WordPress issues. These are html/css/author issues. You know, GIGO (garbage-in-garbage-out).

    I started looking at your errors, but the fact that you can't address even some of the simplest errors, well, takes any wind out of my sails.

    And what's with that theme? I think it's the first one I've seen that refuses to give any (free) support. Bad choice if you need support...

  13. gsu90
    Member
    Posted 8 years ago #

    To all...forgive me if I appear to be rude. That is not my intent by any means. The fact of the matter is that I want to learn this and sometimes have no idea where to begin.

    Yosemite,

    I am not sure if you are being funny or not, but the theme came from the WP Theme viewer. Is there something that I should be looking for in a theme (other than likeing if for the way it looks)?

    Again, sorry if I came about the wrong way.

  14. gsu90
    Member
    Posted 8 years ago #

    I guess when I saw this thread...

    http://wordpress.org/support/topic/76943?replies=27

    I didn't think it would be too much to ask for the same kind of support.

  15. moshu
    Member
    Posted 8 years ago #

    You know, the big difference is that the other guy after they pointed him toward the validator, instead of making remarks on the "quality" of support... set down on his a$$ to work and went down to 2 errors.
    After that they started to help him to hunt down the remaining issues.

    I also don't think it would be too much to ask for the same kind of attitude.

  16. gsu90
    Member
    Posted 8 years ago #

    Now that I have the same kind of attiude what more do I have to do to get the same kind of support? I am not asking anyone to fix if for me.

    Just asking.

  17. yosemite
    Member
    Posted 8 years ago #

    I am not sure if you are being funny or not, but the theme came from the WP Theme viewer. Is there something that I should be looking for in a theme (other than likeing if for the way it looks)?

    I'm serious as a dead cat. I went to the theme URI of your theme and they will not give free support. I've gone to the theme URI's before to seek information and there's typically a list of changes, install information, and running comments from users (and responses from the author) regarding issues.

    And yes, I suggest when you find a theme you like, go to the site (THEME URI:) and see if there's any support for it.

  18. Chris_K
    Member
    Posted 8 years ago #

    Do you have a compelling need to spend time here arguing with the folks who could be helping?

  19. gsu90
    Member
    Posted 8 years ago #

    Do you have a compelling need to spend time here arguing with the folks who could be helping?

    Come on....I am trying to be as sincere as possible. I am not trying to argue with anyone. Please believe that. I am simply trying to get pointed in the right direction.

  20. moshu
    Member
    Posted 8 years ago #

    Though I've given you very detailed instructions above, I'll give you a last chance, since you asked "tell me how to correct the first first few errors"...

    1. Error Line 70 column 21: document type does not allow element "div" here; assuming missing "li" start-tag.
    <div align="center">

    It means exactly what it says.
    You have an ongoing unordered list with list items in between
    <li>.... and ...</li> tags. See the Lesson about lists at the link I gave you.
    You cannot have a <div> between two list items as it happens in your sidebar.
    Remove the div center (an its closing /div pair) from around the calendar - and several errors will disappear.

    7. In XHTML the correct tag for linebreak is <br /> - correct it.

    8. Again, in XHTML every image tag needs an alt definition for text-only browsers; insert in the image tag
    alt="picture-name". Also note, that image tag should end like this /> with a space before it...

    Does it help?

  21. gsu90
    Member
    Posted 8 years ago #

    Yes it does help in terms of understanding what you said. Thank you for the assitance...however I have discoverd something very strange.

    Out of curiosity I changed the theme back to the default them and it still get the same display issues with IE and Opera, it is fine with Firefox.

    Maybe this is not an XHTML issue. Any idea what the problem could be?

  22. whooami
    Member
    Posted 8 years ago #

    Does your browser not support viewing your source? I wasnt aware of there being any out there that were so archaic.

    Taking a look in Internet Explorer, it's simple to see where the larger text starts, at the end of the "Grambling AD has his hands full" post.

    Viewing your source, I see VERY clearly this:

    Now we need to just let this man do his job and support him in anyway we can…GVC send help (snicker).<span style="font-size: 12pt" /> <---

    its that span tag thats causing the large font issue.

    Other than that, and the one validation issue, your site displays the same in IE and firefox.

    --

    Confuscious say: Use that view-source and your brain, you will go far.

  23. gsu90
    Member
    Posted 8 years ago #

    How embarassing! I was so focused on trying to find the problen in the sidebar until I didn't even bother to look at the source code.

    Thanks (all) for your help.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.