Addon Control Panel

8 - Can't Protect the last addon in the list

What steps will reproduce the problem?

1. Select the "Default" sort order
2. Make sure you have several addons in your Interface directory
3. Try to mark the LAST addon in the displayed list (the last one you have before the Blizzard Addons are listed) as PROTECTED

What is the expected output? What do you see instead?

EXPECTED : I would expect to see a Star next to the addon to say it was protected. When exiting WoW and inspecting the ACP.lua I would expect to see the addon in the (unsorted) list of protected addons

ACTUAL : The addon can only be ticked but not protected. When exiting WoW and examining the ACP.lua the name of the addon is successfully added to the list of protected addons but since it is not actually locked, when clicking Disable All, it is unticked and the addon is not loaded during the next UI refresh.

What version of the product are you using?

3.0.10.15

Do you have an error log of what happened?

No errors are generated

User When Change
sylvanaar Oct 16, 2009 at 16:28 UTC Changed milestone from None to 3.3
sylvanaar Sep 28, 2009 at 18:50 UTC Changed status from New to Accepted
SteadfastUK Jan 19, 2009 at 16:01 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 3 comments
  • Avatar of spiralofhope spiralofhope Oct 28, 2011 at 21:30 UTC - 0 likes

    Looking at the code, this appears to still be outstanding for 3.3.16.

    Line 1783 and on, in ACP.lua:

    if addonIdx < origNumAddons and
        savedVar.ProtectedAddons[name] then
        setSecurity(securityIcon, 4)
        securityButton:Show()
        checkbox:Hide()
    else
    

    =>

    if addonIdx <= origNumAddons and
        savedVar.ProtectedAddons[name] then
        setSecurity(securityIcon, 4)
        securityButton:Show()
        checkbox:Hide()
    else
    
    Last edited Oct 28, 2011 by spiralofhope
  • Avatar of Quagm1re Quagm1re Sep 06, 2009 at 21:38 UTC - 0 likes

    This bug has been a long-standing occasional annoyance, so I just dug around in the code today and found the fix for it. Turns out that the fix involves adding just one character to line 1553 in ACP.lua.

    Current line 1553 of ACP.lua:

    if addonIdx < origNumAddons and
    

    Fixed line 1553 of ACP.lua:

    if addonIdx <= origNumAddons and
    

    :D

  • Avatar of miko0001 miko0001 Jan 24, 2009 at 23:16 UTC - 0 likes

    Same here.

  • 3 comments

Facts

Last updated
Mar 30, 2012
Reported
Jan 19, 2009
Status
Accepted - Problem reproduced / Need acknowledged.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
4
Milestone
3.3

Reported by

Possible assignees