Version 2.1.0 is not available/mentioned at WordPress.org. As a result, Packagist doesn't know about the version bump either. Can this be updated please? Thanks much for this plugin!

Your WordPress.org plugin page says:

Last Updated: 1 year ago
Compatible up to: 4.7.10

When trying to install the plugin, I see this:

Warning: This plugin has not been tested with your current version of WordPress.

I currently use the latest WordPress version (4.9.6). Nevertheless, I installed the plugin and it works fine.

Maybe you could make some tests to confirm and thereafter update the info on the WordPress.org plugin page? That would give more credibility to that nice plugin.

WordPress 5.0 is scheduled to be released on November 19. The plugin needs to be tested against the new version to verify compatibility.

https://wordpress.org/support/topic/undefined-index-on-line-38/

^ Undefined index issue is still present topic closed 4 years ago

I only get this error when running WP_CLI commands. This is an interesting interaction as this notice will usually never bubble up. In fact with twenty-twenty-two installed, my CLI command executes correctly. The theme error handling in my case (Rareloop’s Lumberjack starter) appears to catch the errors from this plugin and interrupts execution.

[2022-09-07T00:38:32.149511+00:00] app.ERROR: ErrorException: Undefined index: QUERY_STRING in /app/wp-content/plugins/wp-force-lowercase-urls/wp-force-lowercase-urls.php:38
Stack trace:
#0 /app/wp-content/plugins/wp-force-lowercase-urls/wp-force-lowercase-urls.php(38): Rareloop\Lumberjack\Bootstrappers\RegisterExceptionHandler->handleError(8, 'Undefined index...', '/app/wp-content...', 38, Array)
#1 /app/wp-includes/class-wp-hook.php(307): WPForceLowercaseURLs::toLower('')
#2 /app/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#3 /app/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#4 /app/wp-settings.php(598): do_action('init')
#5 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('/app/wp-setting...')
#6 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress()
#7 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#8 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
#10 phar:///usr/local/bin/wp/php/boot-phar.php(11): include('phar:///usr/loc...')
#11 /usr/local/bin/wp(4): include('phar:///usr/loc...')
#12 {main}

When querystrings are appended it doesn't lowercase the URL.
So I tested:
Correct: https://example.com/Contact/ > https://example.com/contact/

Incorrect: https://example.com/Contact/?Test > https://example.com/Contact/?Test
I would've expected: https://example.com/contact/?Test

Version: 2.0.1

Nice to have

$params = $_SERVER['QUERY_STRING']; attempts to grab up the query string - but only would succeed if it exists. Ultimately, if $_SERVER['QUERY_STRING'], PHP just throws a notice, which clutters debugging logs with unnecessary entries.

It would be nice to simply have $params = @$_SERVER['QUERY_STRING']; to be graceful about it, in the simplest way.