When I download "Latest stable release: 1.28.16 (2015-08-18)" from here the documentation is not working. By clicking on \openui5-sdk-1.28.16\index.html the page opens up with empty content.
With older versions I also had non working offline documentation, the navigation page was showing, but the "details pane" was empty.
Is it only with me (using windows 8.1 and chrome Version 44.0.2403.157 m) or is this something general?
It is related to the browser security when index.html loads its resources (Same-Origin Policy)
So you have two options:
deploy the content on a (local) web server (as already pointed in the readme.txt) and open the index.html via http (for instance http://localhost:/openui5-sdk-1.28.16/index.html>)
run your browser with disabled web security and directly open the index.html
Related
I have a brand new TYPO3 10.4 install with a bootstrap sitepackage.
My page tree is this
Home
-> Building Management
--> Building Rules
Home shows fine, but all of the lower pages throw a 404 using the speaking url's, even from autogenerated links in the menus. I can still navigate using index.php?id=2, but this is not enabled at all by default.
If I set the language link to /en/ (rather than /) then no pages work, not even the home page.
I built the same site on my development server with the same version of typo3 and the same site package and it works as expected, just not on the production. Any idea where to look for a solution? Here's a pic of the site pagesites-page
The .htaccess was a clue. What appears to have happened is that the .htaccess file was not updated during the TYPO3 install. We copied one from another working install of 10.4.4 and that fixed it. I think there is a step in the install process that checks if there is a .htaccess file, and if there is then it doesn't copy or insert the required changes. Once we copied this across everything worked fine.
I have a project in Ionic 4, when I do ionic serve it runs at localhost:8100/
Now when it loads home page, the URL is localhost:8100/home, if I open contact page the URL becomes localhost:8100/contact.
When I try to copy the above URL and hit, then it says -
Sorry, this page doesn't exist. Please check the URL or go back a page.
What do I need to do to get this working?
Based on your comments this is happening because your server does not support fallback. So when you enter a url manually, the server is trying to find that page, but you only have index.html in your app because of Client side routing.
If the app uses the Angular router, you must configure the server to
return the application's host page (index.html) when asked for a file
that it does not have.
The configuration is specific to your server or cloud platform. You can check Angular deployment for more info.
This regularly should not happen and you can't do anything for this. Try to upgrade your ionic to the latest with nodejs since the error my be from currupted project creation. Then after update create a new project and it should go good.
I have deployed my GWT application on a JBoss server, which is located on a virtual machine. If I open Safari/Firefox/Chrome, clear the cache and then navigate to my app: the app fails to load! I just see a blank screen (the title is loaded).
I use SmartGWT and when I just httpfox to examine the traffic, I can see that most resources (images, javascript) is downloaded, but some SmartGWT js files seems to be hanging.
In the screenshot, ISC_core.js and ISC_Foundation.js has not been completely downloaded, and they never are. (It is not always these two files, it can also be different ones, and it changes everytime I retry).
Now, if I reload the browser my app loads perfectly and when I look in httpfox, the files that were not completely downloaded before, is now fetched from the browser cache.
If I clear the browser cache and try again: blank page and same issue.
Does anyone have a clue about what is causing this behaviour and where I should look to fix it?
Note: this only happens when I deploy on my remote virtual machine. If I deploy locally in the same JBoss server setup, I have no problem and cannot reproduce the above issue. Also no problems when I debug in Eclipse and use the Jetty server.
May be this is an Known issue ..Which is posted on Google groups .
As a side note enable gzip on your jboss also..please refer to this link to do that
I have developed a chrome extension and want to know how to host the .crx in github.
I also saw this that's similar to mine (i.e. hosted in github):
https://github.com/franverona/MarkAsRead-Chrome-Extension
but the installation instructions seem complicated (haven't tested even that will work).
Q:
Has anyone succeeded in hosting .crx in github and have users install it with just a click?
(basically satisfying header constraints given by google at
http://developer.chrome.com/extensions/hosting.html)
ok, so this is what ended up:
Hosting in our own server doesn't work in latest versions of chrome. It directed me to google chrome's support section stating that they have disabled it altogether for security reasons
So the only option left (as i didn't want to host it in chrome web store) is manual install - users have to download my extension and drag and drop it onto chrome://extensions page
I chose google code (downloads section) as compared to github for hosting my .crx because in github download is not straightforward.
More details: in github user has to download in 'raw'. It may not be straightforward for users - if they say 'Save as' against .crx without going to raw view then they end up getting git mashed up file (in other words not the original file we upload)
The Google Earth browser plugin apparently no longer requires a key and it's impossible to request one.
The problem is when I run their sample code (Chrome 18 and FireFox 10) found here I get an error message:
The Google Maps API key used on this web site was registered for a different web site. The developer of this web site can generate a new key here.
When I check their plugin page it tells me:
Good news, you already have the Google Earth Plug-in installed. (Version 6.0.3.2197)
So no key is required, but when I try to run the code sans key I'm told to get one, and I can't because Google has removed the ability to request one or download the update. I read online that 6.2 is the newest version but the key has not been required since 6.
Any advice is appreciated.
After trying a force refresh, emptying the cache, and upgrading the browser, Google Chrome still wouldn't allow my example that doesn't use a key to work. I've figured out how to fix the issue.
The problem was that Chrome wasn't automatically updating the Google Earth browser plugin, regardless of the browser. Additionally, their plugin page confirmed I had an old version (6.0.3) but wouldn't allow me to manually update either. So I deinstalled the plugin following these instructions, and then downloaded the newest version (6.2.2) and installed it. One final thing I had to do (on my MacBook Pro): the new plugin installed in Library in my user directory
~/Library/Internet Plug-Ins/
but to get it working correctly I had to move the "Google Earth Web Plug-in" file to the root's library and then restart Chrome.
/Library/Internet Plug-Ins/
The Earth API doesn't require a key - your sample code appears to be working properly. In case you do see an error message in the future, make sure that there's no key= parameter when loading the Google JS:
<script src="http://www.google.com/jsapi?key=ABQIAAAAwbkbZLyhsmTCWXbTcjbgbRSzHs7K5SvaUdm8ua-Xxy_-2dYwMxQMhnagaawFo7L1FE1-amhuQxIlXw"></script>
The keys are specific to a domain, so if you copy old sample code from somewhere (such as from the Demo Gallery, for example) you should just strip out the key=xxx portion:
<script src="http://www.google.com/jsapi"></script>
Despite it saying you don´t need an API key for Google Earth at various official places, your problem is solved, if you create one on https://code.google.com/apis/console (under "API access" and then click on "Create new browser key") and include in the jsapi include: <script src="//www.google.com/jsapi?key=yourkeyhere" type="text/javascript"></script>