Subpanel not getting open in suagarcrm 7.8 version - crm

I updated Sugar from version 7.6 to 7.8 i add some custom code in subpanel-list.js and it was working perfect in 7.6 version . But now in 7.8 version due to this code subpanel is not working . Can any one tell me the solutions for that.
I tried to ask this question to sugar support team but they told me that it is related to custom code , so need to ask to sugar developers.
I am providing my code which was working on 7.6 but due to this code now in 7.8 subpanel is not working.
({extendsFrom: 'SubpanelListView',
//contextEvents: {"list:inviteportal:fire": "renderOnInvitePortal"},
initialize: function(options) {
// this.dataViewName = options.name || 'subpanel-list';
this._super("initialize", [options]);
this.context.on('list:inviteportal:fire',this.renderOnInvitePortal, this);
},
renderOnInvitePortal: function(model){
app.api.call('read',app.api.buildURL(model.get('_module'),'read',{id:model.get('id')}),null,
{
success: function(data) {
bean = app.data.createBean(data._module,data);
app.drawer.open({
layout : 'inviteportal',
context : {
create : true,
model : bean,
module : bean.get('_module')
}
});
},
error: function() {
return;
}
}
);
},
})

I found the problem , In subpanel-list.php in 7.7 version
'template' => 'recordlist',
Now in 7.8 version it is.
'template' => 'flex-list',

Related

Corda - How do you implement expectEvents parallel predicates using Java

I'm looking for a Java example similar to the Kotlin code shown in the following example (taken from the Corda integration testing tutorial at: https://docs.corda.net/releases/release-M6.0/tutorial-integration-testing.html)
bobVaultUpdates.expectEvents {
parallel(
(1 .. 10).map { i ->
expect(
match = { update: Vault.Update ->
(update.produced.first().state.data as Cash.State).amount.quantity == i * 100L
}
) { update ->
println("Bob vault update of $update")
}
}
)
}
I'm also curious if this technique is still recommended, as it seems to have been removed from the latest version of this tutorial (https://docs.corda.net/releases/release-V4.3/tutorial-integration-testing.html).
The page you linked to is broken, however, there is a Corda 4.4 version of the tutorial.
here's the link :
https://docs.corda.net/docs/corda-os/4.4/tutorial-integration-testing.html
There is some similar java code to what you shared here but the examples have been changed a bit.
Class<Vault.Update<Cash.State>> cashVaultUpdateClass = (Class<Vault.Update<Cash.State>>)(Class<?>)Vault.Update.class;
expectEvents(bobVaultUpdates, true, () ->
expect(cashVaultUpdateClass, update -> true, update -> {
System.out.println("Bob got vault update of " + update);
Amount<Issued<Currency>> amount = update.getProduced().iterator().next().getState().getData().getAmount();
assertEquals(DOLLARS(1000), Structures.withoutIssuer(amount));
return null;
})
);
Thanks!

Support for mapping keys in multi-line blocks is deprecated since Symfony 4.3 and will throw a ParseException in 5.0

I have a problem. After updating to Symfony 4.4 I got the following deprecation warning
Support for mapping keys in multi-line blocks is deprecated since Symfony 4.3 and will throw a ParseException in 5.0.
2x in AccountControllerTest::testSettings from App\Tests\Controller
1x in AccountControllerTest::testPageUser from App\Tests\Controller
I have absolutely no clue what this means.
testSettings from App\Tests\Controller:
public function testSettings() {
$crawler = self::$userClient->request('GET', '/nl/account/settings.html');
$this->assertSuccesfulResponse(self::$userClient->getResponse());
$crawler = $this->form(self::$userClient, $crawler, 'submit', array(), '/\/nl\/account/');
}
Thanks in advance!
This mean that you potentially have a multi line key in your somewhere in a Yaml file and it's not supported by symfony and in symfony 5.0 it will throw an exception not a warning !
Something like that:
this
is
multi
key: test

"callback is not a function" with $bindToContext

In my angular-meteor app I'm using mdg:camera. I'm trying to update a field from the callback to show the image. Here's the code snippet:
this.addImageToPost = () => {
MeteorCamera.getPicture({
quality: 50
}, this.$bindToContext((err, data) => {
if (err) {
console.log(err);
return;
}
this.imgDataUrl = data;
}));
};
This has been working great. But now after I finished updating my app to use meteor 1.3 (with all the new updates to angular package and mdg:camera as well) this became broken with a "callback is not a function" error.
If I remove the "this.$bindToContext" part, I get a working code - only obviously it's not reactive.
Any idea what's going on? I wonder if the newest updates broke something...
Any help would be greatly appreciated!

Meteor -> percolatestudio/meteor-migrations --- not working for version 0

Trying to get this migrations plugin working for meteor project: percolatestudio/meteor-migrations
Migrating up and down between various migration versions seems to work fine when greater than 0.
However when trying to migrate back to 0 (clean slate), it doesn't seem to work. Nothing happens --- no errors, and it still thinks it is at the last version it migrated to.
Here is my code for a simple migration:
Migrations.add({
version: 1,
name: 'Add engagement and lastActiveAt fields to cloud users for analytics',
up: function() {
CloudUsers.update({}, { $set: { lastActiveAt: Date.now(), engagements: {} } }, { multi: true });
},
down: function() {
CloudUsers.update({}, { $unset: { lastActiveAt: '', engagements: '' } }, { multi: true });
}
});
It successfully migrates up(), but will not migrate back down() to 0. However if I copy & paste this code and create a version 2 migration. I can successfully migrate up and down between the two.
I am following the documentation on how to revert back to version 0:
Migrations.migrateTo(0)
This was a bug with that specific version, the latest version now has fixed this issue.

Protoype/Scriptaculous Autocomplete

I am getting this error when trying to select a object in my autocomplete
This only comes up in IE 8, and Firefox 3.5, not IE 7 or FF 3.0
Error: uncaught exception: [Exception... "An invalid or illegal string was specified" code: "12" nsresult: "0x8053000c (NS_ERROR_DOM_SYNTAX_ERR)" location: "http://localhost/js/prototype.js Line: 2853"]
P2N.Submission.autoSuggest.init('',
'place-list',
'hiddenPlaceID',
'/placeSearch.ashx?cityID=&allowNewPlace=',
'place-search-spinner', {resultID : '' });
Update:
p2n is
var P2N = {
returnVal: null,
errorMsg: null,
initWindow: function() {
},
addSpinner: function(el) {
if(!$(el).next('img.spinner'))$(el).insert({after: '<img src="/img/spinner_small.gif" alt="" class="spinner" />'})
},
removeSpinner: function(el) {
var spinner = $(el).next('img.spinner');
if (spinner != null) spinner.remove();
}
autoSuggest.init I believe is prototype version 1.6, and Scriptaclous vers 1.8
While they also are loading jquery ver 1.3.2
I believe it may be a conflict in all of these, but why would it work in older browsers?
};
We had the same problem - it's definitely a bug in prototype.js 1.6.0.x. Upgrading to 1.6.1 fixed it.

Resources