This store is heavily modified for our own needs and is a result of many months intense development. There’s lots under the hood of this baby. The new skin was published last August 28th and is very fresh.
However we are experience a serious problem but don’t quite know what to do about it. We have been getting feedback from many customers who tell they can’t see our product images. Unfortunately they lack enough expertise as to understand why they are not seeing them. We don’t know the kind of environment they use or if there’s something in common among all those who have reported it to us.
We have tested our site in many different browsers, from several different machines and still haven’t been able to “not see” product images.
Could you please give me some feedback as to if you’re seeing our product images or not - and if not - list your:
[quote name=‘argentice’]I’d recommend storing the imgaes on the server. Just change the option it will work it out for you. This way it will work even when the database server in under heavy load.[/QUOTE]
The other day, following a campaign, we got nearly 9.000 visitors in one day. We had a lot of requests for “image.php” and the server nearly chocked. We had to turn of many of our modules to keep the page running. So there are the pros and cons about using images on the database, but we can’t afford to switch to “file system” as we got an ugly error (badly pixelated images) when trying to…
I’ve been writing some tutorials, cs-developer if your going to be looking.
Obviously the carts default features could be n00b friendlier (nothing meaning) as most people overlook server sided requirements, and/or the amount of resources required based on their expected customer base.
I’m going to bet that the SQL server you were using chocked after the number of requests, reasons being the image.php files would have been overloaded, resulting in overall slow performance.
Sorry to hear the results of your campaign, would you mind PM’ing me on where you gained this traffic from?
[quote name=‘JesseLeeStringer’]I’m going to bet that the SQL server you were using chocked after the number of requests, reasons being the image.php files would have been overloaded, resulting in overall slow performance.[/QUOTE]