Open RKillinger37 opened 5 years ago
The 404 errors you see are to be expected. The entire admin panel is not completed, but the requirements to enter aircraft, routes and airlines (aviation groups) are there and ready to go. As for the other issue, check the latest release tagged https://github.com/FSVAOS/VAOS/releases/tag/2.0-1908
Also, huge monitor my friend.
Follow up question. Are you on the Discord? I might need to get with you on this to figure out the cause. That being said, 3.0 is quite literally around the corner to the point where I am starting to write off current issues because everything just got a redesign from the ground up. While it's not ready yet for you to start working with it, the 3.0 branch is up now on the repo. Expect all the juicy details in September.
I do have discord. My username is Kingsley#0054 and would happy to do a video share so you can see what i am looking at and try to work this out.
And yeah i wasnt able to access the aircraft, routes, etc. It just stayed on the same page with a rotating icon as though it was thinking about it, but never went to the pages.
Yeah I use a 50inch tv as my monitor lol
Can't wait to see what 3.0 looks like :) Will it still need the vendors folder?
Vendor folder is required as that's what contains the Laravel framework and its dependencies. I live in Phoenix with a typical M-F job, so basing my timing around that.
Ok, i don't work right now, so my time is pretty much available whenever. Just add me on discord when you get the chance.
Hi, I replaced the file using your instructions. Still same issue. Here's a youtube link to a short recording I did clicking on the admin links. https://youtu.be/ktNI1tgfICo Sorry about the blurryness. It's clear when I record, but youtube loves to not make things clear.
The links go nowhere or to a blank page or to a The Content You Were Looking For Was Not found page. Also the Settings and Modules links want to point to a charts.html page.
Originally posted by @RKillinger37 in https://github.com/FSVAOS/VAOS/issues/172#issuecomment-526061385