-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS looping errors after successful login #12
Comments
Thanks for the report, I'll try to fix the issue ASAP. |
@armstrhb Ok, I'm able to reproduce the bug locally, sorry about not testing the application on tomcat 8 :(. I'll do a fix and a release. |
(the issue is present on tomcat7 too) |
Ok, the issue was caused by the fact that tomcat was serving the unprocessed template directly, bypassing the controller that was serving the root directory of the application. @armstrhb Thanks for the opening this issue. I'll do a 1.0.2 release. |
@armstrhb could you try the release 1.0.2: https://repo1.maven.org/maven2/io/lavagna/lavagna/1.0.2/lavagna-1.0.2-distribution.zip ? |
@syjer thanks for the quick turnaround, issue is corrected. Thanks again! |
@armstrhb Thanks for the bug report :). |
Hello Lavagna team,
We've set up Lavagna 1.0.0 (also tried with the new 1.0.1 published today) within Tomcat8. Went through set up successfully, but after login, the javascript console logs are spammed with the following error (as if through loop):
I followed http://help.lavagna.io/ to setup the environment, and accepted the proposed URL for the base URL. Some googling (link) (link) suggests that this is angular shutting down the history push, thinking it's cross domain; however the base URL chosen is accurate to the requests coming in for our local installation: http://techutilities.bcbssc.com/lavagna
The link that I'm redirected to after login is: http://techutilities.bcbssc.com/lavagna/, here's a screenshot:
Looks like something from a URL resources map isn't quick linking correctly.
The text was updated successfully, but these errors were encountered: