When you use setblock "/setblock ~ ~-1 ~ minecraft:ladder there's a texture bug (shown below)
Linked issues
is duplicated by
Attachments
Comments

Still in 14w10b/c, Doesn't occur with that command: /setblock ~ ~ ~ minecraft:ladder 2
If the correct data value is set, then the issue will not happen, so you're basically stating that if the incorrect data value is set, the issue will happen. Not a bug.
TheMoogle: Except that if you don't specify the data value in your command, the right one should be selected.

Gary Closse : Why should the game change something the user has deliberately or implicitely (No data value = 0) specified ?
If you want to place a ladder, place it as block, the setblock command is clearly not intended for regular use from the command line.
Let users use damage values for their creations and let the blocks keep looking like their base counterparts.
Without damage values, what else do we have left?
This got fixed!
It's fixed? Is this in a snapshot? Still present on my trade villagers in 1.8.6 as of right now.
At least my example works without problems... I didn't tried it with other things!
Ah, yeah. As of right now if I have a villager with, say, Paper (DV of 5), and given names/descriptions/etc, the game only cares about DV (last I checked) and unless a DV was set, the NPC would just take any crafted paper with no name or lore... so DV let me make custom trade-ins players couldn't get unless performing tasks such as this. But ever since one particular snapshot it all turned pink and black and while it's still ... er, useable, it's completely weird looking.
Confirmed.
Does not occur, if the correct data value is set, see screenshots