Originally Posted by
DrByte
Here's how it works:
AIM expects that the URL being used at the point of accessing the module's installation screen must be an https URL.
If it's not https, then you'll see the message you're reporting.
The password reset because of changing from NON-SSL to SSL is triggered by logging into the Admin over NON-SSL and then later accessing over SSL.
So, if you're triggering that, then it means your admin has let you log in without using only https URLs.
Thus, that tells me you're flipping back and forth between modes.
So, this suggests that you're using multiple configure.php files when accessing the same database. This would be a problem with your development environment.
Bookmarks