Simon Dickson

Thanks @systmuk – good spot. I’ve updated the ‘translation’ of the link, to match the URL currently in use. It will find its way around the world in due course.

Glad you like the plugin!

Yes, you can hardcode the form into the theme. In fact, that’s how we would expect most people to use it. You can use a conventional WordPress template tag:

facetious( array(
   ...
));

or you might prefer to use:

do_action( 'facetious', array(
   ...
));

as this won’t cause a PHP error if the plugin should ever be deactivated.

One of the options you can specify in that array of arguments is id: that would allow you to target the Facetious form in CSS.

The widget has a class facetious_form, which you could use, perhaps in conjunction with an ID for the particular sidebar.

I can’t say I’ve tested this approach too thoroughly… but if you go to line 91 and change $current_blog->siteurl to get_site_url() it seems to work as expected.

Have a look at the plugin notes:
https://www.ads-software.com/extend/plugins/category-images-ii/other_notes/

It doesn’t try to force an image where it might not be wanted; you need to call the image via a template tag, ie coded into your theme files.

This has done the trick for most contexts, added into functions.php for the theme in question (where 3 is the category ID for the ‘secret’ category, obviously):

function catFilter($query) {
if (!(is_user_logged_in())) {
$query->set('cat','-3');
}
return $query;
}
add_filter('pre_get_posts','catFilter');

I’ll put if(is_user_logged_in()) at the top of single.php and page.php, to prevent direct access to the posts/pages in question.

Obviously that doesn’t cover us for absolutely everything; most of the rest I can live without.

At the moment, though, the better solution seems to be use Huddle or Basecamp: ‘properly’ secure, and optimised for the purpose. A seamless WP-based solution would be great, but $20-something/month is increasingly sounding like a small price to pay.

Glad it’s not just me. ?? Having diagnosed the problem fairly accurately, let’s hope it gives the guys enough to hunt down the problem. I’ve logged it on trac, but there’s been no further update since.

Quick update… this problem seems to be directly related to whether or not you’re logged in.

If I’m already logged into my own site, and I post a comment, I get the blank screen. But if I log out and try to comment as an outsider would, it works OK.

bump… I’m seeing the same problem.

As part of a custom theme idea, I’d like to use the ‘comments popup’ functionality, specifically using the ?comments_popup=(ID) option, to display comments and accept new ones via an iframe.

I have an old local installation of v2.1, and it’s working absolutely fine.

But I’ve tried several installations of 2.3.x, as well as v2.5RC1 and even wordpress.com, and none of them work.

As 5115 described, when you submit a comment, you get a blank screen back. The browser address box shows ‘wp-comments-post.php’.

(The comment doesn’t seem to be received properly; it certainly doesn’t show on the admin dashboard.)

Does this mean ‘comments_popup’ is now redundant functionality?

OK, found a solution for my own problem. Looks my hosting company had activated a ‘mod_security restriction’, so it wasn’t ever a WordPress thing. I’m not sure why the particular site in question was picked out, as other hosting accounts on the same provider weren’t affected. Still, the restriction has now been removed, and I’m able to add tags like there’s no tomorrow. And so begins a happy new 2008. ??

A couple of additional clues which might help:

If I go to an existing post which has formatting (including links) in it, and try to add new formatting, the new formatting is lost when I get thrown out to the homepage… but the prior formatting remains.

I’ve been able to add new tags manually, by going directly into the database via phpmyadmin (although that’s obviously not a sustainable way to work). If I then try to view or edit the posts I just edited manually, the formatting is present.

I’m suddenly having exactly the same problem on a site of my own, running on v2.3.1. As soon as I try to add any kind of additional HTML to a post – a link, or even something as simple as bold formatting – I lose the ability to publish.

The formatting seems to go into the editor OK: for example, if I add a link, it shows up as underlined in the WYSIWYG editor, and I can see the appropriate a href code in Code view. I’m able to save as a draft. But when I hit Publish (or even ‘Save and continue editing’), it throws me out to the site homepage, and the changes are lost.

*Desperate* for some help on this one; this is a serious glitch. A site with no formatting possible in posts, isn’t much of a site at all.