View Single Post
10/15/20, 05:02 AM   #5
Baertram
Super Moderator
 
Baertram's Avatar
WoWInterface Super Mod
AddOn Author - Click to view addons
Join Date: Mar 2014
Posts: 4,979
The problem is, like Votan also responded, that some addons contain subfolders (most of the time in a subfolder "libs") where older library versions are included and loaded hardcoded from the addon's txt file.
In the InventoryGridView.txt file there will be lines like /libs/LIbAddonMenu-2.0/LibAddonMenu-2.0.lua etc.
But this is an older approach of loading dependencies which makes updating libraries pretty hard and fail very often.

Removing the subfolders will keep the old txt file but the txt will not find the fodlers and files anymore and silently fail.
You can add
Code:
## DependsOn: LibAddonMenu-2.0
to this addon's txt file so that it will load the library from your AddOns folder (standalone installation, like an addon) which in most cases fixes the problem.

Another problem could be that the old versions of LAM2 still try to load the library via LibStub which now is obsolete.
First of all do the same like described above and then search in the addon files for "LibAddonMenu-2.0".
Replace any finding in the addons of e.g.
Code:
local LAM = LibStub("LibAddonMenu-2.0")
With:
Code:
local LAM = LibAddonMenu2
where the first part local LAM could be somethign else. The main part is the ending with LibStub("LibAddonMenu-2.0") -> LibAddonMenu2

These 2 fixes should fix the settings menu of your addons.
  Reply With Quote