Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Exact same issue as #2307779: Generating >50 nodes or >10 comments does not work (batches not processed), for the same reason: batch is again set, but not processed.
Adding a batch_process
line in ContentDevelGenerate::generateElements()
for the batch case :
- does insert the items in the
drupal_batch:<bid>:0
queue - does not expose the batch id
- if the batch id is passed to
drush batch-process
callbacks throw all kinds of bad argument errors
Comment | File | Size | Author |
---|---|---|---|
#14 | 2866990-14.patch | 2.92 KB | Oleksiy |
#12 | devel-generate-test-green.png | 166.16 KB | drugan |
Comments
Comment #2
JurriaanRoelofs CreditAttribution: JurriaanRoelofs commentedHaving the same problem. More than 50 nodes in drush genc = no nodes.
Comment #3
vakulrai CreditAttribution: vakulrai as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedI am using drupal v-8.3.4 and devel generate for nodes and content is working fine for me. The following command might work for you:-
1) drush generate-content n (where , n =number of contents you want to generate).
2) drush genc x y (where , x= number of contents you want to generate and y=number of comments per node you want).
Comment #4
vakulrai CreditAttribution: vakulrai as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedComment #5
fgmJust checked with 1.x-dev HEAD and the problem is still present.
vakulrai : did you try with strictly more than 50 nodes (eg 51) or strictly more than 10 comments (eg 11) ? The drush command says it performed the generation but it actually has not when you look at the content admin page.
Comment #6
vakulrai CreditAttribution: vakulrai as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedHi @fgm I forgot to add :-
The Devel Generate module, which comes with Devel, has some Drush commands built in to generate dummy content. If you haven't already installed the Devel module, you can install and enable it with Drush.
Please follow the steps before running the above commands .
1) drush dl devel
2) drush en devel -y
3) drush en devel_generate -y
4)drush generate-content 53
5)drush genc x y
Thanks.
Comment #7
vakulrai CreditAttribution: vakulrai as a volunteer and at gai Technologies Pvt Ltd for gai Technologies Pvt Ltd commentedComment #9
moshe weitzman CreditAttribution: moshe weitzman at Acquia commentedUse 'needs review' when a patch is posted.
Added a little code but still can't get drush batching to work (i.e. >50 nodes).
Comment #10
drugan CreditAttribution: drugan as a volunteer commentedI've encountered with the same issue while working on the Commerce Bulk Commerce Generate submodule's GenerateProducts (devel_generate) plugin. The whole reason is quite complex. If you have Drupal Commerce module installed you can try the
drush generate-products
command which implements the same functionality as in the patch. For now just Drush8 is tested. Let me know whether it works with your Drush9 install.Comment #12
drugan CreditAttribution: drugan as a volunteer commentedCan't reproduce test fail on my local install:
Comment #13
vegantriathleteComment #14
OleksiyThe test was OK on my local too.
Comment #15
andypostComment #16
vacho CreditAttribution: vacho at Skilld commentedThe patch #14 woks fine for me for drush command:
e.g:
Comment #17
andypostComment #19
moshe weitzman CreditAttribution: moshe weitzman commentedMerged. Sorry to everyone for the long delay here.
Comment #20
salvis@moshe:
Your commits aren't reflected on the front page — see #3017628-6: Commits are not showing on drupal user profile page.
Comment #21
moshe weitzman CreditAttribution: moshe weitzman commentedYeah, the block has 12 months ago for my name. Is that same issue as the one you linked to? The commits ARE associated with my d.o. user https://www.drupal.org/user/23/track/code
Comment #22
salvisMy guess is that you've changed either your Git email address or your d.o email address, and they're now out of sync.