-
Posts
8141 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
phpVMS Resources
Downloads
Posts posted by Nabeel
-
-
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.
-
17 hours ago, web541 said:
No, the _token is the CSRF token so that's not stored in the database at all. Just realised that the CSRF token has been disabled (not sure why), so if you have anything to do with @csrf or _token in your form just remove it for now.
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
12 hours ago, web541 said:How are you handling the form data in your create() method? Are you using $request->all() by any chance? If you are then that would be why the _token is showing as it's part of the request (as you already know). From my understanding, if you are going to use $request->all() you should specify your fields/column names that you will be using as part of your $fillable property on your model. Like this
https://github.com/nabeelio/phpvms/blob/dev/app/Models/Airline.php#L34
That way (at least from my understanding), by using $request->all() you are only allowing the fields you have specified in $fillable to be modified in your database, so you are protected from anyone adding a hidden input field into your form for example. This will also allow you to use it without getting that '_token column not found' error as it's not specified in your $fillable property. But @Nabeel can confirm this.
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()
On 5/25/2020 at 9:51 AM, nickkecooper said:Fixed! Thank you Now when I do it the correct way on the create.blade.php, I get this error Column not found: 1054 Unknown column '_token'. Should I do an except command on my insert?
We'll need to see the code for the store() method and also what the model looks like.
- 1
-
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
- 1
-
18 hours ago, LeonardIGO4036 said:
Hey,
phpvms 7 is built on Laravel, and I've taken a look at the DB tables. As you have guessed, the same import CSV files you used for phpvms v2/v5 wouldn't work. The documentation says that you will be able to do an import thought SSH Terminal using the following artisan command. Ik most of the guys are on TFDi hosting, and the good news is they support SSH Access via cPanel. So when you get phpvms7, all you gotta do is go to cPanel > Terminal > and enter the following command with your DB creds.php artisan phpvms:importer {db_host} {db_name} {db_user} {db_pass?}
more information here: https://docs.phpvms.net/setup/importing-from-v2-v5
On a side note,
There is this awesome tool https://virtualairlineschedules.net/ provides data (airports, aircrafts, schedules) which support phpvms7. The only thing left to actually import from your old VA DB is, Pilot Data & PIREP Data, which also can be imported manually
I've been working on Laravel projects for a while now. I created a custom VMS for a client who were running on phpVMS earlier. It was fairly very easy to get all their data from the DB and put it into a format where it was accepted by my VMS because the database tables were much similar. So, the possibility that it can be done without using the Terminal in phpvms7 is still there. I've attached a screenie for reference from when I tried to export data from a phpvms v2 based VA to a custom Laravel VMS.
In conclusion, the odds are that there would be a full featured import tool when phpVMS is released, so we'll cross that bridge when we get to it!
Cheers.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
- 1
-
-
On 5/20/2020 at 4:58 PM, LuxuryCEO said:
cant seem to update mine to beta 4
what I get when I do try to update >> https://flareapp.io/share/dPbWyg7k#F61
Auto update isn't working. You need to manually update which I put in the other thread
- 1
-
36 minutes ago, LuxuryCEO said:
how can I get from beta 3 to beta 4
Manually update; just extract all the files over (delete the vendor folder first), and then go to /update
-
16 hours ago, LuxuryCEO said:
would that be beta 4
Yeah, there might be one more because of the auto-update error
- 1
-
14 hours ago, macofallico said:
LuxuryCEO is the ebst! its solved but the problem in the database user and airline creation in step 3 is there.
I have the site working, but how do i test and install the BETA4,
1- download the zip,
2-decompress and in the subdomain folder, (using cpanel)
3-do i need to do anything else?
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!
- 3
- 1
-
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
-
On 5/9/2020 at 10:18 PM, LuxuryCEO said:
What did you do to make it work? I was going to suggest trying out beta 4 because there are a ton of fixes.
-
18 hours ago, anushpatel said:
Hi everyone!
I just saw the latest version has been pushed but the updater seems to be broken:
GuzzleHttp\Exception\RequestException
cURL error 3: (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
So I have already started building a custom design etc on Beta 3, previously I created a fresh install and transferred everything over from another VM but the database import took forever. Is there anyway to update the version without having to delete all the current files and/or having to change any data? I was thinking of manually importing the GitHub file and then running the installer but I don't know if my custom skin and existing DB would break it?
Thanks!
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.
- 1
-
Yep, a lot of testing, some issues end up coming in. Just released another (hopefully last) beta. A ton of issues fixed
- 1
-
18 hours ago, LuxuryCEO said:
think he ment where is this module
Yes, this is the vmsACARS application which will be released with v7
-
On 5/6/2020 at 1:25 PM, LuxuryCEO said:
hi guys just to let you know this link doesn't work >>
http://downloads.phpvms.net/phpvms-v7.0.0-dev.tar.gz
comes up with this
<?xml version="1.0" encoding="ISO-8859-1"?>
<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>phpvms-v7.0.0-dev.tar.gz</Key><RequestId>62AC3C3EDD5FED54</RequestId><HostId>tXu81xrXRNfx0HsoA91+vjllnHlsiIjJNEeUcn2+VMeQ2+rU/bSoliwKdb24pv46PM/3gkdzEJQ=</HostId></Error>
[SOLVED] Install error
in Support
Posted
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