Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Imported from: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/9db1d82d9f67141a#

There is a special feature in In-Portal (that I bet nobody knew about) that
allows each system setting have it's own validation logic, e.g. be always
required or allow only numbers.
To use it you need to place serialized array of field validation options
into "Validation" column of that system setting.

Because of we are not using this very often (I think we should start using
it at some point) error, where validation logic from system setting A is
passed on to next system setting in same subsection was unnoticed for a
long time.

For example you have 2 system settings one after each other:   -

  • Site name

...

  • Session expiration timeout

When you apply "required" validation to "Site name", then "Session
expiration timeout" settings become required too.

Task: system_setting_validation_mixed_fix.patch

Related Tasks

Jira Legacy
serverIn-Portal Issue Tracker
keyINP-1118

Ready for testing.

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

system_setting_validation_mixed_fix.patch