I have a xpages application running on Domino 9.0.0 which we had upgraded now on 10.0.1FP4, the application is loaded in a SAP portal, it was working fine on older version but in internet explorer the Dojo buttons, Tabs dose not work though they work in Chrome & Mozilla. We had tried adding website rules with HTTP response headers with code 200,206 and 302 also added custom header with parameter 'X-Frame-Options' ALLOW-FROM https://achme.com. Still there is no luck, any pointer would be highly appriciated.
Dojo Version is 1.9.7
Related
After installing the XPages Extension Library v15 from openNTF.org the required way I get an 404 Error when previewing XPages in a browser. Previewing XPages in Notes works fine.
IBM states an issue that you need to check the Build Automatically in Project menu item of Domoino Designer to avoid 404 Error. But that item is checked.
What do I miss ?
Make sure you installed ExtLib on server too.
Restart task http on server.
Clean your project with menu Project/Clean. This way it gets rebuild completely.
If it's still showing 404 error then have a look at error.log file on server.
Update:
You pointed out in your comment that you use "Preview in Web Browser" without a server.
The local preview loads plugins from
<data-directory>/domino/workspace/applications/eclipse
Copy all ExtLib's features/plugins from
<prog-directory>/framework/shared/eclipse
into this directory and restart Notes Client & Domino Designer.
I have an authenticated website that hosts Excel spreadsheets. Apple users have been able to view those spreadsheets satisfactorily in Safari. But in IOS9, the .xlsx spreadsheets no longer display correctly, showing only the headers and none of the content. The relevant HTTP headers are
Content-Disposition:attachment; filename="sheet.xlsx"
Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
I can't help but notice that I have Excel installed on the iPad, and yet I'm viewing the document in buggy Safari. Is there a way to get my document from Safari to Excel, or a header I can set to allow this?
(Using iOS 9.1 and Excel, Safari finally displays an "Open in Excel" option.)
I also see this behaviour.
Opening xlsx files over SSL in Safari on iOS 9 only displays headers.
It works properly in Chrome and Dolphin on iOS 9 and Safari works fine on iOS 8 devices.
Edit: Using web inspector I was able to see that javascript and css files were being blocked.
Here are the warnings.
[Warning] [blocked] The page at [URL] was not allowed to run insecure content
from x-apple-ql-id://C18FD844-A305-415A-8096-90DFD8D43CA8/x-apple-ql-magic/Tabs.js.
[Warning] [blocked] The page at [URL] was not allowed to run insecure content
from x-apple-ql-id://018921C7-D074-4763-8838-E44E535A65F4/x-apple-ql-magic/Tabs.css.
And an Error
[Error] ReferenceError: Can't find variable: ReloadFirstSheetIfNeeded
Now we build a site with sharepoint 2013. Per our customer requirement, we need to support IE8. But my develop environment is IE11(in windows server 2008R2), so I decide to degrade my IE version.
In the beginning, I can use IE11 to access the website which I created in share point. But after my degrading operation, strange things happened: I enter the url in the IE8, it is loading... seems every thing is fine, I can see the background pictures be downloaded in the browser,but few seconds when it loading completes(I guess), it redirects to the 404 error page.(normal page flash to the 404 error page) And I tried to use Chrome to visit this site, every thing works.
I also set the IE security level to low, and trun off IE ESC(enhanced security configuration), it doesn't work.
BTW, the IE8 can access the url: myMachineName/_layouts/15/start.aspx#/SitePages/Home.aspx
So I guess I need to add or change some configurations in the website which I created in the sharepoint to fit IE8.
Many Thanks!
The xPage app was developed and compiled using 851 designer by someone else...
Were suppose to be used inside Notes Client.
Only two of my users when they open the xpage app in the Notes Client 853FP5 standard config on win7 everything displays and no error however it wasn't in xpage UI, instead it looks like some domino view being loaded in a web browser. but all xpage buttons and links are working and displayed. Just the not xpage UI.
If I try to load the app in a web browser, all seems to load fine.
Any ideas? as no other user has got the same issue. If it is an issue with win7, then they are all on win7 though, Or any suggestions in terms of where to start from to debug this issue?
Many thanks
You mention that it's not the "xpage UI" but that "xpage buttons and links are working". It sounds like a caching issue for the CSS files. Try the keyboard shortcut Ctrl-Shift-Delete to clear the local cache.
Source: http://ypastov.blogspot.dk/2013/08/xpinc-clearing-cache.html
I have a web site and IE8, IE9, and IE10 always worked great using IE=EmulateIE7 mode in HTTP header response from IIS/7, but this mode does not seem to render properly in IE11.
The page does not render or behave properly in IE11, although it works fine in EmulateIE7 mode in IE8 through IE10.
If I open F12 tools on IE11, I see the document mode is "7."
The only way to make IE11 working properly is adding manualy the domain to compatibility view mode, then it works great; but we cannot ask all users to manually activate compatibility view for our domains.
How is possible to force IE11 to render as IE7 without adding the domain to the list of compatibility web sites ?
Many thanks to any help !!!
I've been working on this the last few days and there's some bad news, it works, but in order to make it work, the user must add the URL/Domain of your site to the "Compatibility View Settings" of IE 11.
In other words, you can't force the browser to render in compatibility mode without the explicit acceptance of the user.
You will find how to configure it here:
www.windows8core.com/how-to-view-and-configure-compatibility-settings-in-internet-explorer-11-of-windows-8-1/
I have been able to get this to work if I add the X-UA-Compatible header in IIS itself. Not sure why it doesn't work when added to web.config