When I try to activate your extension I've a fatal :

( ! ) Warning: require_once(/home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/vendor/autoload.php): failed to open stream: No such file or directory in /home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/plugin.php on line 59
Call Stack
#	Time	Memory	Function	Location
1	0.0002	369424	{main}( )	.../plugins.php:0
2	0.2076	14231576	plugin_sandbox_scrape( $plugin = 'kagg-fast-post-generator-old/plugin.php' )	.../plugins.php:192
3	0.2077	14231904	include_once( '/home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/plugin.php )	.../plugin.php:2288

( ! ) Fatal error: require_once(): Failed opening required '/home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/vendor/autoload.php' (include_path='.:/usr/share/php:/www/wp-content/pear') in /home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/plugin.php on line 59
Call Stack
#	Time	Memory	Function	Location
1	0.0002	369424	{main}( )	.../plugins.php:0
2	0.2076	14231576	plugin_sandbox_scrape( $plugin = 'kagg-fast-post-generator-old/plugin.php' )	.../plugins.php:192
3	0.2077	14231904	include_once( '/home/csn/Local Sites/wp59/app/public/wp-content/plugins/kagg-fast-post-generator-old/plugin.php )	.../plugin.php:2288

It seem that vendor/autoload.php does not exist

Thank you

I created a site, generated 100 posts, 20 users and 1000 comments. So everything was generated in December 2021 and December 2022.

Here is an example for comments:

All comments were generated either today, or a year ago on 2021/12/13.

Posts:

It would really nice if the posts/comments could be spread across the past year, for example.

When the plugin is activated for the first time, it will check for allow_local_infile setting is On.

On a page reload the warning is gone. This is causing couple problems:

1. Low experienced site owner may be confused because they could not remember the setting name if they want to send it to server/hosting tech support.
2. Someone might think they did perform the correct configuration and the warning isn't displayed any more because everything is ok (while it's still not ok)

Could we keep the warning visible until the mysqli.allow_local_infile is properly set up? It doesn't look redundant since the plugin could not operate normally before that at all.

Right now all the generated comments are for the users that exist on a site. It would be super handy if it was possible to allow comments generated by site visitors not users (so basically by logged out users). Maybe even define the % (so by setting 10% - this number of comments will be generated by logged in users, everything else - by logged-out users).

This query SHOW VARIABLES LIKE 'secure_file_priv' is run on every page inside the wp-admin area.

I think it makes more sense to run it only on the "KAGG Fast Post Generator" page.

This PR adds nested comments.

Nested comments could only be created if adding in steps. Every next step will consider existing comments as parent. If all comments are added within single step, there will be mo child comments.

Possible Drawbacks

With the current approach, generator will add 50% child comments with each new chunk. It is causing some problems:

Comments are not distributing equally to posts. With every new chunk, posts which already have comments will have higher chance to receive new comment (as child comment) then posts which doesn't have much comments yet. And this chance is growing with every new chunk.

It may cause the situation when some posts have thousands of comment and others don't have comments at all:

Test setup:

• Posts already in database 10000
• Generate 500000 comments (expecting to get about 500 comments per post)
• Chunk size 50000 (means 10 runs)

The result:

• Most commented post: 9800 comments
• Less commented post: 0 comments

Alternative design

To fix the distribution of comments, we may need make the NESTED_PERCENTAGE a variable thing, to reduce the percentage of child comments with every new step. Need to be discussed and more tests...

At least, in my case, it's more comfortable to have a current date in post_date, because right now I test a logic in my plugin that relies on post_date and even "today" value is enough.

If MySQL and PHP are in different Docker containers and have different uid/gid the MySQL one doesn't see a target CSV-file, because the file is created with 0600 permissions (in my case)