Opened 14 years ago

Closed 14 years ago

#351 closed defect (fixed)

Print widget doesn't work with IIS7

Reported by: hubu Owned by: hubu
Priority: P2 Milestone: 2.0
Component: Widgets Version: 1.1.1
Severity: Major Keywords: Print widget
Cc: Browser: All
External ID: 1282386 Operating System: All
state: New


  1. Open the Flexible weblayout in MapGuide(The MapGuide configured in IIS7)
  2. Print.

Error: The Printable panel pop up but the panel is empty.

Notes: This problem only happens in IIS7.

Attachments (2)

Fix_Print_Issue.patch (3.7 KB ) - added by hubu 14 years ago.
Fix_fusion_issue.patch (2.8 KB ) - added by hubu 14 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 by hubu, 14 years ago

There is a defect in either JxLib or IIS7. The Print dialog is implemented as a Jx.Dialog. The content of the Jx.Dialog could be set either by:

Jx.Dialog.content = <html code>, or Jx.Dialog.contentURL = <content page url>

But, with IIS7, the Jx.Dialog.contentURL doesn't work. The server always get a 400 Bad Request error.

This submission just use the Jx.Dialog.content = <html code> to load the dialog content.

comment:2 by chrisclaydon, 14 years ago

Would someone from DM Solutions be able to comment on whether this is the right approach? Maybe it would be better to address whatever problem in JxLib prevents this from working correctly in IIS7?

Also, it looks like this dialog displays a number of non-localizable strings. Is that true?

comment:3 by hubu, 14 years ago

Thanks Chris for your comments!

Actually, I am not sure what's the exact problem with the IIS7/Jxlib. Maybe it's a compatibility issue for them.

For the localization issue, I have add these string to the en.json and using OpenLayers.i18n() to get this string.

comment:4 by chrisclaydon, 14 years ago

The current version of the patch does not use OpenLayers.i18n(). Do you need to update it again, or am I missing something?

by hubu, 14 years ago

Attachment: Fix_Print_Issue.patch added

comment:5 by hubu, 14 years ago

Sorry, it's my fault. I've updated now. Can any DM Solutions guys give some comments?

comment:6 by chrisclaydon, 14 years ago

The patch looks ok for the localization changes now.

comment:7 by hubu, 14 years ago

I attached new patch to fix fusion issue. The previous patch caused the fusion break. Because there are some errors in the en.json. In the en.json, we are not allowed adding any comments, and each string should be separated by comma.

by hubu, 14 years ago

Attachment: Fix_fusion_issue.patch added

comment:9 by madair, 14 years ago

Milestone: Future2.0
Resolution: fixed
Status: newclosed

looks like the patch has been applied in Fusion trunk, closing this issue

comment:10 by pdeschamps, 14 years ago

Resolution: fixed
Status: closedreopened

This is a configuration issue with IIS no patch should be necessary.


comment:11 by madair, 14 years ago

Resolution: fixed
Status: reopenedclosed

closing again

Note: See TracTickets for help on using tickets.