Nabeel

Everything follows the Laravel way of doing things, so it uses routes and controllers. https://laravel.com/docs/7.x/controllers Routes all all defined in what are called Service Providers. The RoutesServiceProvider is here: https://github.com/nabeelio/phpvms/blob/dev/app/Providers/RouteServiceProvider.php Controllers are all located in this folder: https://github.com/nabeelio/phpvms/tree/dev/app/Http/Controllers You can lookup the route and see exactly which controller and method it maps to. I believe in that case, it maps to For SimBrief, the definitions are here: https://github.com/nabeelio/phpvms/blob/dev/app/Providers/RouteServiceProvider.php#L78 Which are all map to these methods: https://github.com/nabeelio/phpvms/blob/dev/app/Http/Controllers/Frontend/SimBriefController.php

Yes, I just mean if you're changing the DocumentRoot to phpvms, it should point to the public folder. Same thing for the webserver/vhost if you're running your own. Can I use your instructions on docs.phpvms.net? I'll add a section for xampp and link to this thread. Running Laravel in a subfolder is also usually problematic, so I don't recommend it. And thanks! I enjoy it and it's a fun project. Thanks for helping test and documenting/playing with some of this stuff.. There's a lot of edge cases I can't cover myself.

Don't transfer the files, everything needed is already in the public folder. The htaccess in the root actually tries to redirect to public. In short - using the public folder hides all of the files like storage/resources, etc, so they're not exposed to the outside. It's a security thing. Here's a good explanation of the public folder: https://devdojo.com/articles/explaining-the-laravel-public-folder

This sounds good. I actually would change the DocumentRoot to the public folder, so in your case, DocumentRoot "C:/xampp/htdocs/phpvms/public". URLs will work without having the public in the path

What did you do to make it work? I was going to suggest trying out beta 4 because there are a ton of fixes.

You don't need to do that... if you're doing a custom design, it should be in a new skin folder (which it sounds like it is). Otherwise, just copy all the latest files, and run `/update/`. I have to write this in the docs page, but that would roughly be it.

Yep, I wanted to release another beta in part to check the updater... I'm looking into it to see what's happening.

Yep, a lot of testing, some issues end up coming in. Just released another (hopefully last) beta. A ton of issues fixed

Yes, this is the vmsACARS application which will be released with v7

https://downloads.phpvms.net/phpvms-7.0.0-dev.tar.gz

Sounds like a php extension might not be installed/enabled. Do you have a screenshot of the first installer page with the requirements? Maybe I'm missing a requirement

Have you run the installer already? Are there already tables in the database? I've seen that happen if the install was aborted or there was an error, and there's stuff left over from the previous install. Try clearing the DB and then reinstalling

Yeah this is possible, the permissions of the `storage` folder aren't correct.

There is a "Share" button on that page for the error, can you share that link? Thanks

If you're using a subdomain, point the directory to the /public directory - http://docs.phpvms.net/setup/installation/shared-hosts#method-2-subdomain

Looks like it's a parser error with the backticks. Maybe post a bug report for Visual Studio Code or whatever the PHP plugin for syntax highlighting is

The easiest way would be to create a hidden field with the airline ID you want. Right now, there aren't custom registration fields, probably something I can add in after release

You changed the role for your own user away from admin? I need to block that from happening...

Looks like the latest install there worked. Sorry about the issues. You can try the latest dev, there's a fully packaged version at the link below. There's a lot of fixes, in the installer too: http://downloads.phpvms.net/phpvms-7.0.0-dev.tar.gz

Try the latest dev, I think that should be fixed.

Take a look at the container/docker-compose setup that's in the repository (in the dev branch). That might help

Is this with the latest dev version?

.env is env.php file. Are there more logs in the storage/logs folder that are pertinent?

The config looks right, have you looked in the storage/logs/laravel.log file?

Can you try the latest dev? Who's your host?