DisposableHero

To be honest, what I am wondering is, how you will separate these "registration" based core v7 groups, what will be the impact on page load ? This will definitely need some loops in loops or multi level array functions to pick up same addon developer repaints (like Fenix or Zibo etc) and then add them to a new array, finally display that array with a group name "Zibo Liveries" etc.

Of course, you can check https://github.com/nabeelio/phpvms/blob/6b9658a4e37e193e00e5b1f4b1084130a64aaf1c/app/Http/Controllers/Frontend/DownloadController.php#L55-L65 to see how the files are named and grouped in the controller. You can also check default theme to see the default naming 'cause my theme removes some portions of the names to have better display. Then you can play with the php array to re-group or sub-group stuff as you like I do not know how you will organize your files to have some "Fenix A320" group but it should be possible with some loops and php functions doing array searches etc. Good luck

No need to move the post as it will apply to default theme too. As you found out, what you see and wondered about was a theme feature, a blade file, which you can customize as you wish under your duplicated theme (and share with people if you wish so)... phpVMS v7 returns the data to frontend with some basic grouping as it should (like aircraft, airline, airport etc.) you can re-group or sub-group the end results as you wish. As far as I remember my design, they should be ordered by name (array natural sorting). Good luck

@foreach($awards->whereIn('id', [1,2,3,4]) as $award) You need to know the id numbers of the awards you wish to group for this to work. more info at https://laravel.com/docs/10.x/collections#method-wherein you can use other available methods too. But there is a logical flaw in the code above, Auth always gives you the logged in user. So for example if you place this code to profile index page and then visit my profile, you will see your own awards Hope this helps, good luck

Hi @Nacman Are you asking this for my addons or for general? What you are asking is a basic phpvms v7 feature, and it can be reached easily by using `{{ $user->ident }}` . Even at backend, admin settings, there are controls for this feature (like fixing the ICAO code and defining the digits in the ident, usage of idents in SimBrief etc). Just inspect default theme, or my theme and you will see that there are many usages of this feature in places where a user's info is being displayed. If you are asking this specially for my theme, there is a setting at theme.json to show/hide idents by default. Most of my addons do follow your theme settings and are already configured to show idents along with names when you enable that setting. https://github.com/FatihKoz/DisposableTheme#settings-via-themejson https://github.com/nabeelio/phpvms/blob/ca565fc563d75c673f76207913473c080bceadf0/resources/views/layouts/default/users/table.blade.php#L26 Good luck

Interesting solution probably lies in your cron settings After changing php versions, there are three steps to follow Hosting Control Panel | Restart php itself (most of the hosting providers do this automatically, check if they provide a button - link etc. for it, if so restart it manually) Hosting Control Panel | Edit your cron command to reflect your latest changes to php version (this MUST be done manually, running php8.2 but trying to use a cron command for php8.1 will cause problems) PHPVMS v7 | Go to admin > maintenance and clear cache (this is not mandatory but eliminates risks) 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

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.

https://github.com/nabeelio/phpvms/blob/15563e1181dd4b6ae38e161fadb733c6a8392333/resources/views/layouts/default/dashboard/index.blade.php#L83 https://github.com/FatihKoz/DisposableTheme/blob/50ad455eb8ae4f3565723d0dbc1e70f13fee4016/resources/views/layouts/Disposable_v3/dashboard/index.blade.php#L40C44-L40C44 {{ Widget::latestNews(['count' => 3]) }} @widget('latestNews', ['count' => 3]) Both will end up loading the Latest News widget with last 3 news you entered.

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

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

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.

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

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

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

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

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.

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)

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.