Skip to Content
2-09-2009 @ 12:19PM
If you have already checked the big two sites (and made sure to read the comments for links to off-site fixes or fan updates), you can always try the old "change the .toc" method. Sometimes it works and sometimes it doesn't.Just open up the main .toc file in the addons folder with notepad, and at the top you'll see a short string "## Interface: 2xxxx" where the "x's" are the version number...you'll want to change that to whatever the newest patch version number is, which in this case would be "## Interface: 30000" (without the quotes). Then save the .toc file, overwriting the old one. Take a look in your other .toc files for addons you know are working, and verify that they are ## Interface: 30000, or in the future, whatever that string is, just change the broken addon to what the working ones have.This is a crude fix and it doesn't always work, but I've salvaged quite a few addons this way. Just depends on how much the API changed between patches.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.