[tuaguild]

Any questions about gitemstats come here. and ask me. Also Will Work on a version that uses MMODB support. It will be posted on a different thread.

[KURTZ]

what are the differences between your and THIS hack?

[Gryphon]

Originally Posted by KURTZ

what are the differences between your and THIS hack?

Different author, different code. Does there need to be any more of a difference?

[KURTZ]

Originally Posted by Gryphon

Different author, different code.

OK, but these hacks do the same things ... that's i'm wondering ...

[tuaguild]

They do the same thing but the tooltip popup is different and slightly transparent and also it parses a differant site for item cacheing plus it is easier to use with more features
Both parse wowhead but instead of parsing every time a page loads it saves the item info to the db and loads that item from there then on

[KURTZ]

Originally Posted by tuaguild

They do the same thing but the tooltip popup is different and slightly transparent and also it parses a differant site for item cacheing

OK thx, however i just tested yours, and i've found a little issue ... a missing image in the tool tip ... check the shot attached ...

PS. the other creates a new button into the editor ... can you provide us the same thing?

[tuaguild]

ok let me look into the code and i will post an update
Yes i gotta look at the code and i will add a button also the pictures not showing up go to your vb options and make sure the images are coming from wowhead.com if it doesnt work i will change the code to use an icon pack i provide with the product.

[KURTZ]

thx mate ... also can you provide something for the editor? (i mean a button)

[tuaguild]

working on that this is my first vb product so i am not really sure how to add a button to the WYSIWYG editor cause i havent ever done it i will do some research and get it done for you guys
Also if it says in vboptions it is getting the pics from wowhead and it still isnt working try reuploading all the files and reinstalling the product that is sometimes caused by ftp depreciation

[tuaguild]

fixed problem with icon images not showing up by enableing auto downloading of icons and using the cache set up on your server. Also Added a button to the editor toolbar you must change the permissions for itemstats/wowhead_icons/ to chmod 777 so it will save the icons to the server

[sweede]

While this does basicly nothing that different (except add a lot of additional files + waste to your vbulletin directory) , why are you replacing the default class_bbcode.php and class_bbcode_alt.php files ? That's just a bad idea to begin with.

Besides after looking through the code, your vbulletin_config.php file adds a define for the path to the itemstats folder (which should be in the init_start hook), and your other include , the vbulletin_itemstats.php file is completly empty (0-byte file).

Anyways, for the question above as to what the difference between gItemStats and my product?

Using wowheads powered by javascript does not add additional code to your site. the ItemStats mod adds a table to each for each item link that is created embeded into the item's A HREF tag. If you have a rather large item list (such as say your guild bank listing or even your own characters listing), you could increase the size of your page download by quite a bit.

Also, editing a post with an item in it using the WYSIWYG editor clobbers the item link.

[tuaguild]

if you use the provided class_bbcode.php and class_bbcode_alt.php it doesnt using those files fixes the editor problem with gitemstats and i prefer my code and the differance in speed is negligable plus i am more for guild sites that do not use a guild bank on the site plus yours has to use an outside js in order to show the tooltip mine is internal and if you require a large item cache it is much faster to use your own database for the files than to rely on wowhead every time it parses also i am working on an integration of wowroster from wowroster.net with vbulletin and that requires the original itemstats code

[tuaguild]

after looking into sweede's post I eliminated need for the vbulletin_config_itemstats.php and class_bbcode.php files. I also want to explain how i fixed the WYSIWYG editor problem. If you open your class_bbcode_alt.php file you find a line

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

after the var $unparsed_tags = array( line you just have to add
'item', right above thread. so it should look like this

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

[sweede]

nothing against any user, but eliminate the need to edit files.

look at my products wysiwyg_start hook for the right way to fix wysiwyg support