corpodibacco

so nobody experiencing this?

This is a bug, because it also affects the pagination of the comments.

If I separate comments and pings, and apply pagination (two things you can do with WP 2.7), the pagination will still consider comments+pings, producing always one or two empty pages at the end.

Of course you’re right. And the functions you linked to are golden! At least for me who never studied any kind of programming language, and only navigates into PHP by sight.

Frettsy, thanks a million for this post… I wish I had read it before I released the latest revision 1.8.3 yesterday ??

in fact, you’re right! The help page is misleading. Thanks for pointing this out. Since I just released version 1.8.3 I will update the help page silently for the moment.

…but on the codex those are listed among the actions you can hook in plugins, here

When I use add_action('wp_update_post nothing happens.
There is a loop of infinite posts being created when I use add_action(wp_insert_post, while in other cases no additional posts seems to be created, but Apache crashes anyway.

As I said, save_post does what it is supposed to do (the post title is changed) but then Apache crashes (I am obviously talking about my local XAMPP Apache).

$my_array works fine, it is what wp_update-post does that isn’t clear to me…

anyway, in case you are interested: the first draft of my plugin is here. I welcome feedback! ??

using add_action ('init' finally worked with the first function! So thanks a million man.

anyway, problem: if I use ‘init’ the first function makes no distinction between publishing or editing. I wanted this function to happen only when the post is published.
But I guess this could be worked out by checking on other $_POST values such as ‘publish’ or ‘post_status’.

Yet, for the sake of exploring possibilities, the second function should be better for my case….
Making use of $id (I forgot to put $id in the example here like you noted but it was present in my code when I tested it) it could alter the title after $_POST and therefore be hooked into other actions other than ‘init’. My experiments:

it does not work with 'publish_post', 'wp_update_post' or 'init' itself.

strangely enough, 'save_post' seem to work but it causes Apache to crash down!

'wp_insert_post' creates a infinite series of empty posts titled ‘test’ until apache breaks down.

'edit_post' duplicates the post you’re editing ad libitum until apache breaks down!!

I guess I’ll work with the first… ??

What do you mean it doesn’t rotate? Does it always show the same quote? Is it the ajax loader? Do you use widgets or template tags? Have you installed other plugins in the meantime? more details please ??

Actually, your suggestion sounds right but it does not work for me. post_title is not changed upon publication. Do you think the filter should be added to some other function?

Also this

function for_example() {

  $my_post = array();
  $my_post['ID'] = $id;
  $my_post['post_title'] = 'test';

  // Update the post into the database
  wp_update_post( $my_post );
	return $id;
}
add_filter('publish_post', 'for_example');

doesn’t work. Still looking for help…

I think it would, but the following doesn’t work:

function for_example() {

     $_POST['post_title'] = 'test';

}
add_filter('publish_post', 'for_example');

That’s a weird behavior… The new version 1.8.2 gives you the ability to remove the “new quote” link, BUT, before you do, please try if also the new version gives you the same problem. It should be fixed.

Frettsy, you are absolutely right, a usual sloppy coding on my part. Your fix is perfect for custom permalinks except that it would not work if someone uses a traditional permalink with a ? already in place. But I’ll think about it: and it will be fixed in the next version.

Oh, no, not at all, I know what caused the problem. If you don’t deactivate the old and reactivate the new version, certain conversion operations cannot happen. Usually this is not an issue if you update automatically via wordpress. But if you just remove or overwrite the files, there can be problems at least with certain versions.

Have you deactivated the old version first? If not, try deactivating and reactivating.