Having an issue with a site recently upgraded from D5 to D6. The upgraded Secure Pages module was/is working fine (with previous settings from D5 module), but I need to make some changes, and trying to access .admin/build/securepages times out with a server error after a long while.

I disabled/enabled the module, but no luck there. Any ideas? Should I upgrade to 6.x-1.x-dev?

And, for a temporary workaround if necessary, where in the database can I directly add some pages for Secure Pages to ignore?

[ -- Not sure if this is related, but I'm suffering from the "slow administer page load" (about 45 seconds) in D6 that is well-documented elsewhere but still not resolved, to my knowledge. (I've disabled Update Status without effect.) --]

Thanks for any help!

Comments

IT Guy 3000’s picture

IT Guy 3000 commented

Resolved the http_request_fails issue and this issue remains. Any advice? I've located the field in the variable database where I can add some additional pages to ignore, but would still like to get back to the full SP admin settings page. Thanks.

IT Guy 3000’s picture

IT Guy 3000 commented
Category: support » bug

Any help here? Other issues noted above are resolved, but still can't access Secure Pages admin. Times out after 90 seconds with a FastCGI Error. Have increased the timeout limit without effect. Could this be an upgrade path bug? Thanks.

Gladiator76’s picture

Gladiator76 commented
Version: 6.x-1.8 » 7.x-1.x-dev

I'm having the same Issue, can't access the secure page settings;
Any way around it?
Where can i find the settings in the sql database?
Please help
Thanks

grendzy’s picture

grendzy commented
Category: bug » support

IT Guy 3000: It sounds to me like the timeout is caused by system_check_http_request. Drupal tries to request it's own front page to test the network connection. Failures here are usually the result of network or DNS problems. The core issue is #245990: HTTP request testing unreliable and may be undesirable.

Gladiator76: the settings page is admin/structure/securepages. In newer versions expect it to be moved: #1259196: Move settings page to admin/config/system/securepages.

core’s picture

core commented

I am having problems accessing Secure Pages administration on Drupal 7. Neither paths work /admin/structure/securepages or admin/config/system/securepages. As far as I can tell the module has a check mark by it but who knows if it is installed or not. I've had the same problem with some other modules too, like coder and Ubercart SSL, as well as credit card modules... the admin pages either aren't there or are not accessible.

http://drupal.org/node/1291728

I'm thinking about going backwards and installing Drupal 6 at this point.

core’s picture

core commented

My solution was to go back to Drupal 6. Secure Pages Module was not behaving perfectly but I got the site to a workable condition (using Ubercart). I ended up making the whole site HTTPS and forcing it there through .htaccess and settings.php - as I understand this also protects against "man-in-the-middle" attacks and the hosting company/server doesn't seem to mind - although I don't know if this effects SEO. Drupal 6 clicked together rather well so I hope it is supported for a good while longer.

I have to say, even though Drupal 7 is the official release, I don't think it is ready for prime time if you want to do a e-commerce site... at least with Ubercart (12-2-11). As a small-potatoes-freelancer this was painful for me as I had to go back and rework the site for Drupal 6, and explain the delay to my customer (and adjust my billing). I think it should be made more clear upfront** the status of development instead of finding out what modules don't work after you have most of the site built. More properly I think Drupal 6 should still be the official release for a while longer - the toothpick doesn't seem to come out of Drupal 7 cleanly as of yet. - just my opinion and one of the common practices about software release that I don't like... the premature official release with the users to discover the bugs.

I'm somewhat a newbe with Drupal (my first year with a handful of sites and my first e-commerce site), and did what most people would do and download the recommended release and start building from there. **My recommendation to those starting off building a site with Drupal is to build it backwards and decide what functionality and modules you will need in the end, and check (and read carefully) for bugs and incompatibilities - after you went through your checklist THEN download and install and build from there. This can take some time but will save time and frustration. This seems to be especially important of building e-commerce. Make sure you have items such as ssl, memory limits, and payment gateways checked off.

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Active » Closed (outdated)

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks