When I try to activate the extension `wacon_cookie_management`, I get the following error message:

When I try to activate the extension `wacon_cookie_management`, I get the following error message:

When I try to activate the extension `wacon_cookie_management`, I get the following error message:

When I try to activate the extension `wacon_cookie_management`, I get the following error message:

I am using the route enhancers given here https://docs.typo3.org/p/derhansen/sf_event_mgt/7.5/en-us/ForAdministrators/Configuration/RouteEnhancers/Index.html for my integration of the extension “Event Management and Registration (sf_event_mgt)” from Torben Hansen. The extension is great but I do not get the routing with speaking URLs working (everything works fine without the route enhancers).

I have an issue with my custom hook. I created a new hook and declare it in ext_localconf.php file. When I perform action to delete file from the filelist, I need to call in my hook method processCmdmap_deleteAction(). It doesn’t work now, because my file has been deleted without perform my method where I want to delete my other records. I’m sure this issue is related with this method processCmdmap_deleteAction and my hook (db table and structure is configured properly).
Do you have any idea, why Typo3 can’t run my custom hook and mentioned method when I delete record from the filelist page in the backend side of Typo3 instance?

I have an issue with correct rendering views in Typo3 (backend extension) after upgrade from version 12 to 13.
In changelog I see information about deleted deprecated methods and potential new way to render views – class ModuleTemplate can be used to render correct response (source: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-96730-SimplifiedExtbackendModuleTemplateAPI.html). I use it in my controllers, but unfortunately views are rendered without included Typo3 module layout (Module.html). This leads to issues with basic styling and scrollbar: the scrollbar itself is missing and content is not accessible on the backend as it’s not possible to scroll down or up.