We have an issue with the HTML produced from the Oracle BI publishing engine, in that the pages are not rendering properly in IE6. The issue is that of tables having their row heights hard coded, meaning that cells with multiple lines of text in them only display the first line, despite the fact that all data is present in the HTML source.
To clarify, all pages look fine when viewed in IE7 or above, and Firefox. The upgrade to IE8 is on its way (thank god), but not for another 6 months or so, so we need to find a temporary fix if possible.
Firstly, does anybody know if it is possible to enable some kind of IE6 compatibility mode on Oracle BI publisher through the Java APIS? (a long shot really I know).
Secondly, the transformation produced by the Oracle BI templates is an XLS-FO style sheet. Our plan B here is to manually edit this file to produce the desired output. I would assume it should be possible in here to try and set the heights of rows to be auto decided (or just not fixed), but so far to no avail, with the default "just one row" being displayed again.
Does anyone have any experience / advice with either Oracle BI and IE6, or tables in XSL-FO with cell heights expanding to match content in IE6?
Any help / advice is very appreciated!
The solution to this issue it appears, was to downgrade the Oracle BI Publisher version that we were using. We are currently using version 11g, which according to documentation supports IE7 and 8, not IE6.
Version 10.134 on the other hand supports IE6 and 7. Downgrading the Java APIs to this version resulted in HTML that was IE6 compliant. Whilst in normal circumstances this would not be ideal, for our scenario 10.134 was already being used elsewhere in the business, and was proven to be stable in a live environment. In an ideal world, IE6 should have been updated, but unfortunately you can't win them all!
Related
I am trying to open tables from wizard in forms 6i and database 19c , I can connect by using user name and password in forms 6i but when I select the table from wizard it shows this error ,
actually I need to upgrade my old system and build new system in oracle APEX but during this time I need to continue using old system .
How to fix this error when select the table it show this error
ora-03115 unsupported network datatype or representation
Basically, it means that combination of client software (Forms 6i) is too old to successfully work with a new database (19c).
Forms 6i was released along with database version 8, back in 1997. Oracle database 19c dates from 2019 which means that there's over two decades difference between them. A LOT has changed during that time. Michael Ferrante from Oracle says that
Forms/Reports 6 was never certified for use with ANY database newer than Oracle 8.1.6.
and can't stress enough how important it is to upgrade.
OK, you're switching to Apex, but you can't expect that really old Forms application to work correctly with a new database. Perhaps you should have kept your old database and use it with Forms application, while you'd develop an Apex application using new database version. Once you're done, you'd migrate data from old database to new.
Meanwhile: what is SYS_USERS table description? Does it, by any chance, contain a TIMESTAMP column? If so, that might be cause of your problem. If you don't really care about fractional seconds, see if you can modify that column's datatype to
DATE. Don't alter the original table yet - first create its "duplicate", just switch timestamp to date datatype and try to access such a table from Forms. If it works, consider altering sys_users.
There are numerous reasons why old Forms/Reports versions cannot use DB versions newer than 8.1. The most significant one is that beginning in DB 9 (I believe), the ROWID format was changed/lengthened. Before Forms internally uses ROWID and expected this ROWID to be of an expected format, the change to it made newer DBs incompatible with Forms. Again, this is just one of several changes impacting the use of old Forms versions.
Move to Apex? Seems a better and generally easier approach would be to simply upgrade to a supported Forms version. Once upgraded, begin to take advantage of the many new features introduced since 6.0.8. In the planned coming versions of Forms, there are many new features expected.
Because your Forms application code (within the modules) mostly cannot be repurposed in Apex (or any other technology), what seems to work best for many other users is to invest some effort into moving Forms to a current version and introduce new features where appropriate. As new business requirements arise, carefully consider which technology is best suited for that requirements. As needed integrate all the technologies together (e.g. Forms and Apex can be integrated/share information).
You cannot build a house with a single tool. It often takes many tools to achieve all the requirements appropriately.
Just upgraded to Windows 10. Switching to SOURCE mode in CKEditor crashes the entire browser and cases to refresh. No way to access source.
Microsoft Edge is a new product, and so far, it has quite a few issues that need ironing out.
CKEditor introduced initial Edge support in version 4.5, but there are quite a few bugs that were reported by us to Microsoft and that need to be fixed on their side.
The issue that you describe was actually reported by us, too, you can find it here: https://connect.microsoft.com/IE/feedback/details/1577449/edge-browser-crashes-when-using-ckeditor-toggling-from-wysiwyg-to-source-mode
Anyone interested in having this fixed is probably most welcome to comment the bug report to highlight it's a show-stopper for many users. Sorry about any inconvenience caused.
As MicroSoft says this problem has been solved after update 1511.
Check this link: Browser crashes when using CKEditor (toggling from WYSIWYG to source mode)
I want to know, how to make Oracle Forms 10g or 11g more accessible to people with disabilities. For starters, is Oracle Forms compatible with web browser zoom level, if not, is there some way to dynamically change size of Forms items? I tried to search in the internet, but there is so little information about that.
You can try the ClientDPI parameter in webforms.cfg
I've used it to fix form size (you could say "zoom level") on linux and mac clients. It's not user configurable, but you could offer your users several zoom options through the calling url
Check this out: http://docs.oracle.com/cd/E15523_01/web.1111/e10240/configure.htm
Hope it helps.
This works like a charm: https://discussions.apple.com/thread/8563562
i did not have to install the browser in mention, i used an old mozilla firefox version and looks nice and crispy..ttthe key is the script's terminal.
i changed the clientDPI too to adjunt the size a little.
Oracle Forms runtime 10
Background Info
I'm currently searching around for ways to add support for older versions of Internet Explorer for an existing project that uses Protovis (and therefore the tag). My searching around has led me to two main places:
http://multimedia.journalism.berkeley.edu/tutorials/protovis-internet-explorer/
Touches on the Chrome Frame plugin as well as SVGweb
https://gitorious.org/protovis/jloves-protovis
Seems to be an integration of Protovis with SVGweb
So far, I've downloaded the examples from each of these and opened them up in IE8 and have had no success whatsoever. The exact version of the IE is 8.0.7600.16385 and is running on a 64 bit Windows 7 Machine, and for the sake of SVGweb, the Flash version installed is 10.2.152.
The question(s)
Since I've had no luck making any of these work, I'm wondering if I'm doing something wrong. Can anyone verify that the examples found in http://multimedia.journalism.berkeley.edu/media/upload/tutorials/protovis/protovis-ie.zip and/or https://gitorious.org/~jlove/protovis/jloves-protovis/commits/master work in IE8? If not, is there any other way (preferrably server side, but if there is a plugin that users can download and install for IE8 that would be okay too) to make protovis work on older IE versions?
Thank you for any help or advice!
I never had any luck with either of those solutions either. However, datamarket.com have recently come up with a drop-in shim available from http://blog.datamarket.com/2011/06/22/protovis-support-internet-explorer-8/ which worked right out of the box for me. The only drawback is that interactive aspects of your visualisation may not work in IE using the shim - I had some drag-select functionality that I had to re-implement with sliders under IE.
I've just downloaded IE8, which replaced my IE7, but that's okay because IE8 has a 'compatibility view' which is meant to render pages like IE7 (not sure about the JavaScript).
I was wondering if there is a listing on the internet of all major differences a developer should know between the versions. I've searched Google a bit but haven't found a satisfactory listing.
So, what should I (or any other web developer) know about getting my site working optimally on IE8, and what are the major differences between the two?
I would start by looking here:
Internet Explorer 8 Readiness Toolkit
Differences between IE8 Compatibility View and IE7
IE8 Developer Resources
I don't think you'll find a comprehensive "gotcha" list of rendering quirks until more folks have it installed. There are a bunch of new features like Accelerators that you can develop to build new features into IE8. This looks like a good start.