[Mifos-developer] newcomer - unable to load community app
344 views
Skip to first unread message
Eyal Elkevity
Mar 30, 2015, 5:41:46 PM3/30/15
to mifos-d...@lists.sourceforge.net
Hi all, I'm trying to install mifos. I've followed all the steps for installing the community app, and starting it using "grunt serve" or by loading the index.html directly. both result with a page "stuck" on the "loading mifosx" rotating logo.
I've encountered this post https://mifosforge.jira.com/browse/MIFOSX-1635
and there it was recommended to post the log. The guy that originally posted there somehow got his problem to disappear, but mine is still not working. so here is the log, maybe someone can help me out...
Thanks!
Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen.[Learn More] <unknown>
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create d3.js:479:4
Error: [$injector:modulerr] Failed to instantiate module MifosX_Application due to:
[$injector:unpr] Unknown provider: $idleProvider
createInjector/providerCache.$injector<@http://localhost:9000/bower_components/angular/angular.js:3544:19
bootstrap/doBootstrap@http://localhost:9000/bower_components/angular/angular.js:1299:20
newContext/context.execCb@http://localhost:9000/bower_components/requirejs/require.js:1635:24
newContext/Module.prototype.check@http://localhost:9000/bower_components/requirejs/require.js:871:43
newContext/Module.prototype.enable/</<@http://localhost:9000/bower_components/requirejs/require.js:1112:29
newContext/Module.prototype.emit/<@http://localhost:9000/bower_components/requirejs/require.js:1155:21
newContext/Module.prototype.emit@http://localhost:9000/bower_components/requirejs/require.js:1154:17
newContext/Module.prototype.check@http://localhost:9000/bower_components/requirejs/require.js:925:25
newContext/Module.prototype.enable/</<@http://localhost:9000/bower_components/requirejs/require.js:1112:29
newContext/Module.prototype.emit/<@http://localhost:9000/bower_components/requirejs/require.js:1155:21
newContext/Module.prototype.emit@http://localhost:9000/bower_components/requirejs/require.js:1154:17
newContext/Module.prototype.check@http://localhost:9000/bower_components/requirejs/require.js:925:25
newContext/Module.prototype.enable/</<@http://localhost:9000/bower_components/requirejs/require.js:1112:29
newContext/Module.prototype.emit/<@http://localhost:9000/bower_components/requirejs/require.js:1155:21
newContext/Module.prototype.emit@http://localhost:9000/bower_components/requirejs/require.js:1154:17
newContext/Module.prototype.check@http://localhost:9000/bower_components/requirejs/require.js:925:25
newContext/Module.prototype.enable@http://localhost:9000/bower_components/requirejs/require.js:1142:17
newContext/Module.prototype.init@http://localhost:9000/bower_components/requirejs/require.js:779:21
newContext/context.completeLoad@http://localhost:9000/bower_components/requirejs/require.js:1549:1
newContext/context.onScriptLoad@http://localhost:9000/bower_components/requirejs/require.js:1656:21
Sangamesh Nadagoudar
Mar 31, 2015, 6:24:52 AM3/31/15
to eyal.e...@gmail.com, Mifos software development
Hello Eyal,
Did you install Node.Js and restarted the system, before starting the other installations?
Please follow the steps in the provided link here:
If you are still facing the issue, please ping me on skype id:mifos.support
Thanks,
Sangamesh
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
Mifos-developer mailing list
mifos-d...@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer
Eyal Elkevity
Mar 31, 2015, 9:57:56 AM3/31/15
to Sangamesh Nadagoudar, Mifos software development
hi Sangamesh! thank you for the quick reply... well I don't remember If I restarted after the Node.js installation... there is no such instruction (if the installation itself requested a restart then I probably did one).
and after the npm install I recieved this warning:
npm WARN package.json mifosx-com...@0.0.0 No repository field.
I've proceeded to "grunt serve" anyways, but the same error occured.
question - is there any significance to the location of the folder? it's not directly on the root folder of the drive but rather in a nested folder that's below the root. maybe that's the problem?
thanks again!
Eyal
anyways, I restarted the machine and tried the grunt serve - same error. I redid the steps after the node.js installation which are:
npm install -g bowernpm install -g grunt-clibower installnpm installand after the npm install I recieved this warning:
npm WARN package.json mifosx-com...@0.0.0 No repository field.
I've proceeded to "grunt serve" anyways, but the same error occured.
question - is there any significance to the location of the folder? it's not directly on the root folder of the drive but rather in a nested folder that's below the root. maybe that's the problem?
thanks again!
Eyal
Eyal Elkevity
Mar 31, 2015, 10:18:48 AM3/31/15
to Sangamesh Nadagoudar, Mifos software development
Breaking news!!
found a post with a fix!
found a post with a fix!
after manually updating bower.json with the fix, grunt serve still didn't work. redid all the installations commands (written in the previous mail), and it worked!!!
thanks a lot!
Rohan Mahajan
Jun 25, 2015, 8:37:06 AM6/25/15
to mifosde...@googlegroups.com, mifos-d...@lists.sourceforge.net
Hello Eyal,
I am having the same error as you where all I can see on running the grunt serve command on node command prompt is the rotating LOADING MIFOSX... logo
The first time I ran the command the community app instance ran perfectly, but never after that. I've tried re installing both NODEJS and the dependencies as well as re forking and cloning the mifos x and community app repos
The problem seems to persist and the only error I am seeing is in the NPM INSTALL command, here it is :
The problem seems to persist and the only error I am seeing is in the NPM INSTALL command, here it is :
C:\Users\Rohan\community-app>npm install
npm WARN package.json mifosx-com...@0.0.0 No repository field.
npm WARN engine ka...@0.10.10: wanted: {"node":"~0.8 || ~0.10"} (current: {"node
":"0.12.2","npm":"2.7.4"})
/
> phan...@1.9.17 install C:\Users\Rohan\community-app\node_modules\karma-phant
omjs-launcher\node_modules\phantomjs
> node install.js
Download already available at C:\Users\Rohan\AppData\Local\Temp\phantomjs\phanto
mjs-1.9.8-windows.zip
/Extracting zip contents
Removing C:\Users\Rohan\community-app\node_modules\karma-phantomjs-launcher\node
_modules\phantomjs\lib\phantom
Copying extracted folder C:\Users\Rohan\AppData\Local\Temp\phantomjs\phantomjs-1
.9.8-windows.zip-extract-1435231199945\phantomjs-1.9.8-windows -> C:\Users\Rohan
\community-app\node_modules\karma-phantomjs-launcher\node_modules\phantomjs\lib\
phantom
Writing location.js file
Done. Phantomjs binary available at C:\Users\Rohan\community-app\node_modules\ka
rma-phantomjs-launcher\node_modules\phantomjs\lib\phantom\phantomjs.exe
npm WARN optional dep failed, continuing fsev...@0.2.1
-
> w...@0.4.32 install C:\Users\Rohan\community-app\node_modules\karma\node_modules
\socket.io\node_modules\socket.io-client\node_modules\ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
C:\Users\Rohan\community-app\node_modules\karma\node_modules\socket.io\node_modu
les\socket.io-client\node_modules\ws>if not defined npm_config_node_gyp (node "C
:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\nod
e-gyp\bin\node-gyp.js" rebuild ) else (rebuild)
karma-scri...@0.1.0 node_modules\karma-script-launcher
karma-html2js...@0.1.0 node_modules\karma-html2js-preprocessor
karma-firef...@0.1.6 node_modules\karma-firefox-launcher
karma-r...@0.2.2 node_modules\karma-requirejs
grunt-...@0.0.4-c node_modules\grunt-devcode
grunt-tex...@0.3.12 node_modules\grunt-text-replace
karma-...@0.1.5 node_modules\karma-jasmine
karma-juni...@0.2.2 node_modules\karma-junit-reporter
└── xmlbu...@0.4.2
grunt-cont...@0.3.0 node_modules\grunt-contrib-concat
grunt-con...@0.4.1 node_modules\grunt-contrib-copy
jshint-...@0.1.5 node_modules\jshint-stylish
├── text-...@0.2.0
└── ch...@0.4.0 (ansi-...@1.0.0, has-...@0.1.7, strip...@0.1.1)
grunt-contr...@0.3.4 node_modules\grunt-contrib-requirejs
└── grunt-li...@0.3.1
grunt-con...@0.5.0 node_modules\grunt-contrib-clean
└── rim...@2.2.8
grunt-stri...@0.2.8 node_modules\grunt-string-replace
├── ch...@0.4.0 (ansi-...@1.0.0, has-...@0.1.7, strip...@0.1.1)
└── as...@0.2.10
karma-chro...@0.1.12 node_modules\karma-chrome-launcher
└── wh...@1.1.1 (is-ab...@0.1.7)
grunt-...@0.5.1 node_modules\grunt-replace
└── fl...@1.0.0
grunt-...@0.3.4 node_modules\grunt-hashres
└── wre...@1.4.4
grunt...@0.6.2 node_modules\grunt-karma
└── opti...@0.6.1 (word...@0.0.3, mini...@0.0.10)
karma-coffee...@0.1.3 node_modules\karma-coffee-preprocessor
└── coffee...@1.7.1 (mkd...@0.3.5)
grunt-html...@0.1.18 node_modules\grunt-html-validation
├── col...@0.6.2
├── w3...@0.1.25 (comm...@2.0.0, superage...@0.2.0, super...@0.15.7)
└── req...@2.34.0 (foreve...@0.5.2, aws-...@0.5.0, q...@0.6.6, tunnel-agent
@0.3.0, oauth...@0.3.0, json-stri...@5.0.1, mi...@1.2.11, node-uuid@1.4.
3, form...@0.1.4, http-si...@0.10.1, ha...@1.0.0, tough-...@2.0.0)
grunt-cont...@0.5.0 node_modules\grunt-contrib-connect
├── connect-l...@0.2.0
├── op...@0.0.4
└── con...@2.7.11 (fr...@0.1.0, cookie-s...@1.0.1, pa...@0.0.1, q...@0.6.5,
by...@0.2.0, buffer...@0.2.1, coo...@0.0.5, de...@2.2.0, se...@0.1.1, formidab
l...@1.0.14)
load-gru...@0.4.0 node_modules\load-grunt-tasks
├── multi...@0.1.0 (mini...@0.2.14, lod...@2.4.2)
└── findu...@0.1.3 (gl...@3.2.11, lod...@2.4.2)
requ...@2.1.18 node_modules\requirejs
grunt-con...@0.5.3 node_modules\grunt-contrib-watch
├── tin...@0.0.4 (de...@0.7.4, faye-we...@0.4.4, nop...@0.0.3, q...@0.5.6)
└── ga...@0.4.3 (glo...@0.1.0)
grunt-cont...@0.2.7 node_modules\grunt-contrib-uglify
├── grunt-li...@0.6.1 (zlib-br...@0.0.1)
└── ugli...@2.4.23 (uglify-to-...@1.0.2, as...@0.2.10, ya...@3.5.4, sou
rce...@0.1.34)
gr...@0.4.5 node_modules\grunt
├── wh...@1.0.9
├── datef...@1.0.2-1.2.3
├── evente...@0.4.14
├── geto...@0.1.0
├── col...@0.6.2
├── rim...@2.2.8
├── as...@0.1.22
├── hoo...@0.2.3
├── grunt-le...@0.2.0
├── ex...@0.1.2
├── no...@1.0.10 (abb...@1.0.7)
├── mini...@0.2.14 (sig...@1.0.1, lru-...@2.6.4)
├── gl...@3.1.21 (inhe...@1.0.0, grace...@1.2.3)
├── lod...@0.9.2
├── coffee...@1.3.3
├── undersco...@2.2.1
├── iconv...@0.2.11
├── findu...@0.1.3 (gl...@3.2.11, lod...@2.4.2)
├── grunt-le...@0.1.2 (grunt-legac...@0.1.1, underscore.string@2.3.
3, lod...@2.4.2)
└── js-...@2.0.5 (argp...@0.1.16, esp...@1.0.4)
grunt-cont...@0.7.2 node_modules\grunt-contrib-jshint
└── jsh...@2.3.0 (console-b...@0.1.6, under...@1.4.4, mini...@0.4.0, s
hel...@0.1.4, c...@0.4.5)
karma-phanto...@0.1.4 node_modules\karma-phantomjs-launcher
└── phan...@1.9.17 (wh...@1.0.9, prog...@1.1.8, request-...@0.3.1, kew@0
.4.0, adm...@0.4.4, npm...@2.1.1, fs-e...@0.18.4, req...@2.42.0)
karma-c...@0.2.7 node_modules\karma-coverage
├── mini...@0.3.0 (sig...@1.0.1, lru-...@2.6.4)
├── datef...@1.0.11 (get-...@4.0.1, me...@3.3.0)
├── ib...@2.0.0 (wh...@1.0.9, estra...@1.8.0, mkd...@0.5.1, opti...@0.6.1, fi
le...@0.1.8, coffee...@1.8.0, lod...@2.4.2, esp...@1.2.5)
└── ista...@0.3.16 (support...@1.3.1, wh...@1.0.9, abb...@1.0.7, wordwrap@0
.0.3, no...@3.0.3, on...@1.3.2, mkd...@0.5.1, esp...@2.1.0, res...@1.1.6, async@
1.2.1, fil...@0.2.1, esco...@1.6.1, handl...@3.0.0, js-...@3.3.1)
ka...@0.10.10 node_modules\karma
├── d...@0.0.1
├── rim...@2.1.4
├── col...@0.6.0-1
├── grace...@1.2.3
├── mi...@1.2.11
├── q...@0.9.7
├── mini...@0.2.14 (sig...@1.0.1, lru-...@2.6.4)
├── opti...@0.3.7 (word...@0.0.3)
├── coffee...@1.6.3
├── gl...@3.1.21 (inhe...@1.0.0)
├── chok...@0.8.4 (recursiv...@0.0.2)
├── lod...@1.1.1
├── http-...@0.10.4 (col...@0.6.2, pkg...@0.3.0, opti...@0.6.1, ut...@0.2.1)
├── con...@2.8.8 (met...@0.0.1, ui...@0.0.2, cookie-s...@1.0.1, pause@0.0.
1, fr...@0.2.0, q...@0.6.5, by...@0.2.0, buffer...@0.2.1, coo...@0.1.0, send@0.
1.4, de...@2.2.0, formi...@1.0.14)
├── user...@2.0.10 (lru-...@2.2.4)
├── log...@0.6.26 (as...@0.2.10, under...@1.8.2, readabl...@1.0.33, semve
r...@4.3.6)
└── sock...@0.9.17 (base...@0.1.0, polic...@0.0.4, re...@0.7.3, socket.io-c
li...@0.9.16)
grunt-contr...@0.2.2 node_modules\grunt-contrib-nodeunit
└── node...@0.8.8 (t...@1.3.1)
Any help whatsoever will be much appreciated.
Thanks and Regards
Rohan
Eyal Elkevity
Jun 25, 2015, 10:03:06 AM6/25/15
to Rohan Mahajan, mifosde...@googlegroups.com, mifos-d...@lists.sourceforge.net
Hi Rohan!
The problem for me was a new version of a dependency called "ng-idle", which broke existing code. I needed to force the grunt to build with specific version of it and not the latest version.
inside bower.json file, look for "ng-idle".
for me it was "ng-idle": ""
meaning - no specific version.
change it to:
"ng-idle": "v0.3.5"
I think you might need to rebuild and stuff like that.
good luck!
Eyal
Eyal
Reply all
Reply to author
Forward
0 new messages