DisposableHero

If you are planning to have a landing page, then it is highly advised to install phpvms v7 to a subdomain, you can find the details at installation guide (here at forum) and the details about uploading at docs. https://docs.phpvms.net/installation/uploading According to your explanation, it is clear that you are doing something wrong 'cause it is not needed to edit index.php etc for a proper install.

Glad to hear that workaround saved your day too

Technically you can not start searching or debugging the error I tried scanning a fresh installed sim with SU8 embedded during install, it was ok and all default airports + my addons in community folder was processed (added to database) Then I updated to SU9, tried a new scan with a fresh installed vmsAcars, it went well too and all my airports was found. One of my friends (a pilot of a VA I manage) faced the same issue, formatted his sim pc and fresh installed the sim (probably with SU8 like me), it went well and he is happy now. Another one (from the same VA) had the issue, he tried only re-installing the sim but he was not able to scan like you. I am not telling you to format your disc of course, but this is a strange error and I "assume" it is something broken at msfs and this happened probably when switching from SU7 to SU8 (or in between them somehow maybe with a world update etc, maybe not detected) and now with SU9 it is effecting more pilots Anyway, looks like only workaround now is using another pilots msfs_nav.db file (get it from a friend, place it on top of yours, do NOT re-sync until this problem is identified and fixed). I know, it will be missing your addons placed at community folder if you are not using the same addons with that pilot but at least you will be able to start a flight with acars. Hope it helps

That build will definitely work with my addons Enjoy your night and good luck.

Yeah, this is something thanks for the info. (you can delete the link/file from your Google Drive if you wish so) [2022-05-02 21:33:41] production.ERROR: Undefined variable $captcha Most probably you are using an incompatible (old) version of phpvms v7 with a theme which requires the latest development edition. This is why provided default is working but my theme is not too. Unfortunately you are STILL not following the docs to request help properly. https://docs.phpvms.net/help#information-required Please do not rush, take your time, read the link above and provide info for the bold items whenever you are ready to do so. We only have answers for "What page stuff happened on" and "Laravel logs" items, rest is still unclear. PS: We do NOT need apache and php logs for this error. Best wishes

So what can we do, or how can we help with nothing in hand ? It is clearly written in that page 1. Check laravel logs for error details 2. Ask for help with all required details And there is a link at the bottom for more info about what we need. I am really not understanding this attitude and probably never will You are Either not reading what is written there and running somewhere to ask for help, Or reading it but not following for some reason, Or reading it but doing this on purpose for some another unknown reason. When something terrible or unexpected happens, I do read what is written there, if there are any links to follow I click and read them too. But most of the VA owners/admins (even some so called "webmasters" not doing this) and requesting help with literally zero info. Hope you figure out this and provide some valuable info to get help. Best wishes

That update should go through composer > package.json I suppose as it probably needs to be recognized by laravel framework properly. So just updating the folders with new files may not work at all or may generate problems.

I kindly suggest you to read the docs, main difference between a widget and a module is explained there. Basically, above example is pure js. So it does not need to be a module, does not need to be a widget either. So in theory, it can be used as html/js in a blade OR can be converted to a (ultra) simple widget. Good luck

I liked option 3. Given the fact that v7 offers multi airline out of the box and its flexibility for setup and usage, it may be a nice choice for future. Schedules, fleet, operations etc all can be multi airline and if needed relaxed or easily can be restrictive upon airline needs. (costly, needs vmsAcars license) Option 2 looks like the easiest solution, if the operator has enough database knowledge and have backups for worst cases. (free but risky, can be easy if you have enough knowledge) Option 1 is the easiest

Filter property may be useful; https://www.w3schools.com/cssref/css3_pr_filter.asp

No need to be puzzled, either that pilot did a free flight and selected SVAG (8) as the airline or edited his pirep before sending it and changed the airline. It can not happen on its own, it is simply not possible.

Do you allow free flights ? If this is the case then a pilot can choose and use SVAG (as the airline) and 956 as his/her flight number. Which will give you the exact image above, but you will not be able to find that flight in your database. So, better check your database; a. Flights table for any flights assigned to that "group" airline and fix them (assign them to proper subsidiaries) b. Pireps table for any reports sent with that "group" airline's id As I am using a multiple airline setup for a long time, never had an issue with "airline id <> airline" matching and that part of the core is maybe untouched for years, so all can assume that it will not be touched/changed with upcoming update too. Hereby I am kindly informing you that your "issue" can not be solved by just updating your phpvms as it is not a problem related with core and/or addons. Safe flights

I solved that problem by adding a light colored glow outside the dark colored text and by using transparent background. With that, same logo is being used on both light and dark themes without any visual differences and loss of branding. Light theme: That light anti alliased glow is not noticable at all. Dark theme: That glow makes the text (or logo) visible and separable from the black background and looks fine. Just for your info

