WowAce

This has been fixed.

Patch 5.0.4 introduced an annoying bug to deal with.

Blizzard accidentally declared "_" to be global, so if your addon uses "_" as a global it will cause the GlyphUI frame to not work.

It's an easy fix, instead of:

local class
_, class = UnitClass("player")

Just declare _ as a local variable:

local _, class
_, class = UnitClass("player")

or you can achieve it another way using the select method:

local class = select(2, UnitClass("player"))

Using local variable over global variables is good addon practice for a variety of reasons, some of which include speed of access, interactions with other addons/Blizzard UI, and just not polluting the global namespace.

Good news however is that this is already fixed on the beta and should be slated for patch 5.0.5.

Mikk wrote a nice little utility which helps find global leakage in your addons. You can get it from WowAce here.

Just wanted to give everyone a heads up that a new category has been added.

At this moment we don't have an icon for it, but it exists so you can go forth and use it! :D

Enjoy!

Hello everyone! Patch 4.3 is out today. The ToC for this patch is:

## ToC: 40300

One of the big UI changes is that divide by 0 no longer works. Specifically, Blizzard's Lua fork no longer silently handles division by zero; it throws a Lua error now.

Have fun hacking away at your addons and I hope 4.3 goes smoothly for you all!

Hello everybody!

It's BlizzCon 2011 time! This means that a lot of the staff/moderators are at it. If we don't get back to you right away with an issue please understand that it's because we are not in the office/able to and that we will get back to you as soon as possible!

Have a great day!

We're currently in the process of moving knowledge base articles and wiki's around. This means some links won't work until everything is transitioned.

Thank you for your patience.

The automated process which marked out-of-date projects as inactive after 90 days hasn't functioned in a very long time. It has been fixed, but with the un-intended side-effect of marking as inactive every World of Warcraft project which was released during patch 4.0.1 and 4.0.3 - clearly projects that are still compatible (mostly) and relevant during patch 4.0.6.

Kaelten has undertaken the effort of correcting this, and all erroneously affected projects should have their statuses restored.

Keep in mind that when patch 4.1.x hits the live servers that all projects released under the 4.0.x versions will be eligible for the 90-day inactivity rule.

Ackis Edit: If you're having trouble please take a look at: http://kb.curseforge.com/policy/abandoned-and-inactive-projects/#w-reclaiming-your-abandoned-or-inactive-project

Sorry for the mistake guys/gals.

Some of you may have seen this added last week. In the footer of the site, there's now something that says "Revision XXXX". Well folks, that's a recent changes log. You can see this by going to kb:Recent Changes. Now you can track what's been fixed or added to the site. Feel free to check it out!

Hello everybody! On behalf of everyone here at CurseForge and WowAce I wanted to wish you a very safe and merry Christmas!

And to Torhal, Happy Birthday today buddy!

Hopefully you all have your shopping done so you can sit around and relax today and enjoy the holidays.

Merry Christmas everyone!

The Shattering has happened. Now it's time to level up in the third expansion for WoW. I hope everyone has a fun release night!!!

We will continue to approve projects as soon as possible.

Hopefully the game servers will stay up. :D

Taken from the news report here

We're aware of an issue where random users will not be able to connect to either the Curse Client, Curse.com, and/or other Curse sites. This is a temporary problem that should go away by tomorrow, the 18th.

We do apologize for any inconveniences this has caused, but please do not submit client support tickets related to connection issues until after tomorrow, Thursday the 18th.

Thank you, The Curse Support Team

This does not seem to be affecting CurseForge, WowAce or SC2Mapster.

Stealing this from Merah:

You may need to clean your cache with: ipconfig /flushdns

If it does not help switch to Google's public DNS, they have new records.

>nslookup curse.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    curse.com
Address:  68.64.47.204

>nslookup www.curse.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    www.curse.com
Address:  68.64.47.204

dns1: 8.8.8.8
dns2: 8.8.4.4

Good day everyone.

There have been some issues with the packager over the past week or two. It's a known bug, and there's a known work around for now. The root cause of the problem is being investigated and will be fixed.

Thank you for your patience and understanding.

It's that time of the year, when that wonderful Blizzcon event is going on.

A bunch of Curse staff will be there (Kaelten, Ckknight) along with many addon authors.

So for those of you who are going (or have already left) have a safe and fun Blizzcon.

As everyone knows by now Wow's 4.0 patch hit the US yesterday, and now the EU servers are up as well.

I just wanted to remind everyone that the new TOC # is 40000, and that to get a new update out to the majority of your users with this you'll need to flag a new file as a Release build.

We're seeming to be pretty stable overall, which is great given how much has changed in the hosting situation in the last few weeks.

If you do have any issues please do make sure to report them, as this is probably one of the most stressful weeks we'll have on the whole network for sometime.

Hope everyone has a great rest of the patch day and enjoys the new 4.0 systems and content!

(I'm posting this on sc2mapster as well since it could affect the performance/stability for you guys as well)

If you are looking to update an abandoned or inactive project, please read CurseForge/WowAce Policy on Inactive and Abandoned Projects first.

Cool Links:

Interface files for 4.0

Wishing all of our Canadian friends (like me!) a Happy and Safe Thanksgiving. May you have a wonderful turkey coma. :)

As promised the system for requesting a Beta key is in place.

If you are an author on WowAce.com, order your key here.
If you are an author on CurseForge.com, order your key here.

We'll be getting keys out to people as soon as we can, and just a reminder you must be an active WoW author to receive one of these keys. We'll be manually verifying eligibility as well.

Note: if you see a message about and error when placing your order, please just try again.

UPDATE:

Quote from Kaelten's comment:

We'll be also tightening up our distribution policies.

Going forward, anyone who wants to sign up for a key must have a certain minimum threshold for the popularity of their addons in order to be approved. We'll be using the same metrics as we do for the rewards program for this, although you don't have to be signed up for the rewards program to be considered.

We are leaving it open to new users, however, by default you'll have to wait until your addon reaches the threshold of popularity before you're eligible. Also, at this point we're leaving the giveaway open to team members on addons, not just the manager.

UPDATE 7-22:

Quote from from Kaelten's comment:

I'm about to start sending out the new batch of keys. However, there is currently an issue were EU players cannot redeem them. We've been told that there is a fix coming soon. As soon as I receive word that these work for EU players I'll post another update here.

Update to the update: It turns out that at least some US players are _also_ having the issue redeeming keys. I'm going to keep handing them out though as I've been told that they should work in the near future.

Update 7-23:

Quote:

Please be aware that we are having issues with players being able to claim Cataclysm beta keys currently for all regions. We are looking into this issue and will hopefully have a better update before the end of our day today. If you have given keys out to anyone, please have them hold on to them. The keys are not the problem and it seems to be an issue within the battle.net system. We’ll let you all know once this issue is resolved.

So the keys are good, we just have to wait it out. Good thing being teased makes it all the better in the end... right?

Thanks for understanding guys, and have a good one.

Update 7-26:

Looks like the keys are working now. Enjoy the beta.