CMS MADE SIMPLE FORGE

Frontend Users

 
Back Back to List

[#3829] "Required" field status doesn't work

avatar
Created By: Rick Mann (Ricko97)
Date Submitted: Sun Aug 02 20:59:15 -0400 2009

Assigned To:
Version: 1.6.8
CMSMS Version: None
Severity: Major
Resolution: None
State: Closed
Summary:
"Required" field status doesn't work
Detailed Description:
FEU Properties which are set to "Required" in a group behave like optional
fields.

I have tested this in 2 CMSMS installations for the same site, one prior to
updating modules and one after updating them. "Required" fields could be left
blank without error in the post-update installation (FEU 1.6.7->1.6.8).

I updated FEU in the pre-update installation and tested the fields in that to
confirm.

EDIT: In my rush to submit this, I failed to notice it was already reported. My
bad.

EDIT 2: Just to make myself look even more stupid, in my rush to close this, I
failed to notice the other report ("Date Property Type not working when
REQUIRED") is actually about a different bug, but may be related.


History

Updates

Updated: 2014-04-26 12:19
cmsms_version_id: => -1
state: Open => Closed

Updated: 2009-08-02 23:33
summary: (IGNORE!) "Required" field status doesn't work => "Required" field status doesn't work

Updated: 2009-08-02 23:32
description: FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e => FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e
resolution_id: 9 => 5
severity_id: 12 => 2
state: Closed => Open

Updated: 2009-08-02 23:29
description: FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e => FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e
summary: "Required" field status doesn't work => (IGNORE!) "Required" field status doesn't work
resolution_id: 5 => 9
severity_id: 2 => 12
state: Open => Closed

Updated: 2009-08-02 21:00
description: FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e => FEU Properties which are set to "Required" in a group behave like optional fields. I have tested this in 2 CMSMS installations for the same site, one prior to updating modules and one after updating them. "Required" fields could be left blank without e
resolution_id: => 5