yep yep, that would correct

is there any way we can pull from wowhead as the item site? It is so much faster and cleaner than thott/alaka-spam

No there is not, Itemstats was created by someone else and these are the sites he has coded for and it appears that he will no longer be updating the parser. I might look into doing it myself, but I don't personally use Wowhead.

This is a great product. I've installed it, and found it to be a major upgrade over the previous ItemStats (especially with no file editing).

Recently, someone else overcame the WYSIWYG "oddness" (the item tagged text appears as a hyperlink to the Allakhazam or Thottbot material) by simply having it always reverse transcripted to |item|itemname|/item|. Is there a way that could be done here so that compatibility with the WYGIWYG editor can be ensured?

Thanks!

Yeah I think I saw that on another addon as well. I was going to take a look and see how they did it, I just have not had time to look it up yet. I hope to have a fix for that soon.

Im getting this error message on any forum i visit with this installed...

I absolutely love this for the WoW site I admin, what I wouldn't give to see one for my EQ2 site. Thanks again for this great mod!

This sort of works for me.

The popup works, with sockets, but the item icon wont display.

When I make a post with like, 200 itens on it (bank parses), it crashes the thread. It may seem odd that someone would post 200 itens, but its perfect for guildbanks to post their contents. I did make the parsing mod merge all stacks to reduce the amount of iten links, but still we will get 200 iten links sometimes and it'll crash the thread, and I have to disable the ItemStats mod, post 100 itens, load it, then post more 100 in another post, reload it, then it'll work.

Any advice for this problem? (besides telling the guildbanks to not be such packrats hehe)

Have you tried setting the gItemStats config to parse the Item information upon clicking, rather than upon rendering the thread? Not sure if the crashing is a database error or, more appropriately, a JavaScript error, but that might help debug it.