1. #51
    Sencha Premium Member
    Join Date
    May 2012
    Posts
    2
    Vote Rating
    0
    BakkerSpees is on a distinguished road

      0  

    Default


    Quote Originally Posted by oomta View Post
    Bug 6051 may still be there too.
    I am getting this error too.
    Code:
    node.updateInfo is not a function
    http://localhost:49442/javascripts/extjs/releases/extjs-4.1.1-rc1/ext-all-dev.js
    Line 55252

  2. #52
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Location
    Houston, Tx
    Posts
    8,617
    Vote Rating
    396
    scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future

      0  

    Default


    EXTJSIV-6051

    Marked as fixed in 4.1.1. May need to access nightly builds in support portal to get update.

    Scott.

  3. #53
    Sencha Premium Member
    Join Date
    Mar 2012
    Location
    Norway
    Posts
    24
    Vote Rating
    0
    atomcat is on a distinguished road

      0  

    Default Bug in JSonP

    Bug in JSonP


    Hi,

    There is a major bug in the JsonP class, in the buildUrl method. It does not take into account whatever the settings for the autoAppendParams config option is. The record data is automatically appended, which means, that even if the underlaying writer's encode param is set to true, and also the root property is set, the code will place a records parameter, and it will be duplicated. The problem is, that it takes over instead of the correct Json expected parameter

    Code:
        buildUrl: function(request) {
            var me      = this,
                url     = me.callParent(arguments),
                params  = Ext.apply({}, request.params),
                filters = params.filters,
                records,
                filter, i;
    
    
            delete params.filters;
    
    
            if (me.autoAppendParams) {
                url = Ext.urlAppend(url, Ext.Object.toQueryString(params));
            }
    
    
            if (filters && filters.length) {
                for (i = 0; i < filters.length; i++) {
                    filter = filters[i];
    
    
                    if (filter.value) {
                        url = Ext.urlAppend(url, filter.property + "=" + filter.value);
                    }
                }
            }
    
    
            //if there are any records present, append them to the url also
            records = request.records;
    
    
            if (Ext.isArray(records) && records.length > 0) {
                url = Ext.urlAppend(url, Ext.String.format("{0}={1}", me.recordParam, me.encodeRecords(records)));
            }
    
    
            return url;
        },
    I suggest the following fix:
    Code:
    //if there are any records present, and the autoAppendParams is set to true, append them to the url also
            if(me.autoAppendParams == true){
                 records = request.records;
    
    
                if (Ext.isArray(records) && records.length > 0) {
                url = Ext.urlAppend(url, Ext.String.format("{0}={1}", me.recordParam, me.encodeRecords(records)));
                }
        }
    Unfortunately in the doRequest method, the line commented with //prevent doubling up has no effect, since by that time the records are already encoded to the URL...

    Code:
        doRequest: function(operation, callback, scope) {
            //generate the unique IDs for this request
            var me      = this,
                writer  = me.getWriter(),
                request = me.buildRequest(operation),
                params = request.params;
    
    
            if (operation.allowWrite()) {
                request = writer.write(request);
            }
    
    
            // apply JsonP proxy-specific attributes to the Request
            Ext.apply(request, {
                callbackKey: me.callbackKey,
                timeout: me.timeout,
                scope: me,
                disableCaching: false, // handled by the proxy
                callback: me.createRequestCallback(request, operation, callback, scope)
            });
    
    
            // prevent doubling up -- no effect URL already contains the non JSON parameters...:(
            if (me.autoAppendParams) {
                request.params = {};
            }
    
    
            request.jsonp = Ext.data.JsonP.request(request);
            // restore on the request
            request.params = params;
            operation.setStarted();
            me.lastRequest = request;
    
    
            return request;
        },
    Should I open a bug report on this issue?

  4. #54
    Sencha - Support Team scottmartin's Avatar
    Join Date
    Jul 2010
    Location
    Houston, Tx
    Posts
    8,617
    Vote Rating
    396
    scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future scottmartin has a brilliant future

      0  

    Default


    If you feel you have located a bug, please use the following template:
    http://www.sencha.com/forum/showthre...o-report-a-bug

    Regards,
    Scott.

  5. #55
    Sencha Premium Member
    Join Date
    Mar 2012
    Location
    Norway
    Posts
    24
    Vote Rating
    0
    atomcat is on a distinguished road

      0  

    Default


    Ok. I'll report it correctly. Please note, that I've just tested the suggested bug fix, and it works correctly. So, maybe it's going to be an easy fix for the assigned responsible The bug is present in all, 4.0.7-4.1.1 versions.

  6. #56
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Also, please post bugs on the Bugs forum
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  7. #57
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,229
    Vote Rating
    114
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    @atomcat - sorry for the previous drive-by ... thanks for all your work on reporting this issue.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"

  8. #58
    Sencha Premium Member
    Join Date
    Mar 2012
    Location
    Norway
    Posts
    24
    Vote Rating
    0
    atomcat is on a distinguished road

      0  

    Default


    Ok, bug is reported under title "Ext.data.proxy.JsonP autoAppendParams ignored in buildUrl method".

    @dongryphon No problem. U R welcome.

  9. #59
    Sencha User
    Join Date
    Apr 2010
    Location
    China
    Posts
    43
    Vote Rating
    0
    manlsea is on a distinguished road

      0  

    Default


    Hi Boss
    What is the release time of the V4.1.1?

  10. #60
    Sencha Premium Member
    Join Date
    Mar 2012
    Location
    Norway
    Posts
    24
    Vote Rating
    0
    atomcat is on a distinguished road

      0  

    Default Ext.MessageBox.show inconsistent - hard to reuse.

    Ext.MessageBox.show inconsistent - hard to reuse.


    Hi,

    The Ext.MessageBox.show seems to be a bit inconsistent, since it also takes a config parameter, which is mandatory (if it's empty, it fails to display). On the other hand the parent Ext.Cmoponent class has a showAt method. This is inherited, and what it does as follows:

    Code:
        showAt: function(x, y, animate) {
            var me = this;
    
    
            if (me.floating) {
                me.setPosition(x, y, animate);
            } else {
                me.setPagePosition(x, y, animate);
            }
            me.show();
        },
    The code highlighted in red will cause error, as the MessageBox will try to reconfigure on a non-existing, undefined configure object.

    Also it's a bit of hassle to always pass in the config object, if I want to show the same dialog box again, and certainly the reconfiguration just takes up otherwise unneeded resources.

    I would suggest that the MessageBox should handle the case, as no reconfiguration object is passed in. Would be easier to reuse once created components, and would also fix the showAt bug.

    I took a look into the code, it would take a bit to store some of the reconfiguration parameters (like the wait config for the progressbar instance, if it's a wait dialog, etc.), but I feel, it would worth the efforts.

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar