Description
When first adding #DEPRECATED, a final backup should be made; currently, you have to remember to do this manually.
- When #DEPRECATED appears on the backup page, the #DEPRECATED handling seems to be triggered repeatedly; this is of course wrong.
Overall, people appear to have problems with grasping how the stuff works. Maybe a better way would be to change full-text search to look at the pragma instead of the special edit/display handling.
Example
Details
This wiki
Workaround
Discussion
I think #deprecated does not exactly what it should. HelpOnProcessingInstructions states that " This effectively freezes the last version of the page", but it does not seem so, cause you can still change the last version of the page. So it just disables backups and you can do changes without any hope of recovery.
The docs also state that the last two versions of the page are shown. Thats the case, but the markup is not good.
Finally searchs should not find #depcrecated pages, which is not the case.
I think it is a bug. At least the docs should be clarified.
-- OliverGraf 2004-08-02 17:01:01
Questions
- Is it possible to remove a #deprecated pragma from a page?
- it should...
- If yes, what is a backup of the deprecation archived? (I think not)
- display gets confused if viewing a cached deprecation warning.
- are searchs blocked?
- yes, they are, cause only the newest version is sought. so a search will find contents of the deprecation warning but not contents of the cached last copy.
Plan
- Priority: medium
Assigned to: OliverGraf
- Status: fixed in moin--main--1.3--patch-191