Closed (fixed)
Project:
Multistep (D7)
Version:
6.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Jul 2010 at 18:49 UTC
Updated:
3 Jan 2014 at 01:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
manuel.adanHi,
I got similar situation, but in my case I have not Autocomplete Widgets module installed. Autocomplete fields in any other step but the first return a 403, except for users with 'toggle multistep' permission enabled. I discovered that _multistep_get_current_step function does not determine the real current step in this case.
I patched it to be aware of autocomplete. Patch is attached, please, try it out, and check if it solves your problem as well.
Comment #2
mckeen_greg commentedThanks for the help with the above patch. I had a similar problem, but with FileField. Attached is the patch.
Comment #3
lotyrin commentedI seem to be getting this in dev.
Can we get the above two patches rolled together against dev?
Comment #4
scottatdrake commentedI can confirm that the patch in comment #1 fixes the 403 error when using a Node Reference field, but NOT when using the Autocomplete Widgets module. (That wasn't clear to me initially. )
Comment #5
vlad.k commentedCan't delete the comment, but information was wrong, sorry...
Comment #6
vkareh commentedThe patch in #2 was already part of dev.
I committed patch in #1 (for Nodereferences) and added support for the Autocomplete Widgets module. They are part of the dev snapshot now. Thanks all!