Add-On Releases - gItemStats - World of Warcraft Itemstats

What is it?
[hr]-[/hr]gItemStats is a modification for vBulletin which allows you to display popup World of Warcraft item information on your fourms.

See this thread for the continuation of this modification.

Check out my iGoogle homepage gadget for World of Warcraft item database searching.

[manub]

Waiting for wowhead support, lots of items like the Black Temple / Mount Hyjal gems can't be linked that way

[jaykresge]

Well, someone got WoWhead support working with Itemstats. Please keep in mind, this is Itemstats, not the gItemStats mod on this page. I have not yet tried this. I want to see if Gryphon plans to integrate this into a gItemStats update.

http://forums.eqdkp.com/index.php?showtopic=9342

[Gryphon]

I do not plan on making any modifications to this mod any time soon, with tooltip tools available from Thottbot and [S]Wowhead[/S] it makes this mod severe overkill (not that it wasn't before the tools became available). I have barely started rewriting the mod from the ground up which will trim out much of the fat and bugs.

[Newfarm]

Actually, I don't agree with this mod's function being surplussed; it might be more then what's needed now, but for all intents and purposes it's far, far faster and more user friendly to use [item]Stoppable Force[/item] then [item=123456]Stoppable force[/item].

That alone is priceless.

[Gryphon]

That is what I will provide again in the next version, however you do not need 50 files and slow page scraping to do it as the current Itemstats method uses, it can be hugely simplified and faster and with less bugs.

[Newfarm]

Oh yeah, I see that . As I posted earlier, I imagine all that's needed is for the updateitem script to pull the itemid off wowhead, store that in it's database for future use (as in, just the item_id field allready in the database), let wowhead's JS do, well, all the work while having the local script automagically generate the correct urls for the JS to parse .

Unfortunately it's just a whee bit outside my reach when it comes to modifying code so I can't really be of any help.

Just know that your efforts are valued by a lot of people and is well worth pursuing .

[rstan]

Worked fine for me up until last night when I upgraded to 1.03 from 1.02. Random items are not being found. Some have even went to not found that were already in the cache.

Fire-Cord of the Magus....not found
Bark-Gloves of Ancient Wisdom.....not found

Chestguard of the Vanquished Champion....updated to not not found when already in cache
i remember now i could only get tier items to show by using ala only...but now when i select ala only it cant find anything...hmmm
vb 3.6.8

[rstan]

ok there is a new ala file that is not included in this latest release...

/itemstats/includes/allakhazam.php

get from itemstats site

[sweede]

Originally Posted by Gryphon

That is what I will provide again in the next version, however you do not need 50 files and slow page scraping to do it as the current Itemstats method uses, it can be hugely simplified and faster and with less bugs.

I don't know how you missed it, but the package you install and upload doesnt require most of the php code from the /itemstats/ folder. Only the templates, some of the include files, js and css files.

I have already re-written the gItemStats to be far more "lean" to use than what is downloaded currently. I could probably get rid of a few more files if i had to and make them part of the functions_gitemstats.php file or even a vbulletin plugin.

Also, using the wowhead provided .js in your website doesnt let you cache the item code to your server making repeat visits MUCH MUCH faster.

(g)ItemStats isnt going to be replaced by any means.

[sweede]

Originally Posted by Newfarm

Oh yeah, I see that . As I posted earlier, I imagine all that's needed is for the updateitem script to pull the itemid off wowhead, store that in it's database for future use (as in, just the item_id field allready in the database), let wowhead's JS do, well, all the work while having the local script automagically generate the correct urls for the JS to parse .

Unfortunately it's just a whee bit outside my reach when it comes to modifying code so I can't really be of any help.

Just know that your efforts are valued by a lot of people and is well worth pursuing .

i could probably whip this up in like, 20 minutes...

it'll give me something to do tomorrow for sure.