GetAddOnMetadata?
 

Anybody know what the deal is with GetAddOnMetadata?

Apparently it stopped working with the "X-" fields. I was actually using them a bit for various things, but now it looks like I may have to move all of that into my code.

http://www.wowpedia.org/Patch_5.0.1/API_changes

Right. Is that it? Have we lost all of our ability to use custom fields in the TOC altogether?

Nobody knows, as Blizzard has not addressed the issue. You -- like the rest of us -- will just have to wait and see if Blizzard fixes this bug, or tells us it's a bug but they won't fix it right now, or tells us it's an intended change, or tells us nothing and does nothing.

So we are ...
http://www.youtube.com/watch?v=DpnvS7kM4Fs

No. You just need to be patient. ;)

Are there some more infos about that?
Currently i am working on my interface, and it seems that things like ColorGradient and some other oUF parts are still not working if i used it via X-oUF into my toc file

The bug with X fields was fixed already. If you're having some problem with embedding oUF, it's likely a bug in your code, or a bug in oUF. Make sure you have the latest version from GitHub, and then post in the oUF forum with your code if you still have issues.

i found the error i had.
haste had changed the ColorGardient function into the oUF core files.

the old way i used some month was this:


the first value of the function was value X / value Y
the new function said this:


now i have to put in both variables into the function instead of one single variable.

That really belongs in the oUF forum; it has nothing to do with GetAddOnMetadata, and likely nobody looking for the information you're posting will ever look at this thread.