Every time I save the configuration with the configure script I get an extra set of
(?-xism:
in
{UploadFilter}
and other settings. Here is the diff of one cycle, before and after the change:
diff LocalSite.cfg.save1 LocalSite.cfg
21,22c21,22
< $TWiki::cfg{Plugins}{StopWikiWordLinkPlugin}{Enabled} = 1;
---
> $TWiki::cfg{Plugins}{StopWikiWordLinkPlugin}{Enabled} = 0;
46,47c46,47
< $TWiki::cfg{UploadFilter} = qr/(?-xism:(?-xism:(?-xism:(?-xism:^(\.htaccess|.*\.(?i)(?:php[0-9s]?(\..*)?|[sp]htm[l]?(\..*)?|pl|py|cgi))$))))/;
< $TWiki::cfg{NameFilter} = qr/(?-xism:(?-xism:(?-xism:(?-xism:[\s\*?~^\$@%`"'&;|<>\x00-\x1f]))))/;
---
> $TWiki::cfg{UploadFilter} = qr/(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:^(\.htaccess|.*\.(?i)(?:php[0-9s]?(\..*)?|[sp]htm[l]?(\..*)?|pl|py|cgi))$)))))/;
> $TWiki::cfg{NameFilter} = qr/(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:[\s\*?~^\$@%`"'&;|<>\x00-\x1f])))))/;
71c71
< $TWiki::cfg{RCS}{asciiFileSuffixes} = qr/(?-xism:(?-xism:(?-xism:(?-xism:\.(txt|html|xml|pl)$))))/;
---
> $TWiki::cfg{RCS}{asciiFileSuffixes} = qr/(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:\.(txt|html|xml|pl)$)))))/;
128c128
< $TWiki::cfg{LoginNameFilterIn} = qr/(?-xism:(?-xism:(?-xism:^[^\s\*?~^\$@%`"'&;|<>\x00-\x1f]+$)))/;
---
> $TWiki::cfg{LoginNameFilterIn} = qr/(?-xism:(?-xism:(?-xism:(?-xism:^[^\s\*?~^\$@%`"'&;|<>\x00-\x1f]+$))))/;
Repeat this, and you get one more set of
(?-xism:
. Repeat again, and....
See
Item3048 for my environment.
--
PTh
I can confirm this bug. It has been reported before a long time ago. I was sure it was fixed once.
--
KJL
It was Item1007 I had seen where the (?-xism:(?-xism:(?-xism:... was in the report and the bug item closed. I thought back then that this was the bug that was fixed but it seems to have been a different bug that was fixed.
--
KJL
I am now at
?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:(?-xism:
for some of my settings.
We need this fixed for 4.1. Boosting to urgent
--
KJL
Thanks Crawford.
-> Waiting for Release
KJL
Thanks for fixing the issue. The code now simply filters out nested
?-xism:(...)
, which takes care of existing settings this issue.
Is this a real fix, or is this a workaround to cirumvent another issue?
--
PTh
4.1.0 released
KJL