Profound Logic Forums

Posted: **Tue Nov 13, 2012 3:04 pm**

Hello Jorge, Paul,

We are scheduled to release a new build of Profound UI today. A few changes were made that will give us more detailed information about the issues you are experiencing and help us debug them. Once the build is out, you'll need to grab the newest runtime.js and profoundui.css files and place them in your projects and rebuild your applications. Run your applications and recreate the error and let us know what error messages you get this time; you can email a screenshot of the error screen to support@profoundlogic.com or post them here.

Posted: **Tue Nov 13, 2012 3:36 pm**

Version 4.1.7 is now published, and available for download.

If nothing else, it should give you proper error messages, instead of "undefined".

also, please make sure your PUIUPLEXIT programs are in the PROFOUNDUI library (or, whichever library you installed PROFOUNDUI into.)

Posted: **Wed Nov 14, 2012 3:39 pm**

Thanks for the support so far guys.

I added the latest versions runtime.js and profoundui.css to my project and I'm getting: "Operation prevented by exit program", instead of "undefined", as the error message.

The PUIUPLEXIT program is in the PROFOUNDUI library.

I'm thinking its something on my side now, since I tried to use the file upload widget, and I'm getting the same message: "Operation prevented by exit program".

Posted: **Wed Nov 14, 2012 4:42 pm**

Yes, the upload widget, the camera and the signature upload all call the same server-side program with the same exit program. There was a bug that the server-side program wasn't communicating it's errors properly with the camera -- but was communicating them properly with the widget, but that was just related to how they communicate the errors, not related to whether it worked or not. And is fixed in 4.1.7

I worked with Jorge (jac53 in these forums) today, and we fixed it on his system simply by re-compiling his PUIUPLEXIt program. Neither of us really knows why that helped... but as soon as we recompiled it, it worked without errors.

So maybe that'll help, Paul? If not, let us know.

Posted: **Thu Nov 15, 2012 8:28 am**

Yes, Jorge had sent me an email telling me to recompile the PUIUPLEXIT program. After recompiling, "pui.capturePhoto()" worked. I was able to take a picture and it was uploaded to the IFS. Thanks!

My Signature image is uploading also. However I'm still getting the "undefined" error. I used the example in this post: http://www.profoundlogic.com/docs/displ ... config+%29

I Placed the code in a function and called that function in the onClick of a button. The same way how I used "pui.capturePhoto()".

Posted: **Thu Nov 15, 2012 10:21 am**

Paul,

There are three possible causes of the "undefined" error

A bug in ProfoundUI 4.1.5/4.1.6 caused this message to occur instead of a proper message for the pui.capturePhoto()
A mismatch between the runtime.js and the back-end server code. If you run version 4.1.5 or newer of the server code with version 4.1.4 or older of runtime.js you will get this error.
a bug in your handler code that calls the pui.capturePhoto() or pui.uploadSignature() API (but this is perhaps, unlikely.)

Can you check into these and let us know?

Posted: **Thu Nov 15, 2012 2:07 pm**

I'm thinking its the first cause. I was getting "undefined" when I used pui.capturePhoto() in the 4.1.6 release. When you guys fixed it 4.1.7, I got the correct error message.

I'm still getting "undefined" when I used pui.uploadSignature() in both 4.1.6 and 4.1.7.

This is my function:

Code: Select all

function uploadSigImage(){  

	pui.uploadSignature({
	  "signaturePadId": "SignaturePad1",
	  "dir": "/www/profoundui/htdocs/profoundui/userdata/images/CustImages",
	  "imageType": "image/jpeg",
	  "fileName": "signature.jpg",
	  "overwrite": true,
	  "handler": function(response) {
		if (response.success) {
		  pui.click();
		}
		else {
		  alert(response.error);
		}
	  }
	});
}

Although my upload was successful, "response.success" didn't return true. So it went into the else block which has an alert with "response.error". This is where we get the "undefined" alert. I checked response.success and it is undefined also.

I could take out the alert, since my signature still uploads, but it's something to look at.

Posted: **Thu Nov 15, 2012 5:01 pm**

Hi Paul,

Unfortunately, I can't reproduce this problem. When I try a signature upload, it works fine without any error. When I deliberately create an error, I get a meaningful message (not "undefined")

Does it matter which browser/device you use? Do you have the same problem with all of them?

Posted: **Fri Nov 16, 2012 9:06 am**

I tried it on the latest versions of Chrome, Firefox and on an Android tablet with Ice Cream Sandwich. I'm getting the problem with all of them.

In Chrome's JavaScript console I'm getting this error message: Refused to set unsafe header "Content-Length"

Posted: **Fri Nov 16, 2012 10:47 am**

I'm definitely not having this problem on Chrome on the PC.

It sure sounds like you have a mismatch between your "runtime.js" and your server-side code. Are you absolutely certain that they match each other?

Profound Logic Forums

Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading

Re: Signature/Camera image not uploading