A free extension like this survives only by reputation. You can help by submitting a review in the Joomla Extension Directory. Please take the time to make a review by clicking on the link below (opens in a new window)
I love your work on this (and I will write some goog reviews on your extensions!) I upgraded my plugin 3.7.x version to a 3.8.x.. the field to add a cookie decline access level appeared indeed. I did set it up as per the documentation.
However the whole plugin stopped functioning. The message appears allright but the module positions set to CookieAccept nor to CookieUnaccept just do not show whatever choice I make. I tried all 3.8 versions from the repository.
I reverted back to 3.7.14 to have at least CookieAccept level working again.
I don't see error messages in the log files anywhere.
Do I need to use the exact group and level naming as in the instructions?
If you can tell me where to look and what else information you would like to receive please let me know.
Exact group/level names are not required. The plugin looks for the levels you configure it to look for - and other than not selecting the built-in levels (public, registered, administrator) there isn't any kind of built in requirement for the accept/decline groups.
What version of Joomla did you install to? 3.8.4 and 3.8.5 are virtually identical - I added a polyfill to satisfy a missing piece in IE11 compatibility mode to 3.8.5.
blank screen is a scary error with no logs to give context.....I don't know what to do with that. Would it be possible to turn error reporting to maximum and run 3.8.5 once to see if it picks up anything?
I installed it on joomla 3.8.8
I tried 3.8.0, 1, 3, 4 and 5. 2 is missing in the repository.
It is not so much as a blank page as just the modules set to cookieAccept or cookieUnaccept are not showing either way..
There are no errors..
And it happens on all browsers I have: FF, Chrome, IE and Edge..
Can it be I need a full clean install of the plugin instead of updating it? (or install over it?)
I was just in a site that exhibited the same behavior you described and it looks like a perfect storm of access level IDs matching group IDs between the user manager config and global config. Basically, the plugin checked cookie access levels and they matched the public access levels and the plugin (correctly) refused to add or remove a user from the public access level. I'm feeding it more reliable data and it's behaving normally on the target system and my test server. I've got a working solution I need to finish testing and I'll roll out 3.9.1 when I'm finished.