This post was from a user who has deleted their account.
The problem is definitely on our end, but it's not happening to all users so we're struggling a little bit to isolate it. We're working on it, I promise! =/
We're actually in progress on BOTH of these things. Stay tuned!
This is also part of a larger issue for us, as we've been trying to find ways to make it easier for users to contribute on the developer side as they do on the content side. In light of that we're trying to make alterations to our source code repository to give access permissions on a case by case basis, making it easier for volunteers to help us with particular pieces of code. Doing so may be more trouble than it's worth, but I'd rather build an architecture we can expand later rather than make one-time exceptions.The development team on our site is swamped—in a number of cases with OTHER Client issues—and we don't have any Mac-focussed devs on our team currently. We're not in a position to hire one right now, and we have a few volunteers lined up that we want to talk to about it, it's just a matter of getting our ducks in a row. Please be patient.
We've actually had a number of kindhearted volunteers ask to be involved on much more than the OS X client. The interest is such that, rather than just send someone the source code and say OMG FIX PLZ BEFORE THEY GET OUT THE PITCHFORKS, we'd rather set up a system by which we can assign or take away permissions from volunteers to help us on various parts of the site as they see fit. You can chalk this up to me being pretty... detail-oriented... about how people interact with our code. Beyond that, the OS X client was not developed by anyone on staff. It was developed by another volunteer whose job and life have gotten so busy that he's unable to pay it the attention it now needs. To give you an idea: The Windows Client (mostly supported by mystadio) eats up probably a quarter to half of mystadio's day trying to track down all the difference nuances with how it interacts with different Windows installs/anti-virus programs/firewalls/other random stuff on people's computers/phases of the moon. Finding a volunteer with the time and inclination to deal with all of that is not as easy as you might think. :)Regardless, we do have a few people in mind. We're hoping to get them started at looking at client code "soon".
I'm seeing alot of posts about the addon being fine etc etc... But when I installed the wowhead client, there was no addon installed to my addons folder? I searched the computer for anything with "wowhead" in it, but only came up with the client and a few .txt documents. No addon.Anywhere I can get the addon alone and manually install it? The installer seems to have failed me.Edit: Read back a few pages, seems I'm not alone. 1/2 the posts say the addon isn't getting installed at all (Including me), and 1/2 say the addon is working fine, but the client isn't.
Guys? can u please translate few last posts or make youtube "how to" video? ^^
I'm another who has the problem where the install package does not install the addon into my addon folder. Is there any place to manually get a copy of the addon itself? To the poster above who mentioned that file path might be a problem, my copy of WoW is installed to the default location (same location that is hardcoded into the client) so I don't think that's related in my case.