strange behaviour running ext.js combo in modx 3.2.3 , worked fine till 2.2.15

90 Posts

hurby Reply #1, 9 years, 6 months ago

Does anybody see things that arn.t compatible with 3.2.3 ?

Thnx
Hurby

MCM.combo.Resource = function(config){
    config = config || {};
    Ext.applyIf(config,{
        id: 'mcm-combo-resource' 
		,name: 'resourceID'
		,hiddenName: 'resourceID'
        ,displayField: 'pagetitle'
        ,valueField: 'id'
		,mode: 'remote'
		,fields: ['id','pagetitle']
		,forceSelection: true
		,editable: false
        ,enableKeyEvents: true
		,pageSize: 20
        ,url: MODx.config.connectors_url+'resource/index.php'
        ,baseParams: { 
			 action: 'getList'
			,showNone: true
		}         
    });
    MCM.combo.Resource.superclass.constructor.call(this, config);
};
Ext.extend(MCM.combo.Resource,MODx.combo.ComboBox);
Ext.reg('mcm-combo-resource',MCM.combo.Resource);

This question has been answered by hurby. See the first response.

Sommige mensen hebben aan een half woord genoeg

40 Posts

omegerard Reply #2, 9 years, 1 month ago

Hi Hurby

Quote from: hurby at Nov 07, 2014, 11:41 PM

Does anybody see things that arn.t compatible with 3.2.3 ?

I bet you were struggling with the compatibility of the Modx Campaign Monitor Integration extra.

Have you been able to find a work-around?

Would be nice if you share it. I'm having the same problem.

Regards

Ludo

discuss.answer

90 Posts

hurby Reply #3, 9 years, 1 month ago

Change mcm.combo.resource.js to this:

MCM.combo.Resource = function(config){
    config = config || {};
    Ext.applyIf(config,{
        id: 'mcm-combo-resource' 
	,name: 'resourceID'
	,hiddenName: 'resourceID'
        ,displayField: 'pagetitle'
        ,valueField: 'id'
	,mode: 'remote'
	,fields: ['id','pagetitle']
	,forceSelection: true
	,editable: true
        ,enableKeyEvents: true
	,pageSize: 20
        ,url: MODx.config.connector_url ? MODx.config.connector_url : MODx.config.connectors_url+'resource/index.php'
        ,baseParams: { 
		action: MODx.config.connector_url ? 'resource/getList' : 'getList'
		,showNone: true
	}         
    });
    MCM.combo.Resource.superclass.constructor.call(this, config);
};
Ext.extend(MCM.combo.Resource,MODx.combo.ComboBox);
Ext.reg('mcm-combo-resource',MCM.combo.Resource);

and change this line in core/components/mcm/processors/campaigns/create.class.php

	
$URL = $modx->getOption('site_url'). $modx->makeUrl( (int)$props['resourceID'] );

into this



$URL = $modx->makeUrl( (int)$props['resourceID'] );

Grtz
Hurby

Sommige mensen hebben aan een half woord genoeg

40 Posts

omegerard Reply #4, 9 years, 1 month ago

Thanks a lot, Hurby. It works.

Ludo

Quote from: hurby at Mar 30, 2015, 03:22 PM

Change mcm.combo.resource.js to this:

MCM.combo.Resource = function(config){
    config = config || {};
    Ext.applyIf(config,{
        id: 'mcm-combo-resource' 
	,name: 'resourceID'
	,hiddenName: 'resourceID'
        ,displayField: 'pagetitle'
        ,valueField: 'id'
	,mode: 'remote'
	,fields: ['id','pagetitle']
	,forceSelection: true
	,editable: true
        ,enableKeyEvents: true
	,pageSize: 20
        ,url: MODx.config.connector_url ? MODx.config.connector_url : MODx.config.connectors_url+'resource/index.php'
        ,baseParams: { 
		action: MODx.config.connector_url ? 'resource/getList' : 'getList'
		,showNone: true
	}         
    });
    MCM.combo.Resource.superclass.constructor.call(this, config);
};
Ext.extend(MCM.combo.Resource,MODx.combo.ComboBox);
Ext.reg('mcm-combo-resource',MCM.combo.Resource);

and change this line in core/components/mcm/processors/campaigns/create.class.php

	
$URL = $modx->getOption('site_url'). $modx->makeUrl( (int)$props['resourceID'] );

into this



$URL = $modx->makeUrl( (int)$props['resourceID'] );

Grtz
Hurby

Answered strange behaviour running ext.js combo in modx 3.2.3 , worked fine till 2.2.15