ProAvia

Hmm - maybe your frontpage_main has been modified. What I posted is from the original file. What is line 112 in /home2/ravnalas/public_html/Crew/lib/skins/ocean_blue/frontpage_main.php

Now that you changed to something lower than PHP 7.3..... The "Pilots in flight" Warning you see on the front page of the admin site can be fixed by changing... starting on line 111 of .... /home2/ravnalas/public_html/Crew/lib/skins/ocean_blue/frontpage_main.php from <?php if(count($shown) < 1){ echo 'There are no pilots online!'; } ?> to...... <?php if(is_array ($shown) || $shown instance of Countable) { if(count($shown) < 1){ echo 'There are no pilots online!'; } } ?> That's one of the error I saw more often than others

Yes - drop the admin site down to 7.2 and those Deprecated will go away. While what you have now is not perfect, at least it's functional. Hopefully your host will allow 7.2 for some time. Once you have nothing better to do (HA) - consider updating all your modules to work with the 5.5.2.72 version. Many of the errors you will see will be repeated in the modules, so it' pretty easy to convert them over. As a Suggestion, if you go this route, make a test site on your host to work thru any issues - and set that test site to PHP 7.2. Once it's all working to your satisfaction, you can move it over to the live site (after backing everything up of course). I haven't looked at using PHP 7.3 for the 5.5.2 (Simpilot) branch yet - beyond knowing it will throw errors. It may be possible to use my 5.5.2.72 version and update it for PHP 7.3, but I won't have time to look into it for a while.

I don't think those Deprecated will affect the functioning of the site for right now. They are related to PHP 7.3 and are only showing on the admin panel site. I found some info, but need to research it a bit more before I comment further.

Great that you can at least get into the admin - using a second install. Very weird issue..... Having the inherited PHP version as 7.3 shouldn't affect any domains set for another PHP version - at least it didn't on mine (had 7.2 as inherited, 5.6, 7.0 and 7.1 also available) I will look into the deprecated you posted and let you know..... What PHP version is the main site running? What PHP version is the site with admin access running?

