We have an installation of ez which we are upgrading from 1.9 -> 2.3
The previous installation used a app.pre_content_view_listener to preload all views with specific shared objects. This was/is configured in the main ezplatform.yml: Upgrade to 2.3 admin not loading: "No route found for "GET /admin""
After the upgrade, this listener is now affecting the backend. When I publish an object now we get errors due to this listener (we used the location service to fetch some content, which now does not play well with the admin).
To bypass this my immediate thought would be to make the said event listener site_access relative, or bundle relative opposed to global.
Is this possible and/or the correct approach for ez?