Got your point Colors are nice, grey and yellow tones look good Yeah, there was a discussion or talks about adding "time" as a core expense unit, selectable per flight but what happened to that idea I really forgot. As I am using my own module for income and expense, I stopped using core features. But if I can find that old topic (or maybe the GitHub issue) we can start talking about it again. It may come in handy, we can define expenses per flight by time then. Thanks for bringing that old/forgotten topic back, after Laravel9 maybe we can focus on and have it implemented in core (while looking at the custom expense bug). Best wishes

Why do you need a text change for it ? It is the "block time cost" of an aircraft (comes from subfleet of course) and it is the correct phrase to use there. In theory, it is the cost of using that aircraft for xx minutes, defined hourly as like in real life but calculated per minute. So in short, it is correctly designed, being calculated and used. Please do not mix up things with other things and try to find a way around to have what you wish to see, by requesting changes to working features That custom expense not working is still an open bug, probably will be fixed soon (after Laravel9 switch). If you need to stick with current dev for some reason, then you can design a really simple module to pass your custom expenses, that works, only "custom expenses without a module" solution/example is failing And just wondering, why do you need to create "a cost of crew salary" ? Pilots do get their pays, it is calculated. If you are trying to simulate cabin crew salaries, then doing it with an expense is much more logical. No need to brake working block time cost for that Best wishes

Are you using phpvms v7 ? If not, this may not be the correct place to get support... To me that change looks like a css/styling issue or a browser rendering problem in general.

If you mean making it changeable/selectable by the user, like a language selection dropdown at frontend, no it is not possible. If you want to change the language from English to French, then it is done in env.php file. APP_LOCALE=xx setting is for that.

You can check the docs about how to build addons covering your special needs, https://docs.phpvms.net/developers/addons Needs at least basic knowledge about php itself (specially php7.4 and up) and laravel framework (version 8 and up) to begin with (some database engine knowledge may be needed depending on your needs of course), rest is up to your imagination and coding skills as the webmaster. Good luck and God speed.

For pilots to use their salaries/earnings there are two public ways currently, provided by Disposable Basic "Jumpseat Travel" and "Aircraft Transfer" and some penalties applied by Disposable Special. It is possible to develop many more things to spend that virtual money, like type ratings payments done by pilots, free flights tied to some payment by pilot, maybe a virtual shop for them to buy items etc. All these ideas needs to be developed by the operator or some freelancer for the operator only or a third party developer/company as modules. As far as I know core v7 will not provide this kind of features as it is focused on providing a stable backend which you can build things on and use.

It all depends on how your settings are done, how often you do database cleanup (how many months back you keep records of old/non relevant data), how much data (flights/pireps) you have etc. etc. So there will be no "typical" or "normal" database size which will fit everyone or every install. For example, my live site's database is around 150 mb, I do not keep non relevant data more than 3 months old (like simbrief packs, acars position reports), performing weekly database cleanup and optimization too. So my database backups and export/import operations do not cause any timeouts or errors. But this may not be your case or this can not be called as normal/typical size.

It will work At least you will not see that relationship error anymore with an updated phpVMS v7

Looks like the main links you added to your menu/navbar is ok but you are missing a crucial component, your phpVMS v7 is out of date (or not updated properly, missing some critical improvements). That relationship error is a clear sign this, in other words you are using a Disposable addon which requires a more recent (preferably latest dev build of) phpVMS v7. Latest version of the module has this info in its readme, Compatible with any latest development (dev) build of phpVMS v7 released after 10.FEB.22 Anyway, that "Aircraft <> Airline" relationship was added to phpVMS v7 around the first week of November, 02.NOV.21 to be precise. So if you want to stick with an older v7 release you should also find a compatible release of my addons with that version and stick with it too. I kindly suggest you to update your core phpVMS v7 or do not use my addons as I can not support older versions Best wishes and good luck on the update process.

Looks like you are missing a cache cleanup or the module is not installed properly or you have problems with dynamic links. Either way, first try cleaning your application cache (admin > maintenance > application) as it is a part of the module installation, then for us to better understand what is going on, provide details about that "500 | Server Error". Enable debugging to see it live as it happens or check you laravel logs when you see that generic page. https://docs.phpvms.net/help Good luck

Well, if you just hover your mouse over the Disposable link (which should be placed at the footer and should not be removed according to license), you can see the theme version and date it gets released. Anyway, technically what you did not liked is the `$pirep->ident` generated by phpvms v7. If you do not want to use that then you need to find all instances of it being used in the blade files and change it to maybe `$pirep->flight_number` depending on your needs. Pirep/Flight Ident => Airline Code + Flight Number + "/C." + Route Code + "/L." + Route Leg => UK + 156 + /C. + FEB + /L. + 8 => UK156/C.FEB/L.8 So be advised, if you want to use only the flight number, then you need to add the airline code before it too 'cause it will look like `156` only with `$pirep->flight_number` I can not give you exact locations or file names, it is used in many different blades including module pages.

Glad it worked and saved you from more trouble Safe flights