phpVMS v7 isn't ready for a live environment. And there are no skins or modules yet either. Leave the live site on PHP 5.6 if you can. Well... let's try to get you operational at least.... Make a copy of your DB in phpMyAdmin Make a backup of the live DB also - just to be extra safe (you will now have the live DB, a copy and the separate backup.... 3 in total) Download this version of phpVMS - it will install under PHP 7.2 (won't work in 7.3 though) https://forum.phpvms.net/topic/26545-phpvms-55272-phpvms-552-updated-for-php-72/ Install the above linked version in a separate directory After install, go to /core/local.config.php and change the DB access to the COPY of the DB you made - also change the site URL there See if you can access the admin panel. If all that worked - change this new install (5.5.2.72) to access the live DB and approve all the PIREPS from there. Also do any other admin functions you need to do. Again, if it all worked, the pilots access the present live site. Admin access is through the 5.5.2.72 site. Hopefully that will allow you to get functional again. Don't bother installing any skins or modules to the 5.5.2.72 site - you are just using it for admin functions. Let my know if this crazy idea works for you. EDIT - as an aside - I have 5.5.2.72 running on my site since end of March when my host forced us to PHP 7.2. It took a lot of work to change 5.5.2 to 5.5.2.72 - and also skin and module changes.

The permission number is correct for Admin on phpVMS 5.5.2 I'm not sure the other 2 are causing any issues - just thought it might be good to try downgrading their PHP version. I'm at a loss.

Edit your post above and delete the zip file as it contains a password. As a test, change all 3 for PHP 5.6 . The error level set is okay. From a couple posts up...... Also - in the DB groups table - what is the permissions number shown for Admins?

Also - in the DB groups table - what is the permissions number shown for Admins?

I don't see any errors showing when loading the site and looking around as a guest...... In /core/local.config.php - around line 25 - what is the ERROR_LEVEL set to? Are you using cPanel when accessing your host? Do you have an option for "MultiPHP Manager" - and can you set your VA domain to anything but 7.3 there?

If you are running PHP 7.3 - that may well be your issue. Can you downgrade the PHP version to 5.6 (or as low as 5.3)? If you can't go back to php 5.x, what PHP versions are available to you? What is your site URL?

Did you try to log in again? What happens when you do that? What version of PHP are you running?

Sim was P3D 4.3 - aircraft is default B738 imported from FSX

Under Log.jpg Start Taxi - Landing lights on below 10k - landing lights were off - speed was below 20 kts - When taxiing, got error "Landing lights on below 10k", the landing lights were off and taxi speed was below 20 kts. This shouldn't be a violation while on ground and below 20 kts. On second set of bullet points - just suggestions. As is now, if a violation occurs, it states what to do rather than whwt the violation was. If I don't have landing lights on while below 10k, it should state that "Landing lights off below 10k" as the violation - not imply what to do to rectify the violation.

Great Another option would be to write additional code so that if the pilot hasn't filed at least one PIREP, the module would then get the pilots assigned hub as the current location.... But you are on your own there, as that's beyond my present skill set.

Your module is NOT outdated. It's the exact same one I have. I went thru each file and changed any references in the files from tpl to php and then made sure all the file names ended in php. And then I added the code line I posted above. If I provided my files to you, the end result would be the same. You still haven't answered my question.... Has the pilot filed at least one PIREP. Until the pilot files at least one PIREP, the current location will remain empty - that's just the way the module works. The module looks at PIREP data to get the last arrival point and uses that as the pilots current location.

There are only 3 files for the RandomFlights module In /templates/randomsearch.php - the change I listed above is the only code change in mine from the original file. In /template/randomflights.php - my file is the same as the original In /modules/Randomflights/RandomFlights.php - my file is the same as the original Have you actually completed at least one flight to a destination in your DB with the pilot sign-on you are using to test the module? I just checked mine, and with a sign-on that has not completed a flight, the current location is blank - but with a sign-on that has completed at least one flight, the current location is listed.So, basically, that pilot needs at least one PIREP submitted and approve that landed at an airport in your DB before the current location will show in Random Flights.

I will review my files later when I am home and on the computer - and let you know what I have. There may be other changed I made to get it working correctly.

5.5.2 - that is the same version I use. Not sure what you mean by "he adds icao and doesn't scale". As far as current location being blank, you must fly at least one flight to a destination in your db for that field to show your current location. I guess there may be a way around that, but my pilots can't use the random flights generator until they reach a certain rank - and will have flown several flights before then. Did you try what I posted and did the error disappear?

Don't turn off error reporting - work to fix the issue first and foremost. What version of phpVMS? What version of PHP? Change $pilotid = Auth::$userinfo->pilotid; $last_location = PIREPData::getLastReports($pilotid, 1); if(!$last_location) $last_location->arricao = Auth::$userinfo->hub; $last_name = OperationsData::getAirportInfo($last_location->arricao); $equipment = OperationsData::GetAllAircraftSearchList(true); $airlines = OperationsData::getAllAirlines(true); ?> To $pilotid = Auth::$userinfo->pilotid; $last_location = PIREPData::getLastReports($pilotid, 1); if(!$last_location) $last_location = new StdClass(); if(!$last_location) $last_location->arricao = Auth::$userinfo->hub; $last_name = OperationsData::getAirportInfo($last_location->arricao); $equipment = OperationsData::GetAllAircraftSearchList(true); $airlines = OperationsData::getAllAirlines(true); ?> I think that's the only change necessary. I'm on mobile right now and can't easily do a file compare to be sure. If the above doesn't fix it, I will do a file compare once I am near my computer.

What php version do you intend to use? That might dictate which phpVMS version would work best for you. phpVMS 7 - probably not good to use for a live/production site as it's still being developed - it uses php7+ phpVMS 5.5.2.72 - this is the simpilot version updated to work with php7.2 - and it works in php 7.0 & 7.1 phpVMS 5.5.2 - this is the original simpilot version - this is version 2.x updated to work with php 5.3 - 5.6 phpVMS v2 - sometimes referred to as phpVMS 5.0 - updated to work with php 7.0 and possibly 7.1 & 7.2 - this is the original version updated for php 7 phpVMS 2.x - this is the original released version - works with php 4 - This one probably isn't available anymore As you can see, there are several options available.

VMS Acars 08/22 Build - Version 1.0.1908221708 phpVMS install updated to latest build from 8/22 (7.0.0+190822.6018a6) P3D v4.3 This build appears to have corrected the "Error sending PIREP update, retrying, Too Many Attempts", as none were encountered. 👌👍 See attached zip for pics.... KIAH-KDAL B738 FL180 Log.jpg Start Taxi - Landing lights on below 10k - landing lights were off - speed was below 20 kts Started Takeoff - Strobes on while in flight - still taxiing below 20 kts and on ground - Thrust reverse enabled below 60kts - I was testing to see if it flagged it - works Crossing above 10,000 feet - Landing lights off above 10k' - they were on above 10k - works probably doesn't need the 500' inbuilt delay as we can set an altitude for the violation to occur (maybe 11k in climb and 9k in descent) Landing lights turned on - no flag below 10k - lights were turned on at 4000' MSL Strobes on while taxiing - flagged after clearing runway and below 30 kts - maybe this needs a delay before flagging Summary 1 / Summary 2 pics added for review Landing lights and strobes violation - possible change If landing lights violation is flagged during takeoff, instead of "Landing lights on below 10k" (which is not a violation), should say OFF If landing lights violation is flagged above 10k, should say "Landing lights on above 10k" Strobes - may be better to set to 40-ish knots or greater for violation and possibly have a time delay after landing to allow aircraft to clear runway Log.zip

phpVMS 5.5.2.72 was tested with MySQL 5.6 and 5.7 - it was not tested with any versions of MariaDB. Are you able to change the version of MariaDB to 10.1 or 10.2? Can you downgrade you PHP version to 5.6? If so, install phpVMS 5.5.2 (Simpilot version). Who is you web hosting company? Here are a couple of links that may or may not help.... https://mariadb.com/kb/en/library/incompatibilities-and-feature-differences-between-mariadb-103-and-mysql-57/ https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/ EDIT - can you post any error_log files? Have you opened your browser console to see if any errors are posted there?

Did you mean version 5.5.2.72 ? What version of php... 7.2.?? What version of Maria DB? Do you have the option of using MySQL instead of Maria DB?

If you are going to use one of the classic versions, start a thread in the forums there. Best not to mix v7 and classic in the same post.