I just pushed out a major update to LonelyCache. The main change is that the membership and user authentication model has been completely revamped. There should be minimal impacts to you, however if you are having issues logging into LonelyCache, please let me know. Some of the changes are:
As mentioned, the membership and authentication model LonelyCache uses has been replaced with a new one. This entailed a new database structure for storing and managing LonelyCache members accounts among other things. Every member should be migrated to the new model and should be able to log in as before. This was done mostly in preparation/anticipation of moving to a newer, more secure authentication/authorization mechanism with Geocaching HQ, plus I get to learn some new stuff
Links to LonelyCache will no longer need the ".aspx" and LonelyCache will no longer add that to a link. Including the ".aspx" will still work, so any bookmarks you have set up should still work, though you may want to update them.
This happened a bit ago, but LonelyCache is now using https instead of http. If you access LonelyCache with http, you will be redirected to https. Also, lonelycacheproject.com is being redirected to lonelycache.com. Again, I suggest updating any links you have saved though they should continue to work.
There were several small cosmetic changes made, though I haven't kept track of them all.
The scope of these changes was extensive, I literally updated hundreds of code files. I've tried to verify everything is working but I very well may have missed something. Please let me know of any issues you see with LonelyCache.
There were a few SNAFUs to deal with after the upgrade, but I hope they all are fixed now. Some were:
"Contact Us" email wasn't working, this is now corrected.
Password reset wasn't working, it is now. I should have mentioned above that the password reset mechanism has been improved so now a reset password is no longer sent across the internet to you.
Links from a geocacher's page to a region page were broken and are now fixed.
I should have also mentioned above that if a user gets locked out from too many failed log-in attempts, the lock will now expire after some time period. The user will no longer have to contact help to get his/her account unlocked.
It turns out the search mechanism wasn't working quite right either and is now fixed. Sorry about the hiccups, . I went through the event log since the site update was made and all logged issues have been corrected.
. I went through the event log since the site update was made and all logged issues have been corrected.
but no more 