<filterset begintoken="/" endtoken="/"> <filter token="etc" value="/local/etc/"/> </filterset>
In 1.6.2, the fixed bugs list includes the entry:
* replacestring tokenfilter only replaced the first occurrence.
And, lo and behold, attempting to run this filter in 1.6.2 now gives:
[copy] Infinite loop in tokens. Currently known tokens : [etc]
Would it be possible to make the filtering continue after the last replacement, rather than start over at the beginning of the line, to make such a replacement possible again? It seems pretty clear that no one would ever intend to create an infinite loop of token replacements, so ignoring occurrences of the token within the replacement text from the filter should be safe.
Sorry if this has been covered before, but I did a couple searches on the archives and found no other mention of this question since 1.6.2 came out.
-Chris Shabsin
