spencersokol

Can you let me know what browser and OS you’re running. I’m working on some other things with this plugin, so I’ll try to get this in the next release as well.

I hope to have a chance to look into this tomorrow and have an update out by this weekend. The OP has sent me some great test cases. Thanks for that!

Hrm… I know what’s happening, but I can’t say why just yet. Can find out what comment 4600 is (and if it exists)? It should be in post 6643. I suppose it’s possible a comment was declared a winner and later deleted…

Hey, the plugin counts all comments in the WP db that aren’t trackbacks. As long as Disqus is set to keep it’s comments synced with WP, it should work. But you’re the second person since the plugins release to mention that there’s a comment counting problem, so I’d like to talk offline to get a few more details and try to reproduce this so I can fix it.

Does that sound doable?

Well, it’s not automagically ignoring anything that I can see. Without further testing, the only thing I can think of is the WP API call I’m making is only pulling approved comments, which would make sense. Unfortunately I don’t know if I’ll be able to look further into it this week and I’m out of town next week, but I’ll look into it then.

Sorry, I haven’t looked at the code today, but I think it’s automagically ignoring admin accounts, maybe. You’d think I would have written that in the docs, but probably not. I’ll check this weekend to see if that’s what it’s doing. If that’s the case I may think about letting the end user make that decision and simply let all comments be entries.

OK, I found the issue while testing another plugin I was working on. The issue was with the activation of the plugin not firing for a new installation on 3.0.1. It has been fixed in 1.0.2.

Let me know if you have any other questions.

I haven’t heard of any issues with this plugin not working with 3.0.1. Are you getting a specific error?

It looks like you’re probably running PHP4, given the placement of the error. This plugin requires PHP5.

That notice is at the top of the core plugin file, but not in the readme or the description of the plugin. I will add it there in the next version. I will also have the plugin die gracefully if the PHP5 requirement is not met.

While currently WP only requires PHP 4.3, you should check out this guide in the codex.

I will take a look at this tonight and see what the problem is. Thanks for notifying me.

In the meantime, can you find out what version of WordPress and what version of PHP you are running? Thanks again.

Or would it be best to just request a new plugin with the proper name?

Thanks in advance,
~spencer

One quick thing: when you include the sidebar and footer, you should make calls to get_sidebar() and get_footer(). I’m pretty sure (at least) get_footer() has additional functionality along side including the template file.

All of the parameters you can use in query_posts can be used in your WP_Query object. So you can add it to your $args array.

'category_name' => 'arts and culture'

You can use the parameters from query_posts in your WP_Query call. There are a number of category parameters there. You can pass in the category by name.

Codex: query_posts
Codex: WP_Query

Basically, I’m building a plugin. I want to use WP for all user management. However, I have data in other tables in the WP database that I want linked to specific users (i.e. the WP user id is a foreign key for some of these tables) and I don’t want users deleted who have data in these extra tables. I have an interface for users with a custom WP capability to manage this data from within the WP admin area.

So, basically, I need a way to stop WP from deleting a user if data exists in my external tables.

In my case, it doesn’t make sense to attribute this data to another user upon deletion of a user, nor does it make sense to simply delete the data associated with a given user.

Hopefully that helps explain it.