NextGEN Hogged Server's Memory and Crashed Host's Server
-
I’ve had sooo many issues with NextGEN since the 2.0 update, and I’ve worked through them _all_ until NOW! This is the last straw, the straw that finally broke the camel’s back!
3.71 leached so much memory and other resources from my host’s server that it repeatedly crashed the server. It was so severe, that my host thought that my site was infected with malware, and shut down my site. They then charged me $100 to fix the problem (which they never did find – because they were looking for malware, when it was NextGEN), which I actually fixed by removing NextGEN! This is a Boy Scout website for a troop of boys from low-income families. They CAN’T AFFORD mistakes like this! This is money that they boys desperately for equipment. This is money that had been ear-marked for a new rain fly to replace one that was ruined in a bad storm they weathered.
I have written about the sloppy programming on our Troop’s website, explaining to the parents why their boys had to sell more outrageously expensive popcorn to pay for an expense brought upon them by the developers of this website. We have one of the most popular Scouting websites in the world, at https://troop501.net. If and when the developers make a financial contribution equal to the amount of money that was expended due to their sloppy coding, the post will be removed, and replaced with an acknowledgement. Until then, it will remain there, for everyone to see, world-wide.
I highly recommend that NO ONE use NextGEN Gallery, until these significant issues are resolved!
- The topic ‘NextGEN Hogged Server's Memory and Crashed Host's Server’ is closed to new replies.
