Forum Replies Created

Viewing 15 replies - 346 through 360 (of 390 total)
  • Working on it 😉

    Unsure, but it seems to be because the Kubrick theme (the new 1.5 default theme) uses different positioning than the “classic” skin (which works fine with the plugin). Gonna mess some more…

    I’ve tried my damndest, but I can’t get it to display the drop-down in the 1.5 betas based on the Kubrick theme. There’s doesn’t seem to be any place in the javascript that references and of the “classic theme” DIV tags, so I can’t figure out how to make it go 🙁

    But according to my server, it’s definitely working otherwise 🙂

    Sounds like you’re using MySQL 4.1 with PHP4, yes? That takes a little tweaking. Let us know what versions of PHP and MySQL you’re using.

    Grab the Jan9 nightly – that’s a fixed bug 😉

    Forum: Fixing WordPress
    In reply to: Images

    Give your floats a padding-top:5px; line then, to line up the top of the image with the top of the text. You’ll need to experiment with the number of pixels though to find the right value.

    Don’t quote me, since you’re using 1.21 and I’m on 1.5, but check your template (should be “/index.php”). The call to display the calendar should simply be <?php get_calendar(); ?> – if it isn’t, try changing it and seeing if it works.

    If that isn’t the problem, then someone else is gonna have to step in here 🙁

    Forum: Fixing WordPress
    In reply to: Images

    Adding a float to your IMG tag is the easiest way:

    <img src="http://www.nicktoye.co.uk/wordpress/wp-content/joss.jpg" width="163" height="200" alt="Joss Stone" style="float:left;" />

    That line would put the image on the left side of the post, and text would flow around it. Change left to right to put the image on the right instead.

    The 2nd easiest way is to add a pair of classes to your CSS that define float:left; and float:right;, then using the class in your IMG tag instead of a style declaration like above.

    Thread Starter rustindy

    (@rustindy)

    yup 😉 mostly they work though. some of us just had the bad luck to snag a couple during the middle of a somewhat large change in the code (sort of, at least).

    Thread Starter rustindy

    (@rustindy)

    You’re getting errors instead of the article post date on your pages and in the admin section? That’s all the fix above does – it just checks to see if the function is being sent a date or a dateserial and fills $i appropriately so that it ends up being a dateserial.

    I’m hoping the Jan9 nightly will either fix the function, or fix the function that calls it. This function (above) can currently only take a full date as a value, not a dateserial.

    Thread Starter rustindy

    (@rustindy)

    I haven’t been usually, no. But I did finally on the Jan7 nightly since it seemed so much had changed. Just seemed like a good idea 🙂

    I don’t think that running “upgrade.php” when you don’t need to will hurt anything though, so it’s safe to run it whenever you update the WP files. Usually you won’t need to though.

    If a nightly comes out that requires running “upgrade.php”, it’ll be noted in the codex’s 1.5 changelog page.

    Thread Starter rustindy

    (@rustindy)

    That’s because your host is running a *nix server. A windows server can only go back to 00:00:01 Jan 1 1970 – using PHP’s mktime() function on smaller dates gives an error about using negative numbers in the function.

    I think.

    Check that codex link posted above after the nightly gets on the download page – if I find a show-stopper bug or something very obvious to a viewer, it’ll be listed there. In general, avoid using the 1.5 nightly if there’s a known, obvious bug 😉 The Jan7 nightly didn’t have the problem.

    Thread Starter rustindy

    (@rustindy)

    Hehe 🙂 Keep an eye on http://codex.wordpress.org/Changelog/1.5 for nightly changelogs too, should be a good help if you’re updating your files regularly.

    Thread Starter rustindy

    (@rustindy)

    Quick hack-fix for “/wp-includes/functions.php”:

    Change the line

    $i = mktime(substr($m,11,2),substr($m,14,2),substr($m,17,2),substr($m,5,2),substr($m,8,2),substr($m,0,4));

    to read

    if (strlen($m) > 17) {
    $i = mktime(substr($m,11,2),substr($m,14,2),substr($m,17,2),substr($m,5,2),substr($m,8,2),substr($m,0,4));
    } else {
    $i = $m;
    }

    It’s an ugly hack, but it’s quick and it works 🙂

    Forum: Fixing WordPress
    In reply to: Bad Error Message!

    Ah k, your blog is 1.2, and the latest is 1.22. I don’t know if that file has changed since then (it probably has), but yup, uploading the original version for that version of WP is the way to go. Glad it’s working again.

Viewing 15 replies - 346 through 360 (of 390 total)