-
9 Jul 2012 2:57 PM #1
TreeStore CRUD read request appends incorrect value
TreeStore CRUD read request appends incorrect value
REQUIRED INFORMATION
Ext version tested:- Ext 4.1 rev 1 GA
Browser versions tested against:- IE9
- FF3 (firebug 1.3.0.10 installed)
DOCTYPE tested against:- <!DOCTYPE html>
Description:- If a TreeStore has the nodeParam config item set, when it makes a read request it sends the param defined in nodeParam AND another called "id". These values are always identical.
Steps to reproduce the problem:- Create a TreePanel with a CRUD autoload store
- Render the panel
The result that was expected:
The following params sent- pNode
The result that occurs instead:
The following params sent- id
- pNode
Test Case:
What is sentCode:Ext.define('Songle.store.Playlists', { extend : 'Ext.data.TreeStore', fields : [ "text", {name: 'id', type: 'int'}, {name: 'song_id', type: 'int'}, {name: 'group_id', type: 'int'}, "leaf", "cls", {name: 'parentId', type: 'int'}, {name: 'index', type: 'int'} ], autoSync : true, remoteSort : true, folderSort : false, nodeParam : 'pNode', clearOnLoad: true, clearRemovedOnLoad: true, proxy : { type : 'ajax', api : { create : '../create_playlist', read : '../read_playlist', update : '../update_playlist', destroy : '../destroy_playlist' }, reader : { type : 'json', root : 'results' }, cacheString : 'pDC', writer : { type : 'json', writeAllFields : true, encode: true, root :"pJson" } }, listeners: { }, root : { text : 'Playlists', id : 0, expanded : true } });
What should be sentCode:http://localhost/read_playlist?pDC=1341873270383&pNode=0&id=0
Code:http://localhost/read_playlist?pDC=1341873270383&pNode=0
Debugging already done:- Remove the nodeParam config item and only this is sent
Code:http://localhost/read_playlist?pDC=1341873270383&node=0
Useful Information:- TreePanel has treeviewdragdrop view config and Ext.grid.plugin.CellEditing plugin configured
- The "id" param was not sent in 4.1.1RC1
Operating System:- Win 7
-
9 Jul 2012 6:02 PM #2
Thank you for the report. This has been fixed for the next release.
Scott.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-6755
in
4.1.2.


Reply With Quote