PageNumber-Error after Upgrade to 2011.3
PageNumber-Error after Upgrade to 2011.3
Hello everyone
We have upgraded our used Stimulsoft Libraries to 2011.3
Now there is an error in the web viewer:
The Page Number is not shown when using the one-page-view (the textbox is empty, you can use the buttons to navigate but the buttons are not disabled when you reach the beginning or end of the report)
In the WholeReport-View, we get a javascript-error, the field page number is not found when the viewer tries to deactivate it
This is what the IE-debugger shows:
pageNumber = GetToolElementById(webViewerId, "PageNumber");
pageNumber.disabled = true;
pageNumber is null
Our Viewer is placed in aspx-page which is nested as Iframe in an Ext-Net-Panel in another page. Both pages use MasterPageFiles.
It worked well with the last used version 2011.2.1011.0
Thanks in advance
We have upgraded our used Stimulsoft Libraries to 2011.3
Now there is an error in the web viewer:
The Page Number is not shown when using the one-page-view (the textbox is empty, you can use the buttons to navigate but the buttons are not disabled when you reach the beginning or end of the report)
In the WholeReport-View, we get a javascript-error, the field page number is not found when the viewer tries to deactivate it
This is what the IE-debugger shows:
pageNumber = GetToolElementById(webViewerId, "PageNumber");
pageNumber.disabled = true;
pageNumber is null
Our Viewer is placed in aspx-page which is nested as Iframe in an Ext-Net-Panel in another page. Both pages use MasterPageFiles.
It worked well with the last used version 2011.2.1011.0
Thanks in advance
PageNumber-Error after Upgrade to 2011.3
Hello,
Please check the latest prerelease build. In the release version 2011.3 we reworked the WebViewer component, and since the release we made some fixed of bugs.
Thank you.
Please check the latest prerelease build. In the release version 2011.3 we reworked the WebViewer component, and since the release we made some fixed of bugs.
Thank you.
PageNumber-Error after Upgrade to 2011.3
The error seems to be fixed in 2012.02.03. It works well in IE9
But now I see no reports anymore in Firefox (9 & 10) and Chrome (16). I see the buttons (Print, next page,...) but the report area is white.
I have also tried the WebViewerFx. it is shown in IE and Chrome but it is not loading in FF 10.
There is no java script error reported.
But now I see no reports anymore in Firefox (9 & 10) and Chrome (16). I see the buttons (Print, next page,...) but the report area is white.
I have also tried the WebViewerFx. it is shown in IE and Chrome but it is not loading in FF 10.
There is no java script error reported.
PageNumber-Error after Upgrade to 2011.3
Hello,
Strange issue. Please try clear your browser cache and check the version of the libraries, attached to the project. Also for testing please try to disable the caching on the server side, if it is enabled.
If this fails, then try to make a simple test page with the report viewer. If a simple page will work correctly, then send us the layout of your web page, or a simple project which reproduces the error.
Thank you.
Strange issue. Please try clear your browser cache and check the version of the libraries, attached to the project. Also for testing please try to disable the caching on the server side, if it is enabled.
If this fails, then try to make a simple test page with the report viewer. If a simple page will work correctly, then send us the layout of your web page, or a simple project which reproduces the error.
Thank you.
PageNumber-Error after Upgrade to 2011.3
It seems to work with simple pages. Our page structure is quiet complex and we are using Ext.Net-Components. I'm trying to isolate the areas which cause the error and will post them then.
PageNumber-Error after Upgrade to 2011.3
It seems the report is not rendered on page load (Only with CTRL+F5) when the viewer is nested in an Ext-Net-Panel:
This worked in the old version of the viewer. We did not change the version of Ext.Net.
Code: Select all
PageNumber-Error after Upgrade to 2011.3
Hello,
We have reproduced this error and try to fix it within a week.
Thank you.
We have reproduced this error and try to fix it within a week.
Thank you.