| At line 2 changed one line |
| -------------------------------------------------------------------------------- |
|
| At line 5 changed one line |
| There is a solution to this it involved some very minor mods to the {{~EditTemplate.jsp:}} |
| There is a solution to this it involved some very minor mods to the {{~EditContent.jsp}} (''depends on wiki version and template being used actualyl'') |
| At line 13 changed one line |
| The way this patch works is a bit cheesey but we've been using it for over a week now and have had no ill effects. Basically what this patch does is submit the form contents, immediatly go back one step in history then the server response takes you to the page that the edit-submit was for. viola, magic! (''but timing sensitive maybe?'') One caveat is that you can still navigate __forward__ in you history into the edit window, but I'm willing to live with that as I do not know the keyboard shortcut for navigating forward. |
| The way this patch works is a bit cheesey but JohnV's been using it for almost a year now on a slightly modded [MRG Template] and have had no ill effects. Basically what this patch does is submit the form contents, immediatly goes back one step in history then the server response takes you to the page that the edit-submit was for. viola, magic! (''but timing sensitive maybe?'') One caveat is that you can still navigate __forward__ in your history into the edit window, but I'm willing to live with that as I do not know the keyboard shortcut for navigating forward. |
| At line 15 changed one line |
| Thoughts anyone? This seemes to work nicely for us, but I've not tried it with various browsers. (Though I'm told that the {{.go(-1)}} bit works fine under Netscape and the rest is very basic javascript.) In a way I'd like to see it get more testing and maybe get incorporated into the "mrg" template 'cause I'm lazy and don't like to have to remember what patches I need to do with every upgrade. |
| This seemes to work nicely for us; everyone here uses IE, I use Opera occasionally, but it's not really been tested on anyhting besides those. The {{.go(-1)}} bit works fine under Netscape according to google and the rest is very basic javascript. |
| At line 17 added one line |
| I'm not sure why this shouldn't be made part of the [default template], as it is just so darn useful at keeping novices from getting confused with old edits in thier browser history. |
| At line 21 added 6 lines |
|
|
| ---- |
| CategoryPatches |
| ---- |
| An alternate solution to this may simply be to disable page caching. This would force every page view to reload from the server. If you don't have a high load then you can afford the server work. This will ensure that a user's browser view always coresponds with the data model inside the wiki. |
