I tried to add a comment to
Item4074 and got this error:
Access Denied
Attention
Access check on Bugs.Item4074 failed. Action "%PARAM1%": %PARAM2%.
Contact if you have any questions.
This is not a transient error, just tried it here too.
--
TWiki:Main/PeterThoeny
- 16 May 2007
Secondary issue: "%PARAM1%": %PARAM2%" are not expanded anymore.
--
TWiki:Main/PeterThoeny
- 16 May 2007
Still seeing this issue also in its temporary home at wikiring.
But it works on my Merlin test server which also runs from MAIN.
--
TWiki:Main.KennethLavrsen
- 24 May 2007
it works on MAIN. We can live without it until d.t.o returns to its proper home, there are more urgent things to do
--
CC
I would agree if only on delelop.twiki.org. It happens now also in the temporary bugs twiki. This needs to be investigated and fixed, or it might slip into the release affecting certain environments.
--
PTh
This
is develop.twiki.org right now; and was when the report was submitted. And I
did investigate it, and concluded that the server configuration is behind the curve (as evidenced by
Item3775
--
CC
Item3775 is a real bug, I just re-opened it.
I re-opened this bug here and set it to "not TWiki" since CC indicated that this is Bugs TWiki specific. This is an annoying bug that needs to be fixed.
--
PTh
Could someone please look at this? It is very annoying to type somthing into the inviting comment box and to get a screaming message back to go away.
--
PTh
I looked, but there's nothing I can do; I don't have access to the server. it's nothing to do with the topic template AFAICT; a simple %COMMENT in this topic exhibits the same behaviour. I can't spend any more time on it, especially since it will disappear when we move back to the proper server.
CC
on the other hand,
TestTopic7 shows that it works fine outside the Bugs system - its not a simple issue - when I looked into it last week, the server told me nothing useful either.
--
SvenDowideit - 02 Jun 2007
ok
--
TWiki:Main.SvenDowideit
- 02 Jun 2007
YAY! making a new
LocalSite - this one has been constantly upgraded since we started develop, and svn up'ing to todays version has quietly fixed it. distressing that there is NOTHING in the logs about the problem.
--
TWiki:Main.SvenDowideit
- 02 Jun 2007
Nice one! Thanks for fixing it!
--
TWiki:Main.PeterThoeny
- 02 Jun 2007