Unfortunatly not, because with the absence of a blue post stating otherwise, the same advice is the only solution offered on the official forums.
"They are looking into it" is all we are getting from blizzard so far on the issue, so that is currently all we have.

I'm back on this topic because it just pisses me off that my nameplates do not work correctly.

I have a question on that topic. Basically hooking wow widgets and the threat texture.

I'm hooking the SetVertexColor widget for the threat region of the nameplate. But the function does not fire at all. But if I update the frame via onUpdate and print out the vertexcolor applied to the threatregion via "print(threatRegion:GetVertexColor())" I can see that it changes if I gain or loose threat. Just the hook doesn't fire. :/

If I call SetVertexColor in the function myself the hook fires correctly. How the heck is this possible? Can the vertexcolor of a texture be changed without SetVertexColor beiing used? I don't want to create an onUpdate script just to track the threat status this is dumb. :/

The whole nameplate randomly hiding issue seems to be related to the new "spread nameplates" feature. I do believe this because there are the following console commands that can "fix" the oddly behaviour.

1) /console bloattest 1
2) /console spreadnameplates 0

If you only use #1 you will end up with literally bloated plates, but they hide/show correctly. If you also use #2, there won't be much of a difference. BUT when I did this:

/console bloattest 1
/console spreadnameplates 0
/console bloattest 0

Everything was working again, no bloated plates, hiding/showing correctly. However I had no time to "stress test" it.

Edit: It's broken again after a relog, though.... D'OH! It's possible to repeat the process on each login ...

Edit2: The behaviour seems completely erratic, after login/relog/zoning and repeating the procedure, mentioned above. Sometimes it works fine, most of the time it doesn't. -.-