Re: [pmwiki-users] Should $EnableNotSavedWarning be enabled by default?

2022-01-04 Thread ABClf
No matter what choice will be done for sample-config, it's convenient to have this line written in starting config (commented or no), so that administrators know that such option does exist. As for me I have no preference here. I did not use that option ; testing now. If the message written in the

Re: [pmwiki-users] Should $EnableNotSavedWarning be enabled by default?

2022-01-04 Thread Simon
I couldn't agree more. As there is no easy undo if you close without saving, and the consequences are severe - the loss of potentially a lot of work. Also I think modern expectation (cf online editing such as google docs) is that you can't/shouldn't be able to accidentally lose input. great idea

Re: [pmwiki-users] Should $EnableNotSavedWarning be enabled by default?

2022-01-04 Thread j...@dodin.org
Le 04/01/2022 à 12:22, Petko Yotov a écrit : Thoughts? the best thing could be a periodically save to buffer system. A warning is often disturbing :-( thanks anyway (and happy new year, of course :-) jdd -- http://dodin.org http://valeriedodin.com __

[pmwiki-users] Should $EnableNotSavedWarning be enabled by default?

2022-01-04 Thread Petko Yotov
Currently by default PmWiki doesn't warn when people edit a page, and try to move away from the edit form without saving. We have $EnableNotSavedWarning but it needs to be enabled in config.php by the administrator. I added it to sample-config.php, but I wonder if instead we should simply en