it should be fixed for real this time :)

for some reason i had marked the method getHTTP as a private class, meaning you can't call it directly (i.e. $obj = new wowhead_item(); $x = $obj->getHTTP() ).

I thought i fixed that like.. 3 versions ago but thats what i get for working until 6am 3-4 days week :(

Great making that method public fixed my problems!

Thanks for checking on this sweede!

I've gotten some questions if it would be possible to get spell-id's also working as a mouseover like the item-id's

Any news on the Wotlk.wowhead.com haxxor ? ;p

hmz - I have a problem when trying to link items;

linking items with just;
http://www.wowhead.com/?item=34185
for eksample works.

But using
[item]Sword Breaker's Bulwark[/item]
Does not work;
here's what a url shows when i try mouseover after posting with the [item] codes;
http://www.wowhead.com/?item={option}

Any idea what's wrong?

(oh and if i try and edit the post - the links will not work anymore, as they stand as html in the edit window, and not as or http://www.wowhead.com/?item=34185

Hi Sweede, this is awesome - thank you so much! Much easier to install than itemstats and way less code. Brilliant!

Absolutely brilliant addon. I'm looking around for spell mouseovers atm. It would be great if we could get this addon to do it.

Works like a charm thanks

Causes:
In pages with a lot of <item></item> links (takes longer the more there are until it gives that error). I tried about 450-500 tags to get that error.


Any ideas on how to optimize?

umm.. don't make a single post with 450-500 items ?

Each item is looked up in your local cache for the item ID (wowhead requires item ID to create the tooltip).

If it is not found, it will make a request to wowhead.com (example; http://www.wowhead.com/?item=Netherweave&xml ) to get the XML data w/the item ID.

I cache most of the information in the XML for future use.

vbulletin then creates the item link that the wowheads power.js will process.


The largest time spent is the http request to wowhead.com. if each request took just 1/10th of a second, 450 requests would still take 45s or longer, since each request is sequential.