I am having a problem with Odoo 8 app interface to show full height after logging in successfully. I tried it in Mozilla Firefox, Google Chrome and Opera, they all show the same thing; but shows well in Internet Explorer.
See image link below.
http://i.stack.imgur.com/UW1mN.jpg
I was having same problem. Then I logged out and created a new db, it started working then properly. Don't know why it happened but solved this problem.
I have faced it many times. It usually happens while installing a new module or upgrading a module with following issue(s)
1. any error/mistake made in openerp.py file while mentioning path for any specific file such as "qweb XML" files.
2. Any error/mistake in defining path of a file which is included in module such as path for JS, CSS files.
3. Access right issue on a file. File may not have read permission for odoo user
If you have recently added a new module in Odoo Addons, remove it from addons and then try, it will work.
Hope this Helps!
Related
I'm using latest version of Swagger in my ASPNetCore 3.1 project and debugging on latest version of Chrome. When I try to enter swagger page it sometimes not loading and i see an empty page. It looks like totally random. It solves after I refresh the page.
I saw these errors on console.
GET https://localhost:44389/swagger/swagger-ui-bundle.js net::ERR_HTTP2_PROTOCOL_ERROR
index.html:95 Uncaught ReferenceError: SwaggerUIBundle is not defined
at window.onload (index.html:95)
File in the error is random. Its sometimes a js file, sometimes a .css file. It changes.
If I publish this project on IIS and disable Http/2 support I never encounter this error.
Why?
You can try the following：
1.Check if all your controller methods have [http] tag. If they all do and still doesn't work go to step 2
2.In your configure function to ensure that you have app.UseStaticFiles(); If it still doesn't work go to step 3
3.Uninstall and reinstall swagger. If it doesn't work go to step 4 (Core Only)
4.If you are using Core Install Microsoft.AspNetCore.StaticFiles and reference it in your project.
I encountered the same problem, SwaggerUIBundle is not defined, and the problem is not on the web app that I'm developing but on my network. The problem was resolved after I switch to another network.
When I try to submit to the app store from xcode, I get this error for both Main~ipad.storyboardc and Main~iphone.storyboardc:
"ERROR ITMS-90029: "Storyboard file 'Main~iphone.storyboardc' was not found. Please ensure the specified file is included in the bundle with any required device modifiers appended to the filename."
I've looked at all similar questions posted to stackoverflow and tried their suggestions with no luck.
My app is for iphone ONLY, does not use storyboard, and runs perfectly well on all iphone simulators without errors.
Now when I go back to a snapshot of when the project ran well on simulators, the project no longer runs...I get error "Failed to instantiate the default view controller for UIMainStoryboardFile 'Main' - perhaps the designated entry point is not set?"
The problem was that I deleted the Main.Storyboard file from my project. I thought it would be OK to delete that file since I wasn't using it.
The issue for me was that I switched my supported devices from universal to iPad only. I had also changed the name of the Main.storyboard file but after I had updated the supported devices. So the Main storyboard file base name entry in the info.plist file was still Main.storyboard.
Deleting the entire row for Main storyboard file base name and leaving Main storyboard file base name (iPad) in the info.plist file fixed the issue.
Since your project is iPhone only just make sure to remove Main storyboard file base name (iPad) completely.
I have been following this guide on displaying website pages as an app (http://antonylees.blogspot.co.uk/2013/02/launch-website-as-mobile-app-using.html).
Everything works apart from trying to access a local HTML file as a fallback option when there is no internet connection. I have researched and tried multiple methods to try and do this without luck. The 'This app requires an internet connection' popup works fine, but when trying to load the local HTML file, I either get a grey screen or the 'Page cannot be found' message.
The suggested way is:
window.location="local/index.html";
I have also tried:
window.location.href ="local/index.html";
and:
window.open('local/index.html');
The 'local' folder is a sub-folder of 'www'.
Is there something specific to Windows Phone 8 that I am missing? Any other ideas?
I am using Visual Studio 2013 Express, The latest version of Cordova, and live debugging on a Nokia Lumia 820.
Solved! The problem was completely unrelated to Cordova etc.
I am new to MS Visual Studio and this was my first project using it. I noticed that the local HTML file I was trying to load was not showing in the Solution Explorer. I realised that I had created the file externally of MSVS. As a result I had to right click in the solution explorer and add an existing item. Once I had done that everything worked fine using the same code as in the tutorial. I am guessing that the compile process only includes files listed in the solution explorer.
Thanks for looking anyway! And at least I now know how to display code correctly in Stack Overflow ;)
I'm trying to get TypeScript source debugging working in Chrome, but I'm running into two specific and perhaps related problems.
The first is that the comment generated by the TypeScript/WebEssentials compiler that's supposed to identify the location of the source map file looks like this:
//sourceMappingUrl=MySourceFile.js.map
But Chrome won't read that file. It seems expect that the comment will look like this:
//# sourceMappingUrl=MySourceFile.js.map
If I manually change the comment to that, and refresh my page, then magically the references to all the .ts files show up as sources in the Chrome Developer Tools.
However, that leads to my second problem, as the files don't actually get loaded. The .ts source file that Chrome should be trying to download is http://localhost/MySourceFile.ts, but the one that it's actually trying to download is http://localhost/C:/source/web/MySourceFile.ts. That sort of makes sense, as the opening attributes of MySourceFile.js.map look like this:
{"version":3,"file":"tmp1523.tmp","sources":["C:/source/web/MySourceFile.ts"
But that obviously doesn't work with Chrome, as it interprets the source-map location to be entirely relative, and IIS (quite correctly) won't serve up any URL looking like http://localhost/C:/source/web/MySourceFile.ts.
So, with respect to these two problems, is it Chrome or the TypeScript source-map feature that's doing it wrong? And what's the recommended way of doing this?
I'm using Chrome 25.0.1323.1 dev-m, with TypeScript 0.8.1 and WebEssentials 1.8.5.
This is an issue with version 1.8.5 of Web Essentials (the version currently available from the Visual Studio Gallery). The latest nightly build (at time of writing http://madskristensen.net/custom/webessentials2012.vsix) fixes the problem and generates the map linkage correctly.
I have a Web application that is hosted locally on Websphere. In the application there is a link to a .doc file located on a windows server.
CIT
The link was been working for years, but suddenly stopped working on all computers on the network. When I click the link, nothing happens. I checked the files path and name, and nothing has changed. The interface is viewed using IE8.
Does anyone have any clues onto why this isnt working or where I can look to resolve this?
edit: i have just noticed that the file (CIT_.doc) has been saved in the same directory, could this have an effect on it?
I'd imagine one of the following has occured:
The file has been moved or renamed
The K: drive has been re-mapped or other wise modified to a different location
A popup blocker is tampering with the link (because target="_blank")
In other words you need to manually check that file location within explorer, you also need to try a different browser.
Also you need to change the link to:
CIT
See here for the reason, you may also need to URLEncode it.
It probably has something to do with security settings that your network administrator has recently setup, seeing as the m.edmondson's answer does not work. Try it in another browser besides IE.