WordPress MU

Even after installing plugins to avoid bot sploggers, we do get some manual sploggers coming and making their splogs.

I had thought of a plugin for it.

It maintains its own table to hold a record for each new blog that is created. Also when the blog is added to the table, the public field of the blog is marked 0 explicitly. What the owner wanted is backed up though.

Now, till the blog is removed from the table, the owner of the blog won't be able to mark it public.

In the Site Admin Page, it shows a list of all the blogs, with links to them and an option for each one to select Approve, Spam or Decide Later, to do the respective actions.

Approve just removes the entry for that blog and marks public either 0 or 1 according to what the owner had last tried to mark.

Spam removes the entry and marks the blog as spam. Then it doesnt matter whether it is marked public.

This can be helpful in a way that the latest posts and blogs won't appear on your homepage until you approve them to be public. Also they wouldn't appear on your sitewide feeds.

The problem is it is appending two line breaks in the sitewide feeds generated by it damager's sitewide feed plugin, and hence making it invalid.

I've posted the code of my plugin at http://www.miteshashar.com/wpmu.txt

Can someone please help me out with this one.

Why another table?

Why not just an option in their options table, and then an option (as an array) in the sitemeta table?

All ya need is an array of the blog_id's, and then if that option exists in the local table, the privacy setting can always be forced to remain private.

Then, the only way it's switched is from site admin.

Of course, then "most" spammers will catch on, and probably "pretend" to be nice. You make the change, they fill it up with spam. Adding a little more than usual to spite you for the hassle.

The best options are those that they can't tell are in place, and couldn't find if/what/when/where/how they are implemented.

it is a different table for easier retrieval from database during admin panel actions...

check out the line:

$pubblogs=$wpdb->get_results("SELECT blog_id from pubdenial",ARRAY_A);

also...regarding the spammers figuring it out...
the plugin wont let them know...
coz nothing is explicitly mentioned...
but it doesnt let the blog be marked public until it is approved...
and hence it wont appear on homepage...

I can't see yet another table being necessary when get_option and get_site_option for a simple 1/0 t/f y/n setting and an array of blog_id's is quite sufficient.

In terms of them figuring it out, they will. They'll notice they can't change their privacy setting, and eventually get the picture.

You'd be surprised how much information they'll pass back and forth about things like that. Eventually, they'll have had enough "people" do the deal to figure it out.

And yeah, it'll be on their home page. Right in the source, in the the head with a meta tag.

okkkkk....dint have an idea about that....newayz..
i will shift that to site options...
can u pls try n figure out why it is interfering with the sitefeed...wenever u get time...
meanwhile i will make the necessary changes to the plugin...will take some time though...got my xams close by... ;)

Thanks for saying please, but support for that plugin would fall to the author pretty much. Unfortunately, I'm not a "fix this code, that you didn't write, for free" kinda guy.

If a site is private, it shouldn't even be in the sitewide feed though.

oh dats fine lunabyte...
no probs...
i'll contact IT damager and try and figure out where my plugin is interfering with theirs....

this sounds like a really nice plugin (if it worked) where did you get it?

i am creating it...

oh, sorry about that, I understood that you purchased it and it was not open source when lunabyte said that falls into the hands of the author. Never mind me then.

That was referring to the sitewide feed.

OK...
solved the problem with my plugin ....
check this out...

http://mu.wordpress.org/forums/topic.php?id=6430&page&replies=7