Recently my programmer modified the code in this site so that it is compatible with browsers being offended at displaying non-encrypted webpages. What this means is that instead of what used to be http://www.faunaclassifieds.com/forums/index.php, the site is now https://www.faunaclassifieds.com/forums/index.php
Some people may have gotten alerts from their browsers stating something to the effect that this site is not "secure". It really isn't a problem, since nothing of a really sensitive nature (credit card info, etc.) is handled directly via the code on this site, but I was told that this could possibly cause issues with search engines which may be more and more insistent upon SSL encrypted pages being required for inclusion in their databases.
Anyway, it may take a while before this change is recognized throughout all cached versions of the pages on the various servers between your device and my server, so if you get any odd results, I suggest that you simply manually use the encrypted version (https) and see if that doesn't clear up the problems you are experiencing.
If problems do crop up not resolved by this above simple "fix", let me know and I'll see if my programmer can come up with a solution. As always, any change to the code always has the opportunity to break something unexpected (which is why I don't make such changes unless it seems really necessary), so I wanted to give everyone a heads up about what is going on.
Some people may have gotten alerts from their browsers stating something to the effect that this site is not "secure". It really isn't a problem, since nothing of a really sensitive nature (credit card info, etc.) is handled directly via the code on this site, but I was told that this could possibly cause issues with search engines which may be more and more insistent upon SSL encrypted pages being required for inclusion in their databases.
Anyway, it may take a while before this change is recognized throughout all cached versions of the pages on the various servers between your device and my server, so if you get any odd results, I suggest that you simply manually use the encrypted version (https) and see if that doesn't clear up the problems you are experiencing.
If problems do crop up not resolved by this above simple "fix", let me know and I'll see if my programmer can come up with a solution. As always, any change to the code always has the opportunity to break something unexpected (which is why I don't make such changes unless it seems really necessary), so I wanted to give everyone a heads up about what is going on.