I installed a bunch of plugins and then rebuilt the app. Now I am seeing this banner error: [Screen Shot 2022-09-09 at Friday, September 9, 2022 8.52 PM] I can play wack-a-mole by removing the plugin from the yml and then rebuilding but this is gonna take a while. I am wondering if there’s an easier way. I looked in the /logs but didn’t see anything good: [Screen Shot 2022-09-09 at Friday, September 9, 2022 8.57 PM] Should I look somewhere else for logs? These are the plugins I am trying out: [Screen Shot 2022-09-09 at Friday, September 9, 2022 9.00 PM]

You can look in the Javascript inspector in your browser, it will usually give you the ID of the errant theme component (not sure about plugins). You can also look in the logs for rails errors and infer who to blame by the path of the files mentioned in the error.

I played enable/disable wack-a-mole and found out it was the image gallery plugin. I’d be interested in a better way to track it down though.

Very good. I’ll look into these options. Thank you :blush:.

As a general rule unless your site hasn’t launched I would recommend you try new plugins on a staging copy beforehand. Official plugins (the ones with the green tick) are usually more trustworthy, disabling the third party stuff first is usually a safe bet.

Good point. I love test environments. I should do that sooner rather than later.

How to track down plugin errors

Product Support

pfaffman (Jay Pfaffman) September 11, 2022, 4:05am 7

And I’d generally recommend adding third party plugins one at a time.

Topic		Replies	Views
How to identify which plugin causes error Product Support	8	2102	March 1, 2017
Reporting which plugin has caused the error Feature	5	1315	July 10, 2017
Lots of errors in Logs Product Support	6	1026	May 21, 2019
New topic and reply not working Product Support	7	1977	December 18, 2016
Broken third party plugins can break logging? Bug	3	859	August 20, 2018

How to track down plugin errors

Related topics