Leaderboard

Note: If you own all packages then please note the update order! SPTheme -> DBPack -> DSPack Note 2: If you changed the colors, for example, just backup the following file: /resources/views/layouts/SPTheme/config.json 05.APRIL.25 (v1.3.0 / 1.3.0 / v1.3.5) (v1.3.0 SPTheme) Fixed an issue where incorrect fuel/weight units were displayed Fixed an issue where users could not change their password Fixed some style discrepancies on macOS devices Fixed issues with VATSIM/IVAO user fields and OAuth link Fixed an issue where fares could not be entered when changing aircraft (v1.3.0 DBPack) Fixed an issue where some fleet images were not responsive Fixed an issue where cards did not have space between them Fixed a condition where the cruise profile CI/LRC could not be changed Fixed a label that had some typos Added a failsafe to the SimBrief form in case a profile could not be found Added a failsafe to the random flights Widget (v1.3.5 DSPack) Added a failsafe to the assignments if a flight was deleted Fixed a missing route to the missions area for flight details Fixed an issue with multiple airlines and the selected fleet on free flights Fixed name for the airline on assignments

Hello DisposableHero, The Hero part is certainly very accurate!! Thank you so much for turning me in the correct direction, I don't think I could have been more off track with the direction I was going if I had tried. I appreciate you taking the time out of your day with pictures and a code example to help me out. Thank You so so much!!!

Resolved on discord Hi there I love this add on. It looks really well but something has happened to my dashboard page. It was working fine but now i get a 500 error. I checked the logs and got the following. I had changed the name of the airline yesterday in the admin section and all was working. Same airline just added a little. I have since changed it back to the original as the error on the page shows. Any help would be much appreciated. Thanks

I'm aware of the free flight thingamajig. Looks like it needs to be rebuild.

Dear all, version of my VMSAcars is Version: 2.0.629; Stable Here are my logs https://drive.google.com/file/d/1_bbiALSf5HeAhAiHWwiW1tQLuHYXEV0C/view?usp=drive_link https://drive.google.com/file/d/1i2zQeLY6jBPvjhK3sByAJyTSISn-X7-Y/view?usp=drive_link This is not applicable, i never go to sim menus while flying, i just noticed a drop of frame rate when pause is detected. Also VMS has been freshly reinstalled deleting both software and appdata and XP subfolders too, also i have created by scratch the configuration to my VA. As i said, never did that, the only thing i have changed is that i keep VMS open in a secondary screen while before it was always in background. Also i did some flight with FS2020 and i never got those pauses. Thanks you Luca

My pleasure. At least you learnt the importance of cache by the hard way (maybe the hardest way) around, you will never forget it again Congratulations, enjoy your mails (free for 3 months) with mailgun. By the way, API is the fastest and safest way to implement it, glad it worked as expected and you did not used the smtp solution. Have a nice day Addition; 2022 Jan / Academy award winner screenshot name "An important moment in the history"

Well, I really have no idea why it fails @William, some guys tried the api setup it worked well and some other users of phpvms v7 are using mailgun with api too. I am not blaming you, there should be something blocking api access somewhere. Classic smtp settings should work, I mean it is basic mailing, works for every server, why it should fail at yours. You already have server, port, username, password etc for their smtp access. Just use the default SMTP example with that info. SMTP MAIL_MAILER=smtp MAIL_FROM_NAME='American Virtual' MAIL_FROM_ADDRESS='postmaster@americanva.org' MAIL_HOST=smtp.mailgun.org MAIL_PORT=587 MAIL_ENCRYPTION= MAIL_USERNAME='postmaster@americanva.org' MAIL_PASSWORD='that long password here' API MAIL_MAILER=mailgun MAILGUN_DOMAIN='americanva.org' MAILGUN_SECRET='that long api key here' I assume you are cleaning the application cache from admin > maintenance after doing changes to env.php and saving/uploading that file, failing or forgetting this step will cause problems. (technically until you clean the cache your old env.php will remain in effect and changes will not be applied)