papadoc

Not for nothing, but I just found this post because I did a Google search on that IP address – 94.23.238.222 – which I think has been instrumental in getting my site temporarily shut down by the host due to SQL calls.

ANOTHER Google search suggests the IP is the source for a comment-spammer. I don’t know whether that sheds any light on your own issue or not, but it’s pretty weird.

Is the plugin author still checking this thread?

Absolutely loving this plugin so far… The only thing I’d change at this point is:

When the author of a post comments on their own post, or replies to a comment there, and someone replies to that reply, they get both a notification from the plugin, and a notification from WordPress. If you switch off the WordPress function, they don’t get notified when a reader first comments on their post.

Is there some way of changing a setting, so that the plugin or WordPress knows when an e-mail notification is being sent, and doesn’t send one itself?

Fixed this… I think it was a conflict between this and Brian’s Threaded Comments, which I had failed to disable.

Beautiful plug-in, yo.

It turned out that it was a fairly simple matter of duplicated div tags and the need for a call of clear: both.

IE was more forgiving of the screwy code then FF and others, is all.

Thanks for trying to help, obscure. I already knew that it didn’t validate, but I’m happy enough to have a site that works, which, thankfully, it now does.

DianeV, that’s fine, and is what I already plan to do with future projects. I have acknowledged that it isn’t a Firefox fault.

That said, this website is now already done, and in use, and works as I want it to aside from this one cosmetic thing, which IS working in IE and not in Firefox, so I was hoping that someone might be able to help me fix it? Do you have any ideas…?

Does anyone have any clues on this problem? It has just occured to me again that I haven’t sorted it yet.

Okay…

So I’m looking at this, and realise that it’s definitely something to do with the CSS, but sadly no permutation of putting in the extra </div> has actually fixed it.

Anyone else got any ideas? I can’t work on this at work, because we aren’t allowed Firefox… I’d really appreciate someone finding a solution for this for me, as I suspect it’s a matter of doing some kind of CSS hacking for Firefox.

(One thing that MAY be pertinent to this issue, although I don’t see how, is that I have used the Timestamp feature to delay release of these items. However, I don’t see how that would make a difference to the archive feature.)

YES! That’s it. Thankyou so much.

Hmm… You know, I thought I’d tried every permutation of extra </div> tags… Did you spot a specific discrepancy in the two pages that are flunking out?

Also, do you use any particular method for working out which divs lack closing tags, or do you literally just go through the code and tally up the numbers? I’d be really interested to know… I use IE’s diagnostic tool, and Dreamweaver, but even with those, I still have to count through code to really spot where problems lie…

Kafkaesqui had it with his last suggestion… thanks for all your insights, guys…

pcmt said: “I don’t see /wp-content/themes/default/print.css on your site.”

Yeh, this is me not looking at the files properly and forgetting that the default theme isn’t the one I’m using.

Good point. All changed to lower-case now… but still not working! Although that would have been a bonehead typical error on my part!

Tut, yes… what do I look like, an amateu… actually, scratch that.

But yeh, there’s a really stripped down CSS file in there, named “Print.css”… just pretty much takes out everything but the main content.

Looking into the website’s source code after putting each of those in would seem to show that they’re doing what they need to be doing, but unfortunately it’s not working when I go to print the page.

Do I need to change something else on the page? At the moment, the following bit of code is still intact in the header:
<style type="text/css" media="screen">@import url( <?php bloginfo('stylesheet_url'); ?> );
</style>

And I’ve been putting your suggested bits of code with the other <link rel=... coding that’s there.

So the whole thing looks like this:
<meta name="generator" content="WordPress <?php bloginfo('version'); ?>" /><!-- leave this for stats please -->

<style type="text/css" media="screen"> @import url( <?php bloginfo('stylesheet_url'); ?> );
</style>

<link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="<?php bloginfo('rss2_url'); ?>" />
<link rel="alternate" type="application/atom+xml" title="Atom 0.3" href="<?php bloginfo('atom_url'); ?>" />
<link rel="pingback" href="<?php bloginfo('pingback_url'); ?>" />

<link rel="stylesheet" href="<?php bloginfo('stylesheet_directory'); ?>/print.css" type="text/css" media="print" />

<?php wp_get_archives('type=monthly&format=link'); ?>
<?php wp_head(); ?>
</head>

But as I don’t really understand what the code is doing, I know I’m probably putting it in completely the wrong place, or not making some fundamental important change that’s needed. I’ve always relied on Dreamweaver to do the stylesheet attaching, I’m ashamed to admit.