-
Notifications
You must be signed in to change notification settings - Fork 240
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
infinite loading #33
Comments
Hello, So this EDIT: is this case also happening on demo or only on Your instance? Are you using it on chrome? There might be few differences and things to check:
|
I've just cloned the main branch, ran composer install, created user, logged in and added goal so I wonder what errors You got. In case of no errors in chrome dev tool - please check also the backend logs. |
okay so I am running it on Chrome, I cannot reproduce these issues on the demo, I tried creating a goal after restarting the server and making a goal works, the site seems to work fine except I have to reload it constantly from browser, I'll try the app_debug = true and see if I can find the issue. |
prod.deprecations.log I've provided logs here, I don't really understand whats going on too much, but it doesn't look great. |
Ok so, You have at least one problem to fix on Your side.
Exactly here
Please follow this point in my documentation:
|
Fixed the issue with mysql, didn't help. I have no new logs and no errors in CDT |
you can test out my instance here: division25.xyz with admin/admin maybe you can figure out what I can't. |
It wont let me in with Also please make sure that You got dev dependencies also installed, just make sure You got profiler package in the vendor and u got ENV dev with Debug on, this will help me. |
ah you are correct, it's mayhem/admin also as far as I can tell I do have profiler installed and debug on |
lI just created
Had no errors. My tests were ran in: Can You check that in Incognito mode then as well? Maybe You got some plugin which breaks something. |
okay, so from what I can tell, it seems to have something to do with going to goals, or dashboard, and them not loading correctly, looking in Doctrine
I see this, if I avoid goals/list and dashboard, the site works fine otherwise. |
Yeah that's what there is in the profiler but i also got this in my dev. This cannot be the issue as Your instance, my dev, my prod work fine for me. I thinks this has something to do with Your environment. Can You check it on other browsers but all in incognito/private? |
the same thing happens in incognito in Chrome. |
What version of chrome are You using? |
Version 83.0.4103.61 |
Ok, so I will check that out tommorow on windows. I have older version on Linux |
But now that i think. It still makes no sense. You are playing with demo with the same browser and there are no such problems. Anyway will think tommorow. This is interesting case. |
Like i thought - no sense as with latest chrome version works also fine on windows. I have actually other idea. |
No long running requests, but it seems like the requests get cut short, as if they don't load at all |
I assume that You still got 200 for that requests.
I got 3 more idea, - let's go with the most simple one:
there is also method responsible for showing it: Check if after hiding loader - it works correctly. Now if this will work, with hiding spinner manually then it will give me some hint. |
I mean, i had a one case... very rare thing where 1st ajax calls interfered and spiner was never shown for next call. Maybe this is case the other way around. |
it hides the loader and I can continue on normally. |
Ok so i will take a look in free time if I maybe have some case with Or there is indeed bug which returns 200, yet falls into some js |
is there something I can do in the meantime other than having to manually open console and send that command everytime? I plan on putting this on a touch screened pi that won't have a keyboard so it'll make it a bit difficult to paste it all the time |
Well there is a dirty temporary workaround solution for this, but You need to make sure if all works fine after that, cuz in worst case js might scream that dom element was not found and will break all front logic. Open file:
Go to line: Remove:
go to CLI and run: You can do this after turning env back to It might just work. |
that didn't fix the issue either. now the spinner is just stuck on the screen, but doesn't seem to do anything. I can still work around normally. |
This is really something, i just removed loader from dom on demo in dev tool and then opened some pages alongside with calling the hide/show and spinner is no more there. You are sure that cache clearing went fine? |
yes it did, I got no errors on my end |
just to compare, what version of node and npm are you using? |
Can't answer that question now as I'm on windows now and my dev is on linux - ain't going on linux today anymore. But node/npm should've nothing to do with this unless... You called |
there were some errors with nodesass, I was just curios if maybe that had something to do with it, it fell back to a binary and claimed all was okay, but I wasn't sure if that had maybe caused an issue. if you manage to figure out which node you are using let me know so I can double check against what I am using. |
Check this: https://volmarg.github.io/developer-mode/
good luck - im out for today. I wonder what's going on anyway. |
I have fixed the issue, it's node 12. I downgraded back to node 10, rebuilt PMS and the infinite loading is gone. |
Oh, so You did compiled the Output js/css anew with webpack. This makes sense now as i Also provide both bundles for production. |
Well if I compiled with node 12 it errors out, I did this several time just confirm, then switched to node 10 and did it a few more times and it work every single time I tried it. It seems a couple packages either aren't compatible with node 12, or it's just one that messes up the rest of the build. Either way I'm closing this issue, and I'd like to thank you for taking so much time to try to help me figure it out. |
hosting my own instance, for some reason when I open a new page, it seems to load indefinitely, followed install instructions, and if I refresh the page, the loading circle goes away, and I can use the site normally, but I can't seem to recreate this on the demo site.
EDIT: I cannot use the site normally on some pages, such as the goals page, I cannot add a new goal.
is there a difference between using a release and using a standard git clone?
The text was updated successfully, but these errors were encountered: