Zend Framework

Dijit parsing before store creation fails value setting in FilteringSelect and ComboBox.

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8.4
  • Fix Version/s: 1.9.6
  • Component/s: Zend_Dojo
  • Labels:
    None

Description

In 1.8.4, doing something like this in a view:

echo $this->filteringSelect(
'select',
'20',
array(
'store' => 'store',
'storeType' => 'dojo.data.ItemFileReadStore',
'storeParams' => array('url' => '/my/data'))
);

Fails, the 'value' is not set because the store is not loaded when it it parses the input. With a filteringSelect the input remains a textbox with the value set, but it is not a dojo object, and everything else on the page breaks. With a comboBox the value and label are set to the identifier value that I am passing instead of the label getting set properly (assuming because combo box allows things not in the store). I tried putting a 'value' option in the params array, but that doesn't seem to propagate, and even if I test this by hand it still doesn't load properly because of the way things are getting parsed.

Anyone have any idea's? Besides creating all this stuff by hand?

Issue Links

This issue is duplicated by:
ZF-7360 Zend_Dojo_Form_Element_FilteringSelect value is not populated after calling the populate method on the form object Blocker Resolved

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matthew Weier O'Phinney added a comment -

Confirmed.

Show
Matthew Weier O'Phinney added a comment - Confirmed.
Hide
Permalink
Matthew Weier O'Phinney added a comment -

The following scenarios work:

  • Declarative usage
    • If the store is already defined prior to parsing, and the widget references the jsId of the store, then the value will be set.
    • If the store is already defined prior to parsing, but the widget does not define the store and the store is manually added to the widget following parsing, the value will not be set.
    • If the store is already defined prior to parsing, but has no jsId, there's no way whatsoever to associate it with the widget; the value will not be set.
  • Programmatic usage
    • The store must be set and added as part of the widget declaration for the value to be set (i.e., added as an object, not as a string referencing the jsId)
    • Any other situation will result in no value being set

Thus, the only way for this to work is for the store declaration to happen prior to onLoad, and for the store declaration to define a jsId.

Show
Matthew Weier O'Phinney added a comment - The following scenarios work:
  • Declarative usage
    • If the store is already defined prior to parsing, and the widget references the jsId of the store, then the value will be set.
    • If the store is already defined prior to parsing, but the widget does not define the store and the store is manually added to the widget following parsing, the value will not be set.
    • If the store is already defined prior to parsing, but has no jsId, there's no way whatsoever to associate it with the widget; the value will not be set.
  • Programmatic usage
    • The store must be set and added as part of the widget declaration for the value to be set (i.e., added as an object, not as a string referencing the jsId)
    • Any other situation will result in no value being set
Thus, the only way for this to work is for the store declaration to happen prior to onLoad, and for the store declaration to define a jsId.
Hide
Permalink
Matthew Weier O'Phinney added a comment -

Fixed in trunk and 1.9 release branch

Show
Matthew Weier O'Phinney added a comment - Fixed in trunk and 1.9 release branch

People

Vote (2)
Watch (3)

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.