@R_J said:
I never knew what was the problem here, but if it has caused because a plugin and YAGA use the same event and the plugin should be executed before YAGA, then it wouldn't make sense to unregister YAGA from the plugin because when the plugin is executed, YAGA has already been there first, nor?
The event I hooked into is literally the first event fired in the start up process. Since Yaga doesn't hook into this event, no other Yaga events have been handled at this point.
Comments
The event I hooked into is literally the first event fired in the start up process. Since Yaga doesn't hook into this event, no other Yaga events have been handled at this point.
Still not a great idea.
Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.