האם ניתן ליצור קבוצות של פוסטים עבור פוסטים רבים של WordPress? אולי SQL?

[Seal]

Thanks to all!

@jtbayly

The problem is that your wordpress site wouldn’t have the necessary information to display the proper links, number of comments, and so forth if you do it on the Discourse side.

I did not realize that there were db changes on both sides. Interesting. I am very familiar with the WP db. Too familiar I suppose. I often go to the db first when I should probably use other approaches.

@angus

It requires you to understand all of the data and metadata being stored on each instance.

Yes, I am such a db obsessed fool. I love db design and creation. But… I am not familiar with the Discourse db at all (yet). So…

@angus

Using the WP Discourse plugin has the additional benefit of logging already being setup for WP Discourse publishing, which means you’ll get detailed, post-specific information if any of the publications fail.

Ah yes… proper logging is a wonderful thing.

@angus

In terms of the script itself, you would use the WPDiscourse\DiscoursePublish method publish_post_after_save for each post, i.e. in a loop (with appropriate batching and sleep).

Yes, excellent. I will consider this the proper answer, as it is precisely what I needed.

However…

@Simon_Manning

If the Wordpress command line tools allow you to iterate the posts and save them in a way that triggers the Discourse plugin to create the topics as you want, that’s certainly what I would do. It’s probably not very efficient but for a one-time job, any overhead will cost less time than trying to find a “better” solution.

What I ended up doing was using the WP cli tool as follows

$wp post update 396 398 402 {several more here} --tags_input=discourse

Before this I retrieved a list of row ID’s from the wp_posts table that had post_status = ‘publish’ and post_type = post

I gave that list to the wp post command and it took about 500ms per row using a 4core server. If I specified more than 20 or so rows, Discourse would… ???.. but after that no more links would be made. So I fed it 20 at a time with a 30 second delay and worked on other projects.

So, that answer is a for-real hack, but for me (not yet having @angus answer), it was the most direct route.