Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Forum: Fixing WordPress
    In reply to: www. and non www.

    My particular problem has been corrected as the nameservers for the domain in question were temporarily disabled. With them back online the site is resolving correctly with or without the ‘www’.

    Forum: Fixing WordPress
    In reply to: www. and non www.

    What plugins are you using? I have the same thing happening here. I can get the ‘Server not found’ error to go away by inserting a ‘www’ in the hyperlinks that once coded fine as ‘domain.com’ without the www.

    kenwahren’s solution worked for me – thanks for posting it!

    The following 2 lines were added to admin-hooks.php just before the IF statement on line 160:

    $query_context = new stdClass();
    $query_context->context = array();

    The warning disappears using PHP 5.4.7 and all is well again.

    Forum: Plugins
    In reply to: Members only sections

    @talia – check the top of your template page. It should be something like

    <?php
    /*
    Template Name: Members Only
    */
    ?>

    – take note of the closing php tag. Also, there are a couple of errors that are keeping your page from validating. See the validator.w3.org.

    Forum: Plugins
    In reply to: Members only sections

    Mores – thanks for your login box. It helped me get around a problem with disappearing password functionality in WP 2.5.1 that surfaced after I imported the draft WP blog.

    What is strange is that the Posts are still ‘protected’ with their passwords, but Pages are not – even though I can see them and edit the passwords on the ‘edit page’ page.

    Hats off to everyone that bothers to report their solutions to problems here! TANKS!

    I’ve got the same problem of not being able to get to pages within a password-protected directory, which resides at the root alongside my 2.5 WP blog.

    None of the 3 inputs (given at msmeritt’s link above) for .htaccess worked in this case and I wonder if others are experiencing this problem with WP version 2.5.1?

    I’ve tried to modify the index.php file as per http://gqshen.com/archive/221, but no go.

    Htaccess mods didn’t help either, where this block was added above the WP section for the folder stats:

    # WP Fix
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_URI} ^/stats/(.*)$ [OR]
    RewriteCond %{REQUEST_URI} ^/failed_auth.html$
    RewriteRule ^.*$ - [L]
    </IfModule>

    Next, I’ll try the template-mod to check for a logged-in, registered user before showing the members-only content.

    Anybody having trouble with password-protected pages and directories in v2.5.1?

    Thread Starter LizzyFin

    (@lizzyfin)

    TimF, I saw that exact error (“The requested theme does not exist.” ) a couple times when I was trying to figure out what happened to my theme. If you change the name of the theme in the style.css while that theme is active, that is one way to produce that error.

    I would try to do just that…download the theme, give it a new name, upload it, switch themes and delete the old one.

    Cross your fingers, too, and let us know if it worked!
    Good luck!

    Thread Starter LizzyFin

    (@lizzyfin)

    Eric, thank you so much for helping me troubleshoot this “missing” css file. To update, the problem is resolved now. I’m not sure what had happened to the style.css file, but the fix turned out to be as simple as downloading the entire theme folder, then re-naming the stylesheet with a new theme name and uploading the “new” theme.

    Switching themes did not bring back the formatting of the css until I deleted the ‘old bad’ theme. That didn’t make sense to me, but anyway the new theme is working as intended!

    Thread Starter LizzyFin

    (@lizzyfin)

    Besides, if the stylesheet was actually missing from the theme folder, then the theme would be reported as broken, right?

    So, WP is really finding style.css??

    When I use Firebug to inspect the head of <http://piedmontsar.org/&gt; there is a plus sign next to the link for the css file:

    <link media=”screen” type=”text/css” href=”http://piedmontsar.org/wp-content/themes/search-n-rescue_copy/style.css&#8221; rel=”stylesheet”>

    In Firebug, clicking the plus sign to see the contents of the css file gives 186 lines of what would be a ‘not found’ generic 404 and not the css file as it should be.

    How is this happening? I have another blog that I have been checking everything against (it is also v2.5.1 and its working fine) to troubleshoot this problem and can’t understand what is going on here.

    Thread Starter LizzyFin

    (@lizzyfin)

    To check my file even further as to its css-ness…I double checked that style.css was working properly on my local server (also using WP v2.5.1) and used the file upload feature of the W3C Validator to make absolutely certain I was using the same file and, yet, the css validates.

    When I upload the same stylesheet to my online server, the pages of the web site that call it can not find it, nor can the W3C Validator when checking the xhtml of files that are supposed include the style.css file.

    Style.css has permissions of 666.

    Thread Starter LizzyFin

    (@lizzyfin)

    I’m afraid I don’t know what you mean that you ‘only see xhtml’ when viewing the style.css file. What would tell you that it’s been overwritten with xhtml?

    I took a prior version of the stylesheet and uploaded it and refreshed my browsers. I did this a number of times with different versions of the style.css and have the same results each time.

    I don’t understand how the W3C validator can’t find the file because I can see that it is there and have tried various permissions, 666, 644 to no avail. I can ftp a copy of a working stylesheet with a different name and then change the name to style.css check permissions and still have the unformatted output. Why can I then download said file and read it, alter and re-upload it?

    Beyond that I think the file is actually css. I opened the latest copy on the server (666) into html-kit, copy-n-pasted into the direct input of W3C Validator and the css validates.

    Thank you for the note on class=”post”, sewmyheadon!
    Still lost!

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