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 | Fri, 16 Oct 2009 16:28:59 | Changed milestone from None to 3.3 |
| sylvanaar | Mon, 28 Sep 2009 18:50:35 | Changed status from New to Accepted |
| SteadfastUK | Mon, 19 Jan 2009 16:01:10 | Create |
- 2 comments
- 2 comments
Facts
- Last updated on
- 16 Oct 2009
- Reported on
- 19 Jan 2009
- Status
- Accepted - Problem reproduced / Need acknowledged.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Milestone
- 3.3
- #2
Quagm1re Sun, 06 Sep 2009 21:38:12This 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:
Fixed line 1553 of ACP.lua:
:D
- #1
miko0001 Sat, 24 Jan 2009 23:16:36Same here.