You should not enforce strict standards on production machines.

I only did it temporarily (<30 seconds) to see if I could find the error that was causing the problems I was encountering.

I've resorted to a workaround that seems to work: setting participant_id to NULL in to tokens table.

Not sure if anyone can replicate this or if it is a problem only I have encountered (logging it here in case others encounter it).

Description looks similar to 07278 except that this issue (08410) also includes a participant_id value.

You wrote 'it fails on the last step.' How does it exactly fail?

Sorry - should have been clearer. In production mode, it fails in two ways:
1) The completion page is blank
2) The data, at least from the last step, isn't saved

When I make the participant_id null in the tokens table, both these issues go away and things work normally.

I see - Although it is also a kink in the source code the basic problem is still that your PHP is configured to strict standards (it does not matter if debug is on or off). PHP recommends to not show use STRICT error level on production machines.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13517

Fix committed to 2.05 branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13518

Great - I just implemented the code on my current version and it seems to work with both the scenario where participant_id exists in the token table and where it is null.

As for the the php strict error level, I'll investigate how to reduce it. I hadn't set it explicitly to anything but will now look to take it off strict.

Version 2.00+ Build 131202 released