This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal



Jul 19, 2011, 12:34 PM
5 Posts

Re: "dojo cannot be resolved" errors in DDE with ExtLib Demo Db & fileSendr Db

  • Category: Extension Library
  • Platform: Windows
  • Release: 8.5.2
  • Role: Developer
  • Tags: Extension Library
  • Replies: 2
I totally agree, seeing these errors in DDE is a bit of a pain and can be confusing, however as you have already discovered the errors do not effect the application.
 
Make sure you upgrade to fileSendr V1.2.0.1 which has just been released on OpenNTF. It resolves a lot of issues with the file upload control on the majority of browsers. 
Jul 21, 2011, 7:35 PM
31 Posts
Thanks Declan ... and a couple of questions about fileSendr V1.2.0.1 then
Thanks for the heads-up about the new release of fileSendr.  I've installed it on the server & have given it a spin.  Congratulations on gritting your teeth & getting it to work in IE (still on IE 7 at this client location), which saves me from having to try to decipher it and do a macgyver on your beautiful app. Great job, and so timely (for me).
 
Now that I've done a little testing, I've got a couple of questions that maybe Dec or others in this forum can help me with or explain to me:
  1. At this client location, we're only using basic name-and-password authentication.  In fileSendr, the "login" link will bring up the browser_login.xsp, take my ID & password, not throw any errors, but basically ignore it, and leave me as "Anonymous".  Is there a way for me to get the browser_login.xsp to work with basic name-and-password authentication?  Currently I have to use "?open&login" to call up the stock ugly login pop-up to get authenticated.  Am I stuck with that method as long as we're only using basic authentication?
  2. When sending files, the custom message field is now using the CKeditor, and I find that if I include an image (because if it's possible you know some users will) the custom message part of the resulting email is replaced with:
Content-Type: multipart/related; boundary="==IFJRGLKFGIR11461UHRUHIHD" MIME-Version: 1.0 Content-Type: multipart/related; boundary="==IFJRGLKFGIR11461UHRUHIHD" MIME-Version: 1.0
whereas if I just format text, do lists, add emoticons, the resulting email will include the formatting (exclude the emoticon though).  Is this a server "thing", or do I simply need to adjust the fileSendr form field to store "content as RichText and Mime", or ???
 
Thank-you Declan for providing such a wonderful app to the community, hope you see this post.  If I don't receive any responses after a few days, I'll re-post this to the OpenNTF fileSendr discussion area.
Cheers,
Judy.
 
 

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal