sorry, this should have been a bug report.
I'm not allowed to change it, am I?

What plugin are you using?

The 'Example'-plugin in 'Demo' folder is using type 'list' for settings.

To reproduce you have to move the 'Example'-plugin into 'plugins'-folder.

@sammousa: This is only in the example plugin, not really sure what it was supposed to do. Maybe you can have a look.

@sammousa : Plugin can use own function to save the plugin setting (in array, in json etc ...)
but the real probem is in renderList : it can do only one line.

Did renderList receive current in array or in json ? Did you use renderList in one of your plugin ?
If yes : we must use same than your plugin, if not : we can update renderList for an array of current (i think it's the better solution : it's a list then we have an array,). Alternative is to directly use a json.

PS: we can test if current is array or not too.
Maybe $setting['currents'] for array and $setting['current'] for json

@sammousa : i can take it, but OK to use $setting['currents'] for array and $setting['current'] for json ?

In my opinion, current should reflect the current value.
So if this is a list setting then the current value should be an array.

Serialization should be transparent / invisible to the end user (which is a developer in this case).

Yes, sure for Serialization for current user. But for dev :).

OK, array is better see my comment : "(i think it's the better solution : it's a list then we have an array,)"

2.06 and 2.5 version. Target is 3.0 (or before if we have external dev who made the fix)