iTrader version 2.5.0, new generation now released

As announced last month, here we are today with the launch of the next generation of iTrader, version 2.5.0.

The tradition continue, we’re proud to announce that vbEnhancer is now the official host of iTrader, with a new structure, more addons and a cleaner code for the future versions.

This is just an update, because for 2.5.0 we were focussing in centralizing all the existing addons for the old 2.1 version, and we made it clear that it would be easier with a smooth update for the existing clients and an easy spleen for the new players.

So, what do we get in the box?

All the files are now cleaned and easier to debug, here is the setting page in the vBulletin Options:

itrader_options.jpg

  • Gio~logist’s Main Page is now integrated fully

itrader_main.jpg

  • A new Profile Tab

memberinfo_tab.jpg

  • Completely and only compatible with vBulletin 3.8 generation
  • Refurbished templates, with new icons for ranking (positive, negative, neutral)
  • Option in your Profile Settings so you can show that you are selling/buying something
  • Force display of iTrader infos in specific forums
  • Display of iTrader Feedback Score in postbit

The thumbnail attached shows the extensive list of settings you can manage thru the regular path. as you can see, some new features have settings in the bottom of that page, they are good to look at.

And here is the form you see when you submit a new feedback regarding one of the transaction you’ve been involved in.

submit_feedback.jpg

all without any template or file edit…

You want to upgrade, or install as new?

Easy, if you have not used any of the addons released on vBulletin.org, you simply have to upload all the new files, overwriting the old ones, and uploadthe product file, allow overwriting the product, so it upgrade to the latest.

If you have used any addon that required template edits, like the old version of Giologist Profile block or his Main Page, or if you used MagnetiCat’s Profile Tab, you will need to uninstall these first, and hopefully, we provide all these versions in the Jason’s iTrader Archive forum on top of this… (just follow the opposite of the instructions!)

So, that’s it… there is not much new instructions, as now the entire engine is self documented… you can always post a question in this forum, so you are answered as soon as needed… but also, what’s fun, is that we ask for your requests, suggestions, needs; because we want to make the engine even better for the next version, which will jump to number 3.0 …

Browse vbEnhancer.com to see how iTrader interact… and click « installed »…

Oh, forget the last one… rofl!

Fixes:
1- no version change, but fixed Forums Where Feedback Score is shown, thanks to breakpoint for reporting bug!
2- no version change, but fixed a database error when submiting feedback, thanks to gronph for reporting bug!
3- no version change, but fixed a typo that was causing to display no link in the postbit and no % of rating. you have to re-import the product file, nothing else!
4- no version change, but fixed a database error when submiting negative feedback, thanks to breakpoint for reporting bug! (was reported 3 times more, but never had the error, so was unable to fix!)
5- no version change, fixed an existing array_merge that was making CMPS unhappy… thanks to
gnatster for reporting it!
6- no version change, fixed a missing « escape_string » when submitting in a form… thanks to all who have reported it!
7- september 4th, 2009, update of the product file to avoid the overpassing process of step 2.5.0

8- same date, adding postbit location of feedback score.

9- september 19th, 2009. Modified the install script so it does not avoid the creation of missing fields anymore — sorry, i first given the job to someone who was proven stupid after all…
10- sept. 22th, 2009. continued to edit the install process so it makes less error in dB modifs… i hope it ends the problems…
11- oct. 13th 2009, corrected some little typos

Laisser un commentaire

Votre adresse e-mail ne sera pas publiée. Les champs obligatoires sont indiqués avec *