Thanks for being patient with all of this folks.
I just added version 1.2.0 which removes the fsocketopen checks as it was really behaving badly and not providing the type of connectivity testing I wanted performed. Instead of timing out if the armory was not responsive, it turns out that the armory url was responsive but sometimes not returning results for up to 10 minutes! So, fsocketopen would not close the socket. I tried using a cURL method and also a socket_timeout method but both still had unexpected results. Therefore, I removed that bit of code altogether.
I kept the bit of code that checks to make sure that $cclass is not returning empty and if not, it continues on with the process. If it comes up empty it should not overwrite data into the armorydata table. I also adjusted a couple of other minor code tweaks but overall, it should perform better.
So, for all those that I replied to earlier, you can still read my suggestions on optimizing your site, etc. but I would upgrade to 1.2.0 and have it fix the problems you encountered with 1.1.9.
thanks everyone.
|