tiszenkel

Wow, I completely forgot about this after eight months. I did solve the problem, and it was simple! All I did was attach the same action to the user_register hook.

Managed to get it working! Unfortunately, just calling the function didn’t do the trick, because I’m using a script that runs before plugins are loaded. So I had to use the code independent of the function:

if (wp_next_scheduled('postExpiratorExpire',array($post_id)) !== false) {
wp_clear_scheduled_hook('postExpiratorExpire',array($post_id)); //Remove any existing hooks
}

wp_schedule_single_event($expire_time,'postExpiratorExpire',array($post_id)); 

// Update Post Meta
update_post_meta($post_id, '_expiration-date', $expire_time);
update_post_meta($post_id, '_expiration-date-options', $opts);
update_post_meta($post_id, '_expiration-date-status','saved');

Thanks, Aaron! You’ve got a terrific plugin that’s going to provide some key functionality on a site I’m launching this weekend. This is just the last piece.

Bummer! Well, I have a once-a-day delete script ready to go, so that’s Plan B — just seemed like it would be redundant when I had Post Expirator installed.

Aha! I’d already tried the showcase and it didn’t really help much because it was mostly blogs and smaller sites than ours, but the VIP page is very helpful. Thanks!

Can Theme My Login handle inline error messages? I took a look at it a little while ago but I never installed it — it didn’t look like it could do anything the other plugins weren’t already doing. I’m using a combination of Cimy User Extra Fields (for the extra fields), Email Login (to allow login via email instead of username) and wp-auto-login (to log the user in automatically upon registration).

That’s an intriguing idea, but I’m wondering whether it would still cause a performance hit, because it’s the same server even though there are two installs. I just had another idea, though, that seems so simple I’m kicking myself for not thinking of it before (but isn’t that how it always works?): Two separate WP installs on two separate servers, but identical wp-config files, each pointing to the original database. I’m going to give that a try next, then maybe I’ll give your idea a go.

Thanks a lot for the suggestion!

Another update: I tried wp_create_category on a completely different WordPress install, on a different server owed by a different company, using the default theme with no plugins enabled, and it still didn’t work. I find it so strange that WordPress has this fully documented function that simply doesn’t work. Nothing about it being deprecated or anything. Google reveals that a few other people have had issues, too, but nobody has any real answers, and I can’t find any reports of anyone successfully using it, not recently, at least. It seems like this should be a pretty commonly used function, right?

Luckily, I was able to find an alternative: wp_insert_category.

$parent_term = term_exists( 'Parent Category', 'category' );
$parent_term_id = $parent_term['term_id'];
wp_insert_term(
  'Child Category', // the term
  'category', // the taxonomy
  array(
    'parent'=> $parent_term_id
  )
);

If anyone’s having the same issue I was, there’s your answer.

An update: wp_create_category fails even when I use it inside my theme. The plot thickens.

Yep, it was the version immediately preceding the current one — 2.1.3, I believe.

I managed to fix this problem. If you’re interested, here’s how I did it:

I created a new user with administrator rights. I logged in as that user and demoted my original account to subscriber status, then gave it administrator status again. Presto, it was back in the Post Author box. Finally, I logged back in under the old admin account and used it to delete the new admin account.

I still have no idea why this might have been happening in the first place.