View Single Post
11/06/20, 11:09 AM   #4
Baertram
Super Moderator
 
Baertram's Avatar
WoWInterface Super Mod
AddOn Author - Click to view addons
Join Date: Mar 2014
Posts: 4,989
If LAM options change from OFF to ON this could be because there was a lua error and the whole addon code is broken after that.
If game vanilla UI settings do not change this could also be the same. But in most cases you get a lua error message somewhere, at least maybe already during addon loading before chat output is ready.
This can be viewed with the DebugLogViewer ingame then if you chnage it to show the bigger DebugLogViewer UI (not the small at the bottom right edge of your screen) and then switch ath the DebugLogViewer top left UI dropdown box to only see the current reloadui.
Scroll up in the logged texts and check for red lines or use the red filter button at the top of the UI to only show these.

You might need to go to the LAM settings of DebugLogViewer and enable the logging of the stack trace as well + debug and error and info messages. Then reloadui and check if you are able to see any error messages in the logs that had happened before the chat was ready for output and only occured in the log files then.
This way you might be able to even see the lines within an addon that cause the error message, like normally shown in the lua error popup message. Click the error message in the DebugLogViewer UI list and you'll see the total message (After enabling the stack traceback in the DLV LAM settings).
  Reply With Quote