I'm new to ember and doing a introductory tutorial to build a simple app. When I create a new app and start server, I try visiting the localhost page (http://localhost:4200/) in my browser but the page is blank. The browser window title is of my app name but there is no "Welcome to Ember" text as their should be. Also the ember inspector says "Ember application not detected!" although the little ember icon appears in the address bar of Firefox indicating that there is an ember app.
I have tried to restart the tutorial 3 times now and come up with same results. I have followed all set-up steps provided here. The only thing I did different or in addition to the turorial is I had to run sudo chown -R $USER /usr/localbecause of permissions issues.
All I have done so far is install node, npm, bower, ember-cli 2.2.0-beta.2., and then run these few commands:
ember new ember2-blog
cd ember2-blog
ember server
The terminal gives me a "Build successful - 7016ms." message but I go to http://localhost:4200/ and see the blank page... The inspector says "no ember app detected". Seems like I'm missing something simple but can't figure it out. Is it something to do with permissions? Please and thank you for your help.
This is a bug due to a new version of jQuery. For now you can change the following line in your bower.json file. Then run bower install and it should work.
"jquery": "^1.11.3",
to
"jquery": "1.11.3",
A new version of ember.js is imminent which should fix this.
Related
I have installed openedx using Native installation method. Now I want to change the default logo. As a test, i removed the logo from the folder /edx/app/edxapp/edx-platform/lms/static/images.
But when i open the localhost, its still there. (lms view).
In inspect view, the logo name appears as /static/images/logo.b6c374d66d57.png.
The same operation when I perform in devstack, The logo changes successfully.
What am I missing?
Since I am using the default theme, I think I don't need to configure anything regarding theme customization.
Ok, I am posting the answer as I figure it out. Maybe helpful for someone.
The application was service data from cache and I had to recompile the theme again. Following are the steps to compile the theme.
sudo -u edxapp bash
source /edx/app/edxapp/edxapp_env
cd /edx/app/edxapp/edx-platform
paver update_assets lms --settings=aws
If there are changes in cms contents, execute
paver update_assets cms --settings=aws
I am new on Ionic Mobile application development, so I am trying to POST data from Ionic app. Whenever I have run the app in browser using
ionic cordova run browser
It display below issue in console,
Native: tried calling HTTP.post, but the HTTP plugin is not installed.
Install the HTTP plugin: 'ionic cordova plugin add cordova-plugin-advanced-http'.
I have installed same plugin using terminal but terminal give warnings as its already installed.
Please Suggest.
Based on this https://ionicframework.com/docs/native/http/ you also need to run
npm install --save #ionic-native/http
and referencing it correctly in your app, please take a look at above link
Also for running app in browser try below command
Ionic serve
See https://github.com/ionic-team/ionic-native/issues/1975
The issue appears to have been fixed but there might be a lag in updating npm
I hade the same problem and I solve it with uninstall and reinstall the plugin
Uninstall plugin completely
ionic cordova plugin remove cordova-plugin-advanced-http
npm uninstall #ionic-native/http
and reinstall it
ionic cordova plugin add cordova-plugin-advanced-http
npm install #ionic-native/http
The Native Http plugin is the only way to handle the CORS from the client-side.
The way I see your problem, there might two possible fixes
Check whether the plugin is called after the platform.ready().
Even after it, if doesn't work or show the same error then follow this method.
// Declare cordova as a global constant
declare const cordova;
// directly call the cordova pulgin using "cordova.pulgin.http"
cordova.plugin.http.post(apiUrl, {}, {},
response => {},
response => {})
I'm unsure why my ember does not start. When I type ember server, I see
PS C:\Users\lzc\Ember-Prototype> ember s
version: 0.2.3
A new version of ember-cli is available (0.2.7). To install it, type ember update.
Livereload server on port 35729
Serving on http://localhost:4200/
PS C:\Users\lzc\Ember-Prototype>
I'm pretty sure its not the outdated CLI, because it was working very well for the pas week. When I type ember build, it instantly reads 'Building...` then finishes. Normally my builds are 60 to 80 seconds. I can't identify whether this is a compile issue or settings flaw. Shouldn't Ember-CLI give an error message if something went wrong like this?
Has anyone experienced this before?
Can't run `--verbose', no command in CLI. Issue was when liquid modal tried to register transitions, one of the path strings was incorrect. No error messages given.
I have installed the plugin for 'ember-cli-blanket', using command:
ember install:addon ember-cli-blanket0
But when I run the tests using "http://localhost:4200/tests", nothing is loading I am getting just a blank page, no error in console also.
When I referred in some online tutorials, they asked to pass "data-cover" with the <script></script> tag. But no progress.
If i uninstall the plugin and run the tests it is working fine.
Can anyone tell what am I doing wrong or any more settings needs to be done?
I've been trying to use Ember CLI to set up a new ember install, but the process keeps dying when trying to install ember-cli-qunit. I'm relatively new to using npm, bower, and ember so maybe this could just be an issue with me being dumb. Here is the dump I get when running
ember new webapp
I've been working on this for a few hours and can't really figure out how to fix the issue.
Thanks in advance
You must have ran bower as root at some point, and that would've changed the permissions of bower's cache files in your home directory (as per the error in the EACCESS line). Simply changing the permissions back to your own user (as root of course) should fix the problem.
Because of similar sudo problems driving me crazy (and the system's nodejs package being dated) I switched my setup to nvm: node version manager which installs everything to my own home directory instead and I never need to use root again for node-related installations.