Maximum number of posts per column

[stevejburge]

Just for safety on large sites, I think we should add a setting: "Maximum number of posts per column".

Maybe we set it to 50 at first.

We don't want 20,000 posts trying to load in the "Published" column of large sites.

[olatechpro]

For the record, 20,000 posts cannot be loaded, default is 200 for all @stevejburge

Also, we're making a single query for all posts then showing them under the right status, by your request for "Maximum number of posts per column", that shows we'll be making different post query for different status which shows at least Draft, Pending, Published, Scheduled will results in 4 different post queries on the page and more when using statuses plugin (by implication, this may result on slow page load especially sites with many posts due to many database requests for posts).

Do you think this is better than the usual single query with limit per result/page?

[stevejburge]

@olatechpro Thanks. I'm just trying to be cautious for sites that do have a large amounts of content. Do you think we'll be safe if the user does have 1000 published posts in the time frame and tries to access the Content Board?

[olatechpro]

@stevejburge Did you read my comment from the first line?

[stevejburge]

Sure, if it's already limited to 200, that's good enough for me

[olatechpro]

Also, I'm not against having results per page and it'll be implemented with https://github.com/publishpress/PublishPress-Planner/issues/1610, what I'm saying in essence is having Maximum number of posts per column instead will results in multiple query for all post status which I don't think is efficient.

So, we already limit it to 200 and when we implement pagination/infinite scroll, it can be a setting.

Right now, the setting is useless without pagination or more result scroll. @stevejburge

[stevejburge]

OK, thanks @olatechpro. Let's launch and see if there's any user feedback on this