14 minutes ago, Adriano Faria said:

Wow, so there's another issue there as it is working. 😄

Are you going to release a patch or only next month with a new version?

@Stuart Silvester, this is working for me:

	public function _getEssentialCookieNames(): array
	{
		$appCookie = \IPS\Settings::i()->ntr_CookiePrefix . '_*';

		return array( $appCookie );
	}

It shouldn't?

You may not have the cookie consent mode fully enabled, currently it requires {cookies} and nothing else in the text box to activate, then you'll see two buttons.

That however isn't going to work on the cookies page if the prefix can be changed, it uses that key to load the language strings to explain the reason why the cookie exists.

We'll continue working on the issues we've got then evaluate how we're going to move forwards.

9 minutes ago, Stuart Silvester said:

That however isn't going to work on the cookies page if the prefix can be changed, it uses that key to load the language strings to explain the reason why the cookie exists.

So I'll have to make a "hard-coded" cookie prefix?

10 minutes ago, Stuart Silvester said:

You may not have the cookie consent mode fully enabled

And where do I enable it?

On 6/19/2023 at 5:01 PM, Stuart Silvester said:

That however isn't going to work on the cookies page if the prefix can be changed, it uses that key to load the language strings to explain the reason why the cookie exists.

So to confirm: I can't use it like that? From now on, I'll need to use a hard-coded prefix, right?

1 hour ago, Adriano Faria said:

So to confirm: I can't use it like that? From now on, I'll need to use a hard-coded prefix, right?

If you have a setting to change the cookie name, it will no longer load the language string explaining what the cookie is on the /cookies/ page