Zend Framework

Zend_Validate_Barcode_Ean13 and Zend_Validate_Barcode_UpcA error messages should handle differents keys

Details

  • Type: Patch Patch
  • Status: Resolved Resolved
  • Priority: Trivial Trivial
  • Resolution: Fixed
  • Affects Version/s: 1.7.5
  • Fix Version/s: 1.10.0
  • Component/s: Zend_Validate
  • Labels:
    None

Description

Errors keys shouldn't be "invalid" or "invalidLengh" and shouldn't be the same fo ZVB_Ean13 and AVB_UpcA as it causes translations issues when using both components and having a global translation array for a form.

Issue Links

This issue duplicates:
ZF-3164 Zend_Validate messageTemplate keys are not all unique. Major Resolved
ZF-3920 Unable to translate correct Barcode error message Minor Resolved
This issue is duplicated by:
ZF-7684 Duplicate message keys for Zend_Validate_Barcode_Ean13 and Zend_Validate_Barcode_UpcA Major Resolved

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Thomas Weidner added a comment -

Duplication of ZF-3920 and ZF-3164

Show
Thomas Weidner added a comment - Duplication of ZF-3920 and ZF-3164
Hide
Permalink
Thomas Weidner added a comment -

Issue was postponed until 2.0 after a discussion with the dev-team.
Reason is that the fix for this issue would be a BC break.

Show
Thomas Weidner added a comment - Issue was postponed until 2.0 after a discussion with the dev-team. Reason is that the fix for this issue would be a BC break.
Hide
Permalink
Thomas Weidner added a comment -

Probably fixed with r17874 for ZF 1.10

Show
Thomas Weidner added a comment - Probably fixed with r17874 for ZF 1.10

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Zend Framework. Try JIRA - bug tracking software for your team.