TYPO3 Core

Hi, could you please make a list which "nag screens" you mean? (It is easier to change things then)

- Alert when changing content elements
- Alert when changing in FlexForms
- Alert in the install tool

I think this option to disable the "nag screens" should be set either in the user preferences (user->setup) or in the user TSconfig. Any opinions on that?

I think the most annoying message is the one that appears when one changes the content type. It could be useful if admin users can change the behaviour in the setup but not the "normal" user.
For them the admin should make the decision if the nag screens should appear or not.

By the way, another message pops up on deleting elements.

Another nag screen that should detachable is the alert when inserting (copy/paste) content elements and pages (also on copying with clipboard).

Greets,
Thomas

at least for me the "copy/move/delete" warnings are very helpful and I won't miss them.
I can remember many occasions where reading this messages saves me a lot of work.

but I agree with Thomas that the "onChange" messages in "type" fields should be detachable.
-> f.e. with an extra option in TCA which could be made configurable by extensions authors.

OK, a delete warning makes sense! :)

Greets,
Thomas

Maybe these warnings could be grouped into some groups which could be configured afterwards then?

- Deletion warnings
- change of CE warning
- copy / paste content elements/pages/ (also to clipboard)
what else?

I don't think the onChange warning of the CE should be set in TCA, as this behavior should be changeable for users in User/Group TSconfig. If it was possible to change it in TCA, some authors would allow it, some others wouldn't, and this inconsistency could confuse some users.
Greets, Sebastian

bitmask in userTSconfig
, disable nochangealert in type fields

The attached patch solves the issue. It implements the User TSConfig Option:
options.alertPopups

which is a bitmask, setting which alert boxes should be shown.

1 - onTypeChange
2 - copy/move/paste
4 - delete
8 - frontend editing
128 - other (not used yet)

Default: all.

TODO: TSConfig Reference NEEDS TO BE UPDATED

DOCUMENTATION:

The option supersedes the configuration option
options.noChangeAlertInTypeFields which is removed completely.

user TSconfig: "OPTIONS"

alertPopups

bitmask

configuration which javascript alert popups should be shown:
1 - onTypeChange
2 - copy/move/paste
4 - delete
8 - frontend editing
128 - other (not used yet)

Default: 255 (all)

Nope. Default definitly not all(255)!
Confirm on delete or move has already saved me (and probably some users?) hours of work. ;)

This change in default-behaviour would require feedback from large user-base imho.

Oher than that, sounds good. I'll try the patch.

Hi Peter,
"default 255" means that all warnings will be shown.
Greets, Sebastian.

fixed in CVS.