Description: ------------ Problems sometimes arise if javascript in a template string matches the pattern for a replacement, e.g.: <a href="javascript:my_fn({firstkey:12,secondkey:'String'})"> var myRe = new RegExp("\d{1,5}"); Existing workarounds, e.g. setUnknowns('keep'), are not always convenient. Another possibility is to allow the user to expand the set of illegal characters in template variable names. Here is a diff of a possible implementation: 79a80,81 > var $illegals = ''; > 213a216,220 > function setIllegals($illegals = '') > { > $this->illegals = $illegals; > } > 506c513 < preg_match_all("/{([^ \t\r\n}]+)}/", $this->getVar($handle), $m); --- > preg_match_all("/{([^ \t\r\n}$this->illegals]+)}/", $this- >getVar($handle), $m); 538c545 < $str = preg_replace('/{[^ \t\r\n}]+}/', '', $str); --- > $str = preg_replace("/{[^ \t\r\n}$this->illegals]+}/", '', $str); 542c549 < $str = preg_replace('/{([^ \t\r\n}]+)}/', --- > $str = preg_replace("/{([^ \t\r\n}$this->illegals]+)}/", In the two examples above, $t->setIllegals(',') would work.

on second thoughts, the line in setIllegals() in my proposed changes should probably be: $this->illegals = preg_quote($illegals, '/');

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Will be in 1.5.0