How to get selected messages in groupwise add in - interop

I am trying to get selected messages from GroupWise client add in.
previously our code to get it was working fine using C3POManager with GroupWise version 8, but with new GroupWise version 2014 it has stopped working.
previously working code as below
Dim oSelectedMessages As Object = C3POManager.ClientState.SelectedMessages
If oSelectedMessages.Count > 0 Then
sMessageID = oSelectedMessages(1).MessageID
End If
now with GroupWise 2014 oSelectedMessages is Nothing (null).
I have tried searching on internet and also tried looking at Novell's documentation but couldn't find any suitable solution.
can any one suggest what is changed by groupwise or how to overcome this issue.
Thanks,
Tank

It sounds like you may be using an obsolete version of the C3PO objects. Make sure you have the latest Groupwise SDK.
There is also the Groupwise C3PO support forum.

Related

KendoReportViewer JS upgrade issue

I am trying to upgrade my KendoReportViewer JS file. I was using 'telerikReportViewer-10.0.16.min.js' before. Now I have upgraded it to 'telerikReportViewer-12.2.18.min.js'. After upgrading, the parameters section of reports is not showing.
I am using KendoReportDesigner for building reports. CAn anyone guide me where I am wrong.
Thanks
The report viewer and report server have to be identical in version or at least close. I have asked Telerik support about this before.

Java SDK for Facebook Ads API 2.10 missing AdsInsights.getFieldImpressionDevice() method

Currently using Facebook Ads SDK for Java v2.9 and trying to upgrade to v2.10 or v2.11. However, neither of the newer versions has the method getFieldImpressionDevice on the AdInsights object? I haven't found any change log info that discusses a change or deprecation around this call. Anyone have any insight into this problem?
Also a little confused as to why github :
https://github.com/facebook/facebook-java-ads-sdk/
doesn't have the 2.10 or 2.11 libs only the 2.9 libs even though this link indicates it, eg.,
src/main/java/com/facebook/ads Ads SDK v2.11 Release Nov 8, 2017
Thanks for any help
There's a known issue it turns out. Some (or all) of the breakdown fields and methods in the AdsInsights class were left out. It can be worked around using raw json, eg.,
JsonObject jo = insight.getRawResponseAsJsonObject();
JsonElement je = jo.get("impression_device");
String device = je.getAsString();

Nullreference when trying to set ACL property of new Parse object

As the title already explains I have null reference exception when I try to set the ACL property of my new parse object.
The code is this:
ParseObject storeAssets = new ParseObject("StoreAssets");
storeAssets["myKey"]="MyValue";
ParseACL storeAssetsPermissions = new ParseACL(ParseUser.CurrentUser)
{
PublicReadAccess = true,
PublicWriteAccess = false
};
storeAssets.ACL = storeAssetsPermissions;
the code looks like in the examples of the documentation but it's not working...
I believe it stopped working with new version of Parse Unity SDK, because the app that I have on the store uses the same code and works correctly.
The code gives me Nullreference exception on the ACL setter.
I am using Parse Unity SDK version 1.6.2
Is anybody else experiencing the same problem?
Since I spent hours trying to figure out what the problem was, I think I will answer my question so that other people that encounter the same problem don't waste time.
I solved the NullReferenceException by downgrading to Parse Unity SDK version 1.6.1.
You can download it following this link
https://parse.com/downloads/windows/Parse/1.6.1
I tried one more time with version 1.6.2 just to be sure. Result is that with the same exact code, in version 1.6.1 the code works while in version 1.6.2 I have NullReferenceException
If you find a fix in 1.6.2 please share it.
Ok
This issue is solved. It was a tricky call, because it was due to the Asset store publishing system that corrupted the Parse Package, so you would think you got the latest version of Parse, but it was not the case.
https://github.com/ParsePlatform/Parse-SDK-dotNET/issues/155

ExpressionEngine issue with Wygwam

I have this posted here:
https://getsatisfaction.com/pixelandtonic/topics/wygwam_not_styled_in_cp_entry_and_not_functioning_shown_errors_attached
...but I really need a fix asap if anyone can help here.
I can't get Wygwam to work.
It started with me running this:
EE 1.6.8 (Again, can't update)
Wygwam 2.1.6
FieldFrames 1.4.5
I wasn't able to activate the module. I would receive errors and then the field was jacked.
I then upgraded Wygwam to 2.6.3 and that allowed my to enable the module.
The problem I have now is this:
When I try to Add a new Wygwam field, it tells me that there are no configurations available. When I go to 'Edit Configurations', I only get the serial number input field. I added the serial number, but nothing changed. Under 'Editor Configurations' it just says: There are currently no configurations.
Now I have the existing fields back, however, I cannot view source and do not have any "Configurable Editors" available. I also cannot setup any "Configurable Editors" in the module because I have no settings/options display. Also, I cannot add any new Wygwam fields because when I do, I just get a white screen.
Ok, While this may not be the best answer to provide, it has provided a resolve to the situation I was in.
First off, Kudos goes to Brad Bell at Pixel & Tonic for sticking with me via emails in trying to get this fixed. I am in a situation with this site in which I can't provide access to the site, files, data, etc. It definitely makes getting help with EE related instances more difficult. Brandon and his staff definitely know how to push through these issues.
Thanks guys.
Nothing we were trying was working. What I had to end up doing was rolling back the versions of Wygwam and Matrix from the more recent releases that were installed to WW 2.1.1 and Matrix 2.0.11
I didn't try newer versions as I want to push harder than ever now for a site update/rebuild due to these issues and others. The site is again functional in these areas and they can move forward, (or laterally... depending on your stance), again.

Upgrading Magento

Just a quick question involving upgrading Magento. I currently have version 1.4.1 and would like to update to the newest version. I tried upgrading through the Magento Connect and can not get that to work. And my host will not give me SSH access so I can't do it that way.
It's very frusterating, what are my other options? Can I just download the new set of files and replace those, but keep the old database? Will that work?
Not sure the best way to approach this. Thank you.
search SO to get similar answers:
disable all 3rd party extensions
disable custom themes
upgrade (you can do version by version also)
turn on your theme
turn on extensions one by one and debug

Resources