Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After updating to 7.x-2.9 I have lost the ability to enable Secure Pages module and the Administration Menu (which is enabled) is not working at all. Needless to say, not having the Secure Pages module working is a major concern while running an ecommerce website. People need to see that https in the URL to feel that their information is secure during transfer! Also, I can not Clear all caches from the Performance page or even log in after logging out!
Comments
Comment #1
Infinitee CreditAttribution: Infinitee commentedI got secure Pages working by enabling it on my local copy and importing database but, I still can not log in as user 1. I tried looking at the system and user tables but nothing is displayed on local or production.
Comment #2
jsacksick CreditAttribution: jsacksick commentedSecure Pages is not shipped with Commerce Kickstart, you probably did something wrong during the update, did you follow the steps described here (http://www.drupalcommerce.org/commerce-kickstart-2/install).
Comment #3
Infinitee CreditAttribution: Infinitee commentedThanks,... had to delete everything except sites and re-install.
Comment #4
jsacksick CreditAttribution: jsacksick commentedYou shouldn't have to do that, there's nothing that has been done that could have caused this issue.
Comment #5
rickmanelius CreditAttribution: rickmanelius commentedI know I'm chiming in late to this issue, but given that SSL is one of the requirements for a commerce site, shouldn't secure pages be packaged?
Yes I know that all shared-management payment gateways are technically exempt from this (at least partially) because the card data is sent directly to the payment processor servers. But even locking down /user and /admin behind https would fall in line with best practices IMHO.
I can create a new thread if that would be more appropriate.
Comment #5.0
rickmanelius CreditAttribution: rickmanelius commentedAdded information.
Comment #6
VM CreditAttribution: VM commented#5 should be a feature request in its own issue.