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

[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

Simon


On Wed, 5 Jan 2022 at 00:23, Petko Yotov <5ko at 5ko.fr> wrote:

> 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 enable it by default.
>
> I believe the setting dramatically improves the user experience and
> saves a lot of frustration, especially with inexperienced editors and
> administrators (who have yet to read the documentation and enable the
> setting).
>
> The setting, enabled, might possibly interfere with some custom edit
> forms, although I am not aware of such a case, or with some of the
> existing recipes that do exactly this.
>
> If we enable it by default, anyone who doesn't need this feature can
> disable it with
>
>    $EnableNotSavedWarning = 0;
>
> Even if there might be existing administrators who may be annoyed to add
> this line when they upgrade, I feel the benefit from having the feature
> enabled outweighs the downside.
>
> Thoughts?
>
> Petko
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pmichaud.com/pipermail/pmwiki-users/attachments/20220105/daa13f93/attachment.html>