Forum Replies Created

Viewing 15 replies - 1 through 15 (of 29 total)
  • The problem is in your HTML. You appear to have an unclosed ‘div’ for your main content.
    Most likely you have a Page Template, which is used for single pages like posts and your privacy policy. Towards the bottom of this file, you’re missing a </div> before you call the sidebar.

    You won’t solve it by lookin in WordPress files.
    If your host provides access to cPanel you can view the mySQL databases linked to your account. You can also view any users linked to that database. If a mySQL user doesn’t exist, recreate one with the same name & password as that listed in your wp-config file. Add that user to the database with permissions. Then try to reconnect to WordPress and it should work.
    If this is indeed the problem. ??

    Contact your host’s support for assistance.

    It is possible your username no longer exists, or doesn’t have access to the database WordPress is accessing.
    Connect to your hosting account via cPanel (or alternative). Check if the mySQL database has the username you’ve used in your wp-config file and if that username has permissions for the WP database.

    You’ve got a li declaration in nav.css as:
    li a
    {
    text-decoration: none;
    background-color: #2f77a9;
    color: #FFF;
    padding: .2em 1em;
    border-right: 1px solid #fff;
    }

    You’re not limiting the styles to lists within navcontainer so the rules will be applied to all instances of li. Change to (like you’ve got with ul):
    #navcontainer li a

    You could read up on ‘CSS selectors’ and modify your code to what is accepted as best practice.

    What theme are you using? To remove bullets for lists in the sidebar you would need the id of the div surrounding the sidebar.

    Adding the following to your stylesheet should remove the bullets for _ALL_ lists (unless the definition is being overridden in a class).
    li {list-style-type: none;}

    More details about css list properties

    I’m not sure, but I guess you’re referring to the IE 3px issue. I direct your attention to box model lessons, glish’s list of hacks and this google search on the 3px issue.

    BTW, when you post a question here please include more information – theme you’re using, WordPress version, etc. Also read this.

    Forum: Installing WordPress
    In reply to: Install error

    If the file is corrupt, delete it and download a new copy of WordPress (or if you can get it, just the required file).
    Check the permissions on the file – are they set to at least 755. Check that the file exists on the server, it may not have been uploaded or may have been uploaded with zero length.

    BUT, it seems to be a PHP-related error so you should contact your hosting provider, or research the solution on a forum geared toward PHP solutions.

    In the support forums – topic 22383 seems to have an alternate solution.

    Forum: Fixing WordPress
    In reply to: Javascript Problem

    [deleted – double post]

    Forum: Fixing WordPress
    In reply to: Javascript Problem

    With the semicolon at the end of that line, the script works fine for me. Also validates to xhtml 1.0 transitional.
    Why do you say you had to change the javascript code to lowercase?

    Forum: Fixing WordPress
    In reply to: IE funny white box

    Well, for starters, you have two <head> and two <body> tags. If you are including files like header.php, footer.php etc., you do not need to redefine such tags in each file.
    Validate your code.

    The table you are using for your navlinks and the header image (which IMHO is too freakin’ big) has a total width greater than the total width of review*.gifs you are using…hence the whitespace. After review20.gif you are missing an image to account for that extra width.

    From viewing the attachments on the plugin pages you’ve linked, it seems that the plugin is lacking the closing php tag.
    Add the following after the last line for both files:
    ?>

    Check that it’s not being overwritten somewhere else. It does appear to be defined twice in the stylesheet. The second declaration will take precedence. Also, in the header file, there is a declaration for #page dealing with the background images. An option is to place the border style in the header (but not in the PHP if statement – place it after the #footer styling), and you should see the border around the #page.

    Unfortunately I’ve got more problems for you. In IE6 Win, the columns are shifted to the right.

    If we are going to use Google, we could have radio buttons for the aforementioned WP Support search and Codex, alongside the ‘Search www.ads-software.com’ button.
    Since Google searches older posts, perhaps we should encourage use of a ‘completed’ tag or some formatting (coloring the thread title’s background – like active plugins’ green) for topics that have been deemed to be useful in finding a solution by the original poster (or all questions answered). Similar to expertsexchange, etc.

    I’m using IE6 on windows, and I don’t have any UI issues. The first post appears just fine, at the top of the page, just like it does in FF1.0.3.

    Several errors stem from <p> tags that do not appear to be closed – lines 99, 110, 125. They should be removed (unless they _are_ closed, which I am missing).

    I think, the line 85 error occurs because the <script> is within the <ul> tag (opened on line 59 and closed on line163).

    Hope this helps.

Viewing 15 replies - 1 through 15 (of 29 total)