Problem/Motivation

I installed Redis yesterday, and since I can now use this module, I finally got a chance to try it out. And it works perfectly, so thank you very much for creating and maintaining it @vaish :)

I did run into a small bump in the road ...
I usually install modules with composer require drupal/crawler_rate_limit. However, you may end up with the old version 2 with this method ...

I couldn't figure out why the module wasn't listed on the Status page, as expected ... it wasn't until I looked under "Extend" and saw "Crawler Rate Limit 2.0.0" and remembered seeing version 3 on the project page, that the penny dropped.

It's probably due to this line in composer.json: "prefer-stable": true,

Steps to reproduce

Install the module as you would any other module, and get the old version 2.

Proposed resolution

Tag version 2 as not supported, or version 3.1 as stable? Version 2 seems to be used by very few sites, by now:

Week		1.0.x	2.0.x	2.1.x	3.x	3.0.x	3.1.x	Total
Sep 21, 2025	3	26	0	0	149	1,941	2,119

Remaining tasks

User interface changes

API changes

Data model changes

Comments

ressa created an issue. See original summary.

ressa’s picture

ressa
he/him
commented
Issue summary: View changes
ressa’s picture

ressa
he/him
commented
Issue summary: View changes
vaish’s picture

vaish commented
Status: Active » Needs review

Thanks for pointing this out. Version 2 has been marked unsupported for a very long time. Instead, I created stable 3.1 release. I believe that should fix this issue.

ressa’s picture

ressa
he/him
commented
Status: Needs review » Reviewed & tested by the community

You're welcome @vaish, and thank you for making an incredible module. It reduced the Bot strain a lot, and the server CPU usage went down from averaging ~90% to ~12%.

And perfect with the new release, I now get the latest Version 3 with composer require drupal/crawler_rate_limit.

vaish’s picture

vaish commented
Status: Reviewed & tested by the community » Fixed

You're welcome @vaish, and thank you for making an incredible module. It reduced the Bot strain a lot, and the server CPU usage went down from averaging ~90% to ~12%.

Thanks, @ressa. Glad to hear that.

Marking this issue as fixed.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.