Opened 13 years ago
Closed 13 years ago
#351 closed defect (fixed)
Print widget doesn't work with IIS7
|Reported by:||hubu||Owned by:||hubu|
|External ID:||1282386||Operating System:||All|
Change History (13)
comment:1 by , 13 years ago
comment:2 by , 13 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 , 13 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 , 13 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 , 13 years ago
comment:5 by , 13 years ago
Sorry, it's my fault. I've updated now. Can any DM Solutions guys give some comments?
comment:6 by , 13 years ago
The patch looks ok for the localization changes now.
comment:7 by , 13 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 , 13 years ago
comment:8 by , 13 years ago
http://trac.osgeo.org/fusion/attachment/ticket/351/Fix_fusion_issue.patch is reviewed. The code looks good.
comment:9 by , 13 years ago
|Milestone:||Future → 2.0|
|Status:||new → closed|
looks like the patch has been applied in Fusion trunk, closing this issue
comment:10 by , 13 years ago
|Status:||closed → reopened|
This is a configuration issue with IIS no patch should be necessary.
comment:11 by , 13 years ago
|Status:||reopened → closed|
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.