You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that you shoud throw an error for each trigger_error found in a controller and a warning for each trigger_error found anywhere else and if an extension call trigger_error in a "Symfony Event" (i.e. KernelEvents::*) it should be denied
The text was updated successfully, but these errors were encountered:
Not yet at least. The official Pages and Boardrules extensions are using (sort of) controllers for our ACP pages, and we have found that in those cases we must still use trigger_error. Using the a symfony response is not available to our controllers in the ACP.
i think maybe wait until we can truly not use trigger_error anymore in the ACP.
I think that you shoud throw an error for each trigger_error found in a controller and a warning for each trigger_error found anywhere else and if an extension call trigger_error in a "Symfony Event" (i.e. KernelEvents::*) it should be denied
The text was updated successfully, but these errors were encountered: