Posted by Kaelten Feb 25, 2009 at 20:54 UTC
We've had a bug in the forum's login script that was accidently clearing emails from accounts. This would prevent people from receiving emails or any other notifications.
Also I've revamped several chunks of our dns records, reverse dns, and spf records.
This should help increase the reliability of receiving email in general.
Posted by Ackis Feb 24, 2009 at 18:33 UTC
All of the knowledge base articles have been reorganized to be nested. This will make them easier to browse, however some links in the articles themselves may not work anymore. We'll be fixing those up over the next little while.
Posted by Kaelten Feb 18, 2009 at 21:18 UTC
Just wanted to make sure all of our authors had a chance to signup to win the Reactor by Hardcore Computers we're giving away on curse.com.
I've signed up, but I'm probably not eligible :(
Anywho, signup here if you're interested.
Posted by Kaelten Feb 04, 2009 at 00:52 UTC
I know it's been a while since I posted my last status update for the project. I apologize for the silence, but we're nearing payday!
So now, after several months of intensive development I want to bring to you guys the first release candidate for the 2.1 line.
Well, almost everything! Well, almost.
What were the issues again?
Here is a brief recap of what I posted in my last announcement as some of the major issues.
* Ignoring manual deletions * Installing over addons * Downgrading addons * UI feedback failures * Poorly worded options and button text * Too much automation in some places, too little automation in others * Lack of features that are considered defacto standards * General reliability
Now let's talk about what we did about them.
What we did about them!
The UI has gone through some major overhauls. Hrm, how can I explain this......
The old client
The new client
There are more changes than can be seen in that screenshot, but I think it gives a rough idea.
Well we didn't get everything I talked about in the last message done. Here's the list. I've struck through things we've finished. Things that are works in progress I'm marking with italics.
We'll be finishing things up as soon as possible.
Changed Behaviors & Methods
The Mac Version
Do you want the good or the bad news first?
I'll start with the bad. It's not here.
The good news is, we're now actively getting it ready for it's first night out. I can't promise exactly when just yet, but Soon has never been so close. I hope to start leaking alphas out next week, but again I can promise nothing!
The one thing I don't think anyone can argue with is that this client is hands down superior to it's predecessor. There is not a doubt in my mind regarding that.
Is it perfect? Of course not. Are there bugs? Sadly, yes I'm sure there are. However, there was no way we could justify continuing to hold back this update and letting people continue to use the old version.
We're looking for feedback as we're getting ready to put this out there to all 700k+ users in the next few weeks. Please use the ticket tracker I'm going to link below to report any feedback. But please, try and see if the ticket already exists.
I also want to apologize to all you guys who've been struggling with the 184.108.40.206 client for so long. Support on it has been weak to non existent, I'm going to be keeping a tabs on things much much closer with the new client in order to ensure that the same backlog doesn't happen with this one.
So guys, last thing I'm going to tell you is how to get the new client. So make sure to check the link section below!
Posted by Ackis Jan 29, 2009 at 15:59 UTC
There were many e-mails sent out regarding projects which were marked as inactive.
These e-mails, in the format of:
We're sorry, your project, <Project Name> (http://wow.curseforge.com/projects/project-1234/), has been marked as inactive on CurseForge/WowAce.
Recently the site upgraded its project status component and as a result all projects which have been previously merged or deleted were marked as inactive again, causing the e-mail to be sent out. Your main projects have not been affected in any such way.
-Note from Kaelten: Yea guys, we apologize for the mixup. We've already patched the cronjob so that such a thing won't happen again. Also for those of you who have many projects that were marked as inactive last night sorry for the span :)