Forum Replies Created

Viewing 15 replies - 316 through 330 (of 390 total)
  • Hokay you two, head to http://test.innereyes.com and try and duplicate the problem. Login is “admin”, password is “wptest”. Let me know how it goes 🙂

    Amiantos, if you can, disable all your plugins temporarily and see if the problem still occurs (i assume you’ve probably done this already, but best to be certain).

    Because 99 times out of 100, that’s what it is – a firewall issue.

    The suggestion, of course, is that because the demo site you tried works and yours doesn’t (now), it’s something specific to your machine. On the other hand, you’ve had others login to the system who get the same error, which suggests a server-side issue (or a bug).

    This started just few days ago for you? A week ago? Two?

    Ah k, didn’t know that had already been done.

    What versions of MySQL and WordPress are you using?

    In the site admin area, go to the Options menu, then Writing – it’s the 3rd option down – just uncheck the things you want unchecked 🙂

    Well, if either of you wants to email me your password and step-by-step instructions on how to trigger the problem, I’ll be happy to do the double-check for you.

    russ@innereyesTAKETHISOUT.com

    Jose, were you having this problem as well?

    Happy b-day! Don’t think I can make the drive in this weather though, sorry to say…. Have a drink for me 😉

    It’s *extremely* unlikely that some sites requiring headers work while WP doesn’t, unless a firewall or router (or privacy setting in the browser) is blocking the header transmission on a per-domain basis.

    To see if headers are making it to your domain at all, create a file named info.php containing the following lines:
    <a href="info.php">click me</a>
    <?php
    phpinfo();
    ?>

    Upload the file and open it in a browser. Click the link at the top. When the page refreshes, scroll down to the <b>HTTP Headers Information</b> section (about 1/3 of the way down). The field called “Referer” should contain your domain name and the full path to the “info.php” file you just created (like “http://www.mydomain.com/info.php&#8221; or similar).

    If it does, then referrers are not being blocked, and it is a bug. If the field is empty or contains anything but the exact path to your “info.php” file, then it is something else – most likely a router/firewall or privacy setting.

    The important thing is to *click the link first* before checking the referrer setting – it’ll be blank (or non-existant) since you will have typed the address in manually. So click first, check after 😉

    Positive 😉 You had 49 <div> tags, but only 48 </div> tags 🙂

    You’re missing a </div> tag in there. Just stick it in right before your </body> and see if it works 🙂

    Your nav links aren’t working?

    I just mean the “new” way seems more logical. Why can’t the archive pages be paged as well as the index page? It keeps loading times low, and you don’t end up with 40 or 50 posts to scan through to find what you’re looking for.

    But like I said, it might be a good idea to have a seperate paging criteria for archive pages. I only show 6 posts on my index page, but I’d like 10 or 20 on the archive pages instead. Particularly if your archives only show the summary info instead of the teaser text.

    Forum: Fixing WordPress
    In reply to: Asides with 1.5

    Because it uses the custom fields for it’s input, yes, it’s limited to being attached to an existing post. Like i wrote in the thingy, it’s all i need for mine 🙂

    You want Matt’s Asides fer sure 😉

    In “suggest_data.php”, adding the following code right after the include line will make it work in 1.5:

    if(empty($qu)) {
    $qu = $_REQUEST['qu'];
    }

    Nope, not gonna happen. I don’t know where to change the source to get the last 31 “physical” days listed instead of the last 31 “post” days.

    Even though I like the idea of having an entire month’s posts on one page (sort of – that might be a really big page), I’m not sure it’ll happen. You might end up with a page containing a hundred posts then, if your blog is really busy. Then, in order to be consistent, a yearly archive would have to display an entire year on a single page. That would easily hit 150 to 200 entries on a single page.

    Perhaps a second pair of field can be added to the system for archives specifically? Another “# of days/posts” selection that only affects the archive pages 🙂

Viewing 15 replies - 316 through 330 (of 390 total)