Go to the line mentioned in the error and replace
While you're at it check if it's called in any more places and do the same replacement.
You can remove that huge list of addons now btw :)
- Curse Premium
Member for 14 years and 26 days
Last active Wed, Dec, 11 2019 06:57:10
- 0 Followers
- 894 Total Posts
- 0 Thanks
Oct 15, 2008Posted in: General AddOnsQuote from BremicThere is a posted update? The latest update I can find seems to have been flagged by one library getting updated, and the mod itself does not work.
Maybe he was referring toQuote from Dridzt
Edit: Temporary filefront link added
Oct 15, 2008Ackis Recipe List is broken on the current WotLK beta build as well as the 3.0.2 live build.Posted in: General AddOns
Laibcoms has opened a ticket about it.
I've added some more info and a quick and dirty hack to get ARL to work with minimal edits.
Oct 15, 2008A few occurrences ofPosted in: General AddOns
need to be replaced with
BankItems.lua lines: 3909, 3916, 4129
Oct 15, 2008Skillet 1.11 beta works fine for the most part.Posted in: General AddOns
It spams the default chat frame with some debug output when it scans new recipes for the first time but that's not a problem
Only real bug I could find was some leftover pre-3.0 widget code for scrollframes.
I've posted a ticket and fix for those errors.
Oct 14, 2008It's not ag_uf related.Posted in: AddOn HELP!
(in the sense that any addon that populates dropdowns can cause it)
It's a problem with Blizzard handling of dynamically populated dropdowns.
The first addon that tries to create more list entries than are already available in the game
causes the taint.
We were discussing this on wowinterface a while ago.
I don't remember the name of the author that dug up the reference to a very old bug,
that's still going strong.
I made a very simple addon to reproduce it, that does absolutely nothing
(except create a dropdown and populate it with some bogus entries).
It will cause action blocked errors when you try to set the focus
from the target frame dropdown even if it's the only mod running.
Oct 14, 2008I can vouch as far as to say that the link/file contains only lua and xml files.Posted in: General AddOns
(at the time I downloaded it anyway).
Also it seems that Kirkburn has been in touch with the package uploader.
Oct 14, 2008While waiting for ForteWarlock (only using cooldown + core from it for the amazing cooldown bar)Posted in: AddOn HELP!
to update for 3.0.2 I reverted to my archived age-old version of coolDown+IFrameManager.
Lo and behold it still works out of the box.
My hat's off to Shag, virtually unbreakable code across 2 major patches :p
Oct 13, 2008This list of updated mods will keep causing havoc.Posted in: Updaters
The problem is that the "release" site, curse.com is "updating" with any change to the underlying project.
Even if it's not one that causes the files on the "release" site to be updated.
We are not helping anyone by repeating the same useless information about how to configure the updater,
unless we want to send people running in circles "buying time" for fixes.
Follow that link I just posted and tell me which of those addons are actual updates for 3.0.2
and which are r4xxxx files from the old wowace svn.
90% of the file listing is garbage.
If CC pulls from the same sources it will keep breaking people's addons folders simple as that.
I'm sorry to say but that page might as well be taken down immediately.
The best service curse can do to its visitors at this moment with patch-day madness coming.
It's 10x times worse than anything files.wowace.com ever was.
Follow me as I click the currently top "updated" mod:
"Last Update: 1 hour, 3 minutes ago"
If I am a clueless user I might happily download r56825.19 that happens to be the "most recently updated" file.
If I was a frequent visitor of files.wowace.com I might remember that the wowace svn closed
down somewhere around the r89000 revision number so this looks fishy.
Idea: maybe the files from Curseforge just haven't updated yet!
(we're already in science fiction lands as no ordinary user will make such deductions).
Let's see how easy it is to visit the "back-end" to see what caused the update alert.
The only link on the mod page that takes you to the project pages is
"See tickets on Curseforge"
I have to follow that then on that page (that probably contains no tickets)
pick the Files tab then click on the topmost file to see this changelog
" r56825 | mok | 2007-12-10 19:11:02 -0500 (Mon, 10 Dec 2007) | 2 lines
M /trunk/item2phpBB/localization.lua item2phpBB:
- added portions of providing an allakhazaam link (to be continued.. eventually)"
and I still after all this detective work and 10 clicks have no f*cking clue why that mod is on the "updated" list.
While I fully understand and support all the reasons for the change...
Curse is a total mess atm.
In a very ironic twist of events, Curse - the public frontend
is only usable by addon developers and power users atm.
Every normal user has a good chance of fcking up their interface.
IMO: Find the parts that work and axe everything else until patch day madness is over.
Hide it under the carpet or whatever.. just take the non-working parts out of public view.
Oct 13, 2008As you'll notice from the package name I never finished going through and making sure it's 100% ok.Posted in: General AddOns
However I brought it to the point of getting no errors in solo play
(that is to say masterloot or other group functions are totally untested).
I will probably fiddle with all modules to make sure they work as I'm not interested in alternatives,
just wasn't a high priority until now.
- To post a comment, please login or register a new account.