Hmm... Don't seem to be picking up all the routes - what am I doing wrong?

[barryanders]

Hmm... Don't seem to be picking up all the routes - what am I doing wrong?

It has been a while since I have worked on this so there are a few possibilities.

The most recent version may have a bug perhaps? I don't think it does, but it has been many months since I actually used it so I can't confirm for sure. Still, I doubt that this is the case. So let's troubleshoot...

It should crawl them all no problem. This is probably just a mistake in your question, but I noticed that you wrote bin/plugin generate when it should be bin/plugin blackhole generate.

There are a couple things that may be happening here. One is that I have never tested this on a URL with ports included (although this shouldn't matter).

Since you saw output, I'm sure this is obvious but just to clarify that by including -p blackhole, you are writing to a subdirectory called blackhole within the root folder of your Grav installation.

[RamblingRoss]

Thanks for the quick reply.

You are quite right, the invocation was written wrongly in the question - it should be "bin/plugin blackhole generate".

As guessed I was deliberately trying to write the output to a sub-directory called "blackhole".

I have now tried invoking with and without both port number and output path specification, but to no avail. The tool always seems to halt after generating eleven files.

No matter, its a great tool and I can script out suitable invocations for all the routes.

@RamblingRoss the specific 11 number is quite strange. It may have something to do with the simultaneous file count. I'll have to check this out when I have time. Sorry that it's not working as it should for you.

@RamblingRoss, thank you for your bug report. This is legit. I'm not sure what version this was implemented in, but I'm guessing it happened when I implemented the simultaneous limit feature. This needs to be fixed immediately so I will see what I can do.

@RamblingRoss I found the problem. It was a bug in RollingCurl. Will post the fix soon. I also found another bug while messing with this so again, thank you.