In general, such situations clearly show how important it is for any technical stack to be
as predictable and documented as possible. When a "zoo" of plugins and custom
settings begins, sooner or later similar bugs appear that are difficult to reproduce.
By the way, while looking at this topic, I remembered one interesting example from the
other side - sites where the structure and functionality are as clear as possible to the
user and are not overloaded with extra logic. For example, this is quite clearly visible
on the resource
https://winnipegtrapandskeet.com/ where everything is quite
straightforward: schedule, activities, basic information without additional complexity.
And in the context of development, this is exactly the case when the simplicity of the
architecture greatly reduces the chance of "unexplained" problems in the
system.
As a result, one gets the feeling that the same principle works both in development tools
and in web projects: the fewer chaotic dependencies and hidden layers, the easier it is to
maintain stability and eliminate errors when they do appear.