I was just about to post this SQL error myself. Ironically it errors out on my dev forum, but not my production one. very odd

Quote:

Warning: implode() [function.implode]: Bad arguments. in /profilestats.php on line 72

lol...i don't want to be damed to hell :eek:..i clicked install another great mod to my board thanks michelle.:up:

Awesome mod! :eek:
It is very useful for my site!
Installed! :D


:up::up::up:

Nice job! I had to install the $template_hook[navbar_quick_links_menu_pos3] in navbar to get it to show up in quick links, but it was no big deal. Works fine! Thanks...

Looks like this will be very popular, thanks for sharing, I will install this when I get home. thanks.

**Installed**
Works just peachy on 3.6.7

Thanks :)

Hi Lea,

another good hack...I just tried it: it gives me the same db error as the one above if I enable the "Show custom fields stats?" and put no value in the "Custom profile fields to display".

The other strange thing I noticed is that in the profilestats.php code, you refer to $vbulletin->options['eps_customfields'] in the code, but after importing the .xml, that field is called $vbulletin->options['eft_customfields'], is this ok for you?

I'll wait for the fixed version...and thanks again for another one...;)

Keep up the good work.

Yet another great mod.
*Enigma nominates Lea as coder of the month :p

Sorry for the delay, I really liked the movie and got carried away afterwards reading threads in its imdb message board (Its called "The Illusionist", watch it, it was really good)

Its not odd at all. Probably in the dev forum you do not have any custom fields, whereas in the production one you do. This error is caused when trying to fetch custom profile fields when none exist. Of course it will be fixed shortly.
I probably confused the prefixes with my previous mod (eft_ was for featured threads). I'll fix that as well, thanks a lot.

Oh boy, I really suck at debugging my mods :(:p

Thank you everyone!!! :):):):)