Description
If you move an exising macro to a different name in 1.6 1900:89fffad859b5 you got a traceback on each one where that old macro name was used before.
May be there should be a test added to clear the page cache
Steps to reproduce
- do this...
Example
Component selection
- general
Details
MoinMoin Version |
1.6 1900:89fffad859b5 |
OS and Version |
linux |
Python Version |
2.4.4 |
Server Setup |
cgi-bin |
Server Details |
|
Language you are using the wiki in (set in the browser/UserPreferences) |
|
Workaround
Discussion
When changing code you have to touch the configuration file or the MoinMoin directory. The bytecode cached by moin checks for that and invalidates itself if it detects a change there. We can't check every single file for obvious reasons.
Another method is to globally clear the cache manually or with moin command.
I don't want that checking, perhaps we can invalidate the bytecode cached if that exception occures and then reload again one time. So it fixes this itselfs
Plan
- Priority:
- Assigned to:
- Status: