DisposableHero
-
Posts
690 -
Joined
-
Last visited
-
Days Won
111
Content Type
Profiles
Forums
phpVMS Resources
Downloads
Posts posted by DisposableHero
-
-
21 hours ago, Nacman said:
On a side note, I am keeping notes of files (and copy of files) that I have changed to to suit a need. So far succesful, nothing broke yet 🙂.
I assume keeping these notes and files is almost mandatory as when a theme or phpvms gets updated they will be over written, correct?
Follow duplication procedure... That simple it is, as explained in @ProAvia's post and is explained with examples in my readme files (subliminal message for reading the readme files) :)
Duplication logic works for default theme too, so whatever theme (or my module blade files) you are playing on , duplication saves your life ;)
Good luck and enjoy.
-
1
-
-
{{ Widget::latestNews(['count' => 3]) }} @widget('latestNews', ['count' => 3])Both will end up loading the Latest News widget with last 3 news you entered.
-
1
-
-
This is not related to an addon route or page (because DBasic.news is a page to display all news, not a widget to place somewhere)
What you need to do is, placing latest news widget (which is a part of phpvms v7 itself) to your home.blade.php.
You can check the default theme's dashboard/index.blade.php or disposable theme's dashboard/index.blade.php to see how widgets are placed in blades. Also Dispo Basic's readme file explains the general logic about placing widgets and configuring them. Even though it gives examples for its own widgets, similar calls can be used for default widgets (like latest news, latest pireps, latest pilots, livemap etc)
Good luck
-
1
-
-
12 hours ago, Nacman said:
New User here. If you are just getting into phpvms 7, as I am, the METAR and TAF don't work because aviationweather.gov replaced the API.
For METAR
If you edit AviationWeather.php you can replace this code ... with this code
Considering v7 is open source and can be improved by contributing via GitHub I would kindly suggest NOT to share core code changes here in the forum. Instead if there is an issue within the latest dev, opening a bug report and fixing it with a pull request is the best solution. So then when a new build gets generated (believe me, it is something urgent this happens pretty quick), everyone following/using v7 dev versions can benefit and it will be less risky compared to editing files manually (or advising that).
GitHub repository link is on the top menu
https://docs.phpvms.net/installation/updating
For best and quickest update (considering you do not have custom core file edits), replace item 4 with this;
4. Download latest dev (zip or tar.gz) package and upload it to your hosting via cPanel (or Plesk) file manager (or FTP), unpack using the same file manager and overwrite everything.
(if you have edited core files, you may need to apply your changes back but be careful, double check your changes and replaced files, like a config file or .htaccess a service etc.)
Safe flights
-
1
-
-
I think this can be done in blade... If you know the codes of awards for hours/pirep counts, then you can alter the foreach loop to show only them at top section (or left section) then the rest at bottom etc. (according to your placing wishes)
-
@Aharon You are still at phpVMS Classic (v2/v5) section, just look above your first post, it is clearly displayed there which subsection you are in... Also at forum main page try reading the section headers
And what is ASCARS ? As far as I know the airlines' you are flying for are using vmsACARS.
Good luck and God speed.
-
16 hours ago, Imanol said:
Hi @DisposableHero. Thanks for your reply. For "custom page" I mean those you can add from admin panel through the option config -> pages/links.
By the way, I could fix the issue with the tags like {{ $user->name }} modyfing them to {{Auth::user()->name}}.
Understood...
The problem is simple, those pages do not have a controller providing you data to use. This is why {{ $user->name }} fails but {{ Auth::user()->name }} works. To be able to use for example $flight, $user or $aircraft you need it to be prepared in the backend (controller) and passed to the view (that page you are visiting), otherwise you will get errors and those pages are not designed to provide you those details.
Same applies to translations and helpers (@lang is a helper), try using {{ __('common.profile') }} instead of @lang('common.profile'), it may work.
https://laravel.com/docs/10.x/localization#retrieving-translation-strings
Good luck
-
What is a "custom page" ? Do you have the user model accessible on that custom page you referring ? What does the error details say ?
If you can follow the "Getting Help" guide, it will be more easy for others to understand and try helping you out.
https://docs.phpvms.net/help#information-required
Good luck
-
Not advised (or accepted) but possible as long as you can keep track of every commit and/or every changed file.
In the end, what is published is the best and approved way to update, it ensures smooth installation of latest build and eliminates human errors. If you want to do it the hard way around, then so be it
But be advised, if something goes wrong in your process and you start getting strange results and/or unexpected errors, this method will reduce the support you will get back 
Good luck
PS: If it is only the vendor folder you are worrying about, it is easy to build it with composer commands and with proper entries in composer files if you are using additional packages on your server. You can even build vendors on a local server and then upload to your real server if it does not offer command line access etc.
-
"id" in v7 is the ident of a navaid, not an auto increment field like in v5 series... "TOMBI" or "FRA" as an example and name holds the name of the navigation aid, which is displayed on map popups.
Only "id" field is used to identify the data and process on flight maps. Nothing else in v7 uses that navdata table, it is only used to display flight maps which have pre-defined routes (do not mix it up with pirep maps please as they have all the data they need to be drawn on a map -acars position reports and imported route-) If the pilot does not import a route then a great circle gets drawn for "planned route", and acars position reports gets used for "actual route".
Example "Flight Map" with navdata being used;
Example "Pirep Map" with both planned route (imported from operational flight plan) and actual tracks (this hap has no connection to navdata table of v7);
Difference between "Flight Map" and "Planned Route" of a pirep can be seen clearly here. My Navdata is actual but that "flight" does not have any SID/STAR thus the map is drawn with airway connection only.
Hope this gives you a clue about the usage of navdata in v7
Good luck on the conversion
-
1 hour ago, filipet said:
I've uploaded this:
I have reinstalled phpVMS and now will be adding airports one by one, everything seems to be okay.
Sorry for bothering you.
I have a question. Are airports that are not added, going to be added automatically when filing a pirep via ACARS without biding?
Brgds.
Technically speaking adding 40k+ airports or any number should not affect the latest loading system, as it is simply searching live as you type or gets the first 20 or 50 to build the dropdown, then loads more as you scroll.
There may be another problem (or problems) affecting live search/load. When it is not working be sure to check your browser console for any errors. And be sure what you are importing, is the file fully compatible with v7 (I remember that file having some problems before, did not checked later for updates)
And for your question, answer is "Yes" as long as your settings allow automated lookups and unadded airport usage (in some rare cases lookup may fail, like an airport can not be found in VaCentral database, ICAO code mistyped, ICAO code changed etc)
Good luck
-
12 hours ago, dualznz said:
there is more fields in your navdata dump @Strider than whats in the database table, im running v7 of phpvms, do we just drop the current navdata table and import your version ?
This is for legacy (v2/v5), not for v7 as far as I know and as you can see it is published under phpVMS Classic section of the forum.
Good luck
-
1
-
-
3 hours ago, SKD said:
Hello,
where can i find the settings for auto accepted pireps in phpvms7 ?
Admin > Ranks
-
Possible other causes of airport dropdowns not working
-
Cross Origin Scripting Errors
(APP_URL should match your current url, having http in .env but using https while visiting your website fails due to cross origin restrictions, can be solved either by fixin the APP_URL or allowing cross origin scripting between your domains) -
Custom Theme Errors
(Dropdown live search introduced recently, so if your theme is not properly configured to utilize the scripts and select2 features it will fail) -
Custom Blade Errors
(If you have an edited theme, they need to be updated to utilize the search properly, check provided default theme from original source: github or from latest dev release, implement the necessary changes to your blades)
Hope this helps people in the future
-
Cross Origin Scripting Errors
-
Great news then @SKD
I will check the status field from v5 data and provide a solution for v7 too (not for you anymore but for future Legacy Imports).
Enjoy v7
Side Note: Status should be ARR (ARRIVED) for v7 pireps, it is designed like that. When a pirep is finalized/closed by the pilot, it gets this status. So we should set this for imported pireps, even if they are rejected, they should be arrived. Thanks for sharing your findings on this.
-
1
-
-
4 hours ago, SKD said:
Ah ok. I will check the rows in the tables.
Perhaps there is a bug in the importer of the old v5 schema.Unfortunately yes, your imported pireps do not have `submitted_at` data
And this is causing the issue because my modules rely on the submit date, not creation date for operational reasons. A kind friend provided some v5 and imported v7 data yesterday night and I saw what I need (Summary; Legacy importer needs to be updated for at least two missing fields)
By the mean time, you can copy the created_at field as your submitted_at field in your v7 database with a query (cause the future update of the imported will do the exact same thing)... This will solve your statistic problems, something like below may work;
UPDATE pireps SET submitted_at = created_at WHERE submitted_at IS NULL;
Good luck
-
What is the `submitted_at` date of your pireps ? I am not asking the v5 pireps, we should check v7 tables from now on. As I am pretty sure those stats do work fine, we need to find the difference between an "imported old pirep" and a fresh v7 one to provide a solution (if it is possible of course)
-
Yeah, exactly what I though
Below that part, at line 406 you have the passenger and cargo counts of accepted pireps, which uses laravel's whereIn() function and fails because your placeholders passing the maria/mysql 65k limit.
If you check the latest update/version of my Disposable Basic module, you will see that I limited it and now it should pass that line, do not cause an exception and work without pax and cgo counts.
BTW, my idea reversing the logic causes inaccurate results due to cancelled, deleted, rejected pireps.
Hope it helps. (at least until we find a better solution)
-
1
-
-
Another solution can be reversing the logic for the stats, instead of using whereIn(...) , I can use whereNotIn(...) with rejected pirep id's array
That will be much less and below 65k I think for everyone.
-
48 minutes ago, SKD said:
Ok i fill my database again and start the migration. I will write back until the migration is done.
Probably you will be hitting MySQL/MariaDB's placeholder limits with my module's stat service, it tries to read all accepted pireps and pirep fares to get the pax/cargo counts.
If this is the case we can look further to improve that logic with only laravel relationships. Looping thought 170k pireps to get the total count may take some server time though, but we will see how it goes.
Another solution would be limiting that feature with 65k pireps, so pax/cgo counts will not work on your setup but will be present on others until they hit 65k pireps
-
Checked flight import code, if the distance is not supplied (empty, null) importer is designed to auto calculate @nobleord ... If it is not working please open a bug report instead of a feature request
Safe flights
-
5 hours ago, nobleord said:
Drat.
I looked in v5 and there is an option to "recalculate" the distances of each in the flight admin page but didn't see something similar while poking around in v7. (It also did the calculation during the import)
Is there a feature request wish list to add a "recalculate" option?
Thanks,
Bryan
Of course, there is a Feature Request option at GitHub, also bug reporting is possible, both being tracked and discussed there.
https://github.com/nabeelio/phpvms/issues/new/choose
https://github.com/nabeelio/phpvms/issues
Safe flights
-
It is auto calculated when creating a new flight via admin interface but not during import as far as I remember.
-
2 hours ago, Nabeel said:
I think I put in there how much time they were stopped as a field? If not, I think I can add that pretty easily
Yeah we already have "Total Pause Time" in pirep field values, but the OP's question was not about pause, also pause is not counted as flight time as expected. What he wants is simply eliminating sandbaggers with some automation.
Interesting issue maybe with PHP8.2
in Support
Posted
Interesting solution probably lies in your cron settings
After changing php versions, there are three steps to follow
Only after these steps are completed, and you still get php or extension related error, double check enabled extensions and php settings for your new version. As they need to be installed and configured per each version installed.
Good luck