miva_array_collapse question

[ids]

If I had:

mivarray[1]
mivarray[3]

and run it thru miva_array_collapse, I get the proper count of 2. But isn't it suppose to reorder the indexes?

mivarray[1]
mivarray[2]

And maybe I should also ask this first, does this work in storemorph? I didn't receive any errors, and not getting an expected result.

Thanks,
Scott

[Gordon - Phosphor Media]

According to mivascript.com:

Collapses the array_variable making the indices sequential starting at 1. Returns the number of elements in the array.

So it should reorder the indices. I'm sure I observed this when using it years ago. Are you seeing different behavior?

[ids]

I didn't receive any errors, and not getting an expected result.

So yes different behavior.

More specific:

mivarray[1]
mivarray[3]

has a max of 2. When cycling through starting at 1, you never reach the 3rd element because the index didn't actually get reordered.


I think it was 5.21 Engine fixed a bug that read like it was related because it wasn't removing sparse elements.

But, this is also in the templates not mivascript (as in a module).

More detail in case it's important... the array I need to collapse is a global.

[Gordon - Phosphor Media]

I've only used it in modules, in fact it is in 10 of ours. AFAIK it works fine still (although I'll verify soon).

[ids]

Does that mean you're going to verify in a template?

[Gordon - Phosphor Media]

No, I don't do template code, sorry.

It doesn't make sense that it would behave differently in SMT vs. compiled module, since it calls the same function either way.

[RayYates]

I tried this test and it worked for me.

<mvt:assign name="g.array[2]" value="'TestString1'" />
<mvt:assign name="g.array[5]" value="'TestString2'" />
<mvt:assign name="g.count" value="miva_array_collapse( g.array )" />

count = &mvt:global:count;<br>
&mvt:global:array[1];<br>
&mvt:global:array[2];<br>

Max = <mvt:eval expr="miva_array_max(g.array)" />

[ids]

Thanks Ray.

I am concluding a typo in my code somewhere.