Despite a nice long "D7 port" thread with lots of suggestions for getting around the core bugs, I no longer have a properly patched module since upgrading to the latest (Feb. 2012) -dev version. My first patch threw a bunch of failures; I didn't move on to the others.

Are the links in the highlighted box on the project page still correct? If not, what patches are the latest tested, working patches for D7 / SecurePages 1.x-dev?

CommentFileSizeAuthor
#3 errors.png13.22 KBm.e.

Comments

mrpeanut’s picture

mrpeanut commented

I am using 7.x-1.x-dev (2012-Feb-03) and successfully applied the 3 patches from those links (in the highlighted box) and changed settings.php as per those instructions. Everything is working fine for me.

Have you used the latest patches from those threads? (On a couple, I think there might be a few different patches.)

grendzy’s picture

grendzy commented
Status: Active » Fixed

Good idea. I've updated the 3 links on the project page to link to specific comments / patches for D7.

m.e.’s picture

m.e. commented
StatusFileSize
new errors.png13.22 KB

Thanks for that update, but my first patch* still fails. See screen capture below.

Just to be clear, I am on the Feb 3 2012 7.x-1.x-dev version of the module and I am attempting these patches as per your updated links:
1050746-POST-APOCALYPSE_0.patch*
471970_0.patch
961508-20.patch

I uploaded the patches to /sites/all/modules and my first command was
patch -p1 -i 1050746-POST-APOCALYPSE_0.patch

grendzy’s picture

grendzy commented

I wasn't able to reproduce that with http://drupal.org/files/1050746-POST-APOCALYPSE_0.patch.

The test bot has also marked it green so we can be confident that it applies to 7.x.

m.e.’s picture

m.e. commented

I'm on Drupal 7.12. (It was after upgrading to that version and to the latest -dev of this module that my session problems began.) Was your test on the same version of Drupal?

mrpeanut’s picture

mrpeanut commented

Yes, I'm on Drupal 7.12 as well.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

sansui’s picture

sansui commented
Status: Closed (fixed) » Active

I have same issue as m.e., exact same errors - did you resolve by updating core to dev version instead of 7.12?

sansui’s picture

sansui commented
Status: Active » Fixed

The patches did indeed work against current dev version, just coming back now to close this

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.