Problems with advanced search and custom extension

Friday 10 October 2003 8:14:10 am - 2 replies

2 replies

Author	Message
David Syers	Tuesday 14 October 2003 4:52:13 am Well it turns out that in the end it was not my custom extension at all. The problem lay in one of my templates where I had accidently passed an array as a fetch function parameter instead of the array value.
David Syers	Tuesday 14 October 2003 7:48:39 am Now it turns out that I was a bit hasty earlier and it turns out that I was passing the correct value (I just mistook it for an array at first). There is a bug with the \|reverse operator when you are under the advanced search. ie. If $node.path_array was equal to array(1,2,47,94) and you did {set node_array_reversed=$node.path_array\|reverse} under any other view (as far as I am aware anyway) you would expect $node_array_reversed to be: array(94,47,2,1) However under the advanced search you get yarrA So it looks like under the advanced search \|reverse is returning the type text "Array" reversed.

Author

Message

Tuesday 14 October 2003 4:52:13 am

Well it turns out that in the end it was not my custom extension at all.

The problem lay in one of my templates where I had accidently passed an array as a fetch function parameter instead of the array value.

Tuesday 14 October 2003 7:48:39 am

Now it turns out that I was a bit hasty earlier and it turns out that I was passing the correct value (I just mistook it for an array at first).

There is a bug with the |reverse operator when you are under the advanced search.

ie. If $node.path_array was equal to array(1,2,47,94) and you did

{set node_array_reversed=$node.path_array|reverse}

under any other view (as far as I am aware anyway) you would expect $node_array_reversed to be:

array(94,47,2,1)

However under the advanced search you get

yarrA

So it looks like under the advanced search |reverse is returning the type text "Array" reversed.

You must be logged in to post messages in this topic!