Nabeel

That looks like a problem on my end, let me fix that. Didn't know that was a required dep for Intervention

Ah yes, 7.3 is fine. Try using this for the cron: cd /home/blusquar/phpvms && /opt/cpanel/ea-php73/root/usr/bin/php-cgi -d register_argc_argv=On artisan schedule:run

Awesome! I haven't really tested on Windows, so if there are other issues you come up with, post issues on the Github, that way is a little easier for me to track. Much appreciated!

Ah, yeah, create a ticket. You've switched to PHP 7.4 already in cPanel? What's the command line that phpvms shows?

Great to hear. I was going to mention what ProAvia did, the phpinfo page is useful.

There's no log because it's not running the cronjob. You have to ask your host the correct path to PHP for setting it up. I try to guess what that path is in the cronjob page. It would look something like: php /blusquar/phpvms/artisan schedule:run >> /dev/null 2>&1

Vangelis is correct, you need to enable those PHP modules. There's a list here, it should be complete: http://docs.phpvms.net/setup/requirements

Thanks, please add that one in Github as well. I fixed the first one you posted

Are you on a VPS? Or shared hosting? If you're on shared hosting, you're might be outgrowing it. If you're on a VPS, using php-fpm is best for performance, and there's some guides out there on tweaking it for performance.

It was causing a lot of issues so I had disabled it, but it's still enabled in some places. I have to look at re-enabling, I think I fixed most of those issues This is right, it will only allow what's marked as OK in $fillable. But you always have to have $fillable set, if it's not there, it won't get filled (got bit by that a couple of times). For example with Frontend/PirepController::store(), I use $request->all() We'll need to see the code for the store() method and also what the model looks like.

Hey, if I understand correctly, the expense is being applied for every airport, not just the arrival? Can you add a bug in Github? Are you able to duplicate it on the demo site?

You have to set a name for the route with ->name("admin.update"); and then call it with "staff.admin.update". If you look at the installer module you'll see it. I thought it defined route names automatically but only for resources

There's also a YAML command line importer which I'm planning to expose in the admin panel at some point, but it can be a little dangerous. It's how the data seeder runs too.

What problems were you having with the importer? I'd like to fix them before a release, esp since there are multiple legacy versions, I know there are some things that might have been missed. It was tested a lot, someone's import took something like 6 hours but it got done heh

Try now

Post in this thread: https://forum.phpvms.net/topic/25447-add-on-acars-software-for-phpvms-version-7/

Auto update isn't working. You need to manually update which I put in the other thread

Manually update; just extract all the files over (delete the vendor folder first), and then go to /update

Yeah, there might be one more because of the auto-update error

Go to /update, or if you try to log in and go to admin, it will check if there are updates pending

There is a guide to developing addons here: https://docs.phpvms.net/developers/addons With a sample plugin created here: https://github.com/nabeelio/phpvms-module If there are issues, something is missing, or you just have questions about best-practices, let me know. Any addons that aren't created in this way will a) have a good chance of messing up someone's install b) get wiped out in an auto-update, and therefore, will be locked and removed until they're compliant. I know modification and addons are a huge draw, so I'm not trying to restrict that, and yes, the process is a little more complicated and there is a learning curve, but it's for long-term viability and the good of the ecosystem that these rules are going to be enforced. Your addon should also be submitted here: https://forum.phpvms.net/files/category/8-add-ons/ Thanks!

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