Hi @JevgenijVisockij,

I found only one issue:
In all fields, you have a required option

Before, it was ok

Thanks to check and feedback.

Blocked #21245 as that PR would remove uneeded red * from Yes/No types.

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

• Admin.Notifications.Error
  • The field is invalid. Please enter a positive integer number.

(Note: this is an automated message, but answering it will reach a real human)

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

* `Admin.Notifications.Error`
  
  * [ ]  [`The field is invalid.`](https://github.com/PrestaShop/PrestaShop/pull/21234/files#diff-cc92abd6661aff278f401928bb4395b8R81)

(Note: this is an automated message, but answering it will reach a real human)

Previous message was "The %s field is invalid" with %s being "Password reset delay" I think that message no longer makes sense since now error message is shown next to the field. Should I change message back to how it was or maybe anybody has ideas for a better error message here.

Input is considerd invalid when it's not numeric or is lower then 0.

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

* `Admin.Notifications.Error`
  
  * [ ]  [`The field is invalid.`](https://github.com/PrestaShop/PrestaShop/pull/21234/files#diff-cc92abd6661aff278f401928bb4395b8R81)

(Note: this is an automated message, but answering it will reach a real human)

Previous message was "The %s field is invalid" with %s being "Password reset delay" I think that message no longer makes sense since now error message is shown next to the field. Should I change message back to how it was or maybe anybody has ideas for a better error message here.

Input is considerd invalid when it's not numeric or is lower then 0.

Hi @JevgenijVisockij, sorry for the late answer!
If I understand well, it is the same error than in this PR (#21243). If yes, why not using the same wording? "The field is invalid. Please enter a positive integer number." in Admin.Notifications.Error

Also, I agree that if the error message is just next to the field, it may not be necessary to specify the name of the field again. Could you show me with a screenshot how it would appear, please?

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

* `Admin.Notifications.Error`
  
  * [ ]  [`The field is invalid.`](https://github.com/PrestaShop/PrestaShop/pull/21234/files#diff-cc92abd6661aff278f401928bb4395b8R81)

(Note: this is an automated message, but answering it will reach a real human)

Previous message was "The %s field is invalid" with %s being "Password reset delay" I think that message no longer makes sense since now error message is shown next to the field. Should I change message back to how it was or maybe anybody has ideas for a better error message here.
Input is considerd invalid when it's not numeric or is lower then 0.

Hi @JevgenijVisockij, sorry for the late answer!
If I understand well, it is the same error than in this PR (#21243). If yes, why not using the same wording? "The field is invalid. Please enter a positive integer number." in Admin.Notifications.Error

Also, I agree that if the error message is just next to the field, it may not be necessary to specify the name of the field again. Could you show me with a screenshot how it would appear, please?

Hey

I think using same wording makes sense.

And here is the screenshot

Hi @JevgenijVisockij,

It is ok ✔️

THanks!