I've added the note about positioned parameters to sources.php.dist.

Acutally, I think the issue this was referring to only occured with 
the positioned params, so never mind ;)



Guess we can close this then with a note in the sources.php file?



But i'm still getting some strange behaviour with lists...will 
investigate more.

Yea, that's what i was hoping and why I posted that 'just to clarify' 
post, as a kind of hint in that direction ;)

I don't follow this part.
Yeah. Not as pretty as I'd hoped.

Hmm. I'd forgotten about the updatefield action. I can't see how that 
would work with positioned parameters already. So maybe the answer is 
that positioned parameters simply aren't supported here?

Just to clarify:

The existing code works fine as long as we don't use positioned 
parameters in the format string -' %2$s %1$s' for example.  With just 
' %s %s'  every thing is fine, but we need to put the field we are 
using to store the contact list name first in the 'fields' array...and 
off the top of my head, even if we were able to use a regex, we'd 
still have to "manually" ensure the correct ordering of the fields in 
the fields array, no?

Doesn't look like it's going to be that easy (of course).

1) We use the 'format' string in other places (as parameters to 
vsprintf for example)

2) The format string is also used in Horde_Form_Action_updatefield, 
which specifically explodes the string on '%s' ... and we can't change 
this without breaking bc.

Sounds good.

Does anyone see a problem with changing the 'format' parameter from a 
printf format string to a regexp? That seems to be the simplest thing 
to me, and probably allows much more flexible fields as well.

FYI



http://bugs.php.net/bug.php?id=42107

Due to a bug in PHP (both 4 and 5) we need to change the sscanf() call 
in Turba_Driver::toDriverKeys to some other inplementation.



The bug causes problems when using positioned parameters in the format 
string (inserts extra array elements in the results as well as 
confusing the order of the results in some cases) thus causing the 
composite fields to break....and possibly preventing the creation of 
new contact lists.



Example:



$test = sscanf('hello world, '%2$s %1$s');

print_r($test);



produces:



Array

(

     [0] =>

     [1] =>

     [3] => hello

     [2] => world

)