Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter jmdesantis

    (@jmdesantis)

    Oh. Thank you so much. That worked. Though I think I’ll just stick to the html version, if that’s all right.

    Both you have been an immense help with this.

    Thank you!
    Thank you!
    Thank you!

    If I seem melodramatic it’s just that I’ve been going mad trying to debug all of these issues. Minus a few corrections and additions, I should be good to go. Looking forward to officially launching the blog (the real thing, not the faux-html thing I’ve been using) next Wednesday, if possible.

    Thanks again. All the best.

    Thread Starter jmdesantis

    (@jmdesantis)

    I see why. The code is

    <img src=”../images/siteart/logo_banner.png” width=”780″ height=”180″/>

    for calling the header image, however, it’s calling it from:

    /2012/11/images/siteart/logo_banner.png (as apparent from the links in the top menu as well)

    How do I fix the code so that it’s going back to the main folder to then go to the images folder?

    Thread Starter jmdesantis

    (@jmdesantis)

    That doesn’t seem to be correcting it, though logging out did.

    Some of the error issues I’m having trouble finding, but a new problem became apparent. Though the code is the same for single.php as it is for page.php and index.php, for some reason when I look at an individual post, it’s not showing the images in the sidebar or header:

    https://jmdesantis.com/2012/11/hello-world/

    Thread Starter jmdesantis

    (@jmdesantis)

    Thanks for the response and checking out those errors. Unfortunately, some of what seems to read well in Dreamweaver doesn’t translate into WordPress. I’m going to go through the errors and correct them today. So thanks for running that for me, otherwise I wouldn’t have known.

    As for the clear: both; code, it seems to have worked fine, without the need of creating a new way of adding in the background colour. Is that showing on yours too?

    NOTE: I’m running on Firefox as well and I’m still seeing the extra space between the top of the page and the top of the wrapper.

Viewing 4 replies - 1 through 4 (of 4 total)