500 Internal Server Error due to dash in cookie consent route prefix

[captainscorch]

Issue Description

The default configuration for the cookie consent url/route prefix includes a dash character, which causes a 500 Internal Server Error when trying to load the cookie consent script, which then causes the buttons to not work anymore, making the consent banner unusable.

Current Behavior

When attempting to load the cookie consent script, the following error occurs:

GET http://localhost:8008/cookie-consent/script?id=XXXXXX net::ERR_ABORTED 500 (Internal Server Error)

When attempting to click on the buttons, the following error occurs:

Uncaught TypeError: Cannot read properties of undefined (reading 'acceptEssentials')

Expected Behavior

The cookie consent script should load without any errors and the buttons should not throw an error and close the consent banner after the action.

Steps to Reproduce

1. Install the package with default configuration
2. Attempt to load a page that includes the cookie consent script

Proposed Fix

Change the default prefix in config/cookieconsent.php from:

'prefix' => 'cookie-consent',

to:

'prefix' => 'cookieconsent',

Additional Context

This issue affects the default configuration. Users who have published and modified their configuration may not experience this problem if they've already changed the prefix.

Environment

• Laravel Version: 11
• PHP Version: 8.3
• Package Version: ^1.2

[toonvandenbos]

Dashes should not cause any problems in slugs. I think you have something else going on. Did you have a look at the details of the error?

[captainscorch]

This was the only error I got, everything else worked fine. No other warnings either. In Laravel 10 with an older project this issue did not arise, so maybe it's related to some change in Laravel 11, either way the above change fixed it in my case. You are right, the slug shouldn't cause any issues, but for some reason it solved the issue.

[toonvandenbos]

Thanks for your response, @captainscorch. I'm not able to reproduce this issue on a L11 installation either, so if you could still post your full error log here maybe we can have a better look at the issue. Thanks!

[captainscorch]

@toonvandenbos thanks for pushing on this, I did some more testing locally and was able to fix the issue without the slug change, it was an issue related to my local Vue / Inertia codebase, totally unrelated to the package.

I verified this on a new Laravel 11 installation as well.

I will close this Issue now, thanks again!