Hey guys, I'm running a site with an auctioning script installed but I'm having a major problem.

When I setup an auction, and add images, the images upload fine but when one views the auction, there's no images and if you look in the DB the auction number and the uploaded images number isn't the same e.g auction number #100023 should have image #100023 but seems to be generating incorrect image numbers for the images and the auction image is always 3 numbers ahead #100026 hence the fact that the images wont show.

I have no idea how to fix this.

I need help badly on how to solve this, could anyone assist?
If you have msn messenger and would like to help, please pm me, otherwise reply to this thread.

Thanks guys,

Shaun

find the code that generates the number for the image id and toss a - 3 in there.

Hi NullPointer, I have no clue where to find that though, thats why I requested help since my php knowledge is limited.

As stated before, I dont have much cash on hand but I am offering a php developer a position on my site to help maintain the site etc... and once it gets busy (and it will since there are charges for the service on the site) you will be paid for the work you do, I'm also discussing with two other people who actually want to invest in the site so payment (eventually) wont be a problem. I just need to get the site up and running properly first so that I can start with the SEO/ad campaigning.

Please guys, I really need help with this script.

Shaun

what script are you using?

Hi Hafio, its a phpprobid script bud.

I still need help with this guys, still nobody willing to lend and experienced hand?

You paid for phpprobid and they won't fix it or give you any support??
I don't know the software but -3 probably isn't the best answer you should be looking in the database tables for a sequencing number. Also there's more then one image it's got to be something other then one image number match what do the other images have?

If this is still an issue try cmod the cache folder to 777. It should work I had the same issue and support spotted the problem.