ProAvia

With some hosts and using PHP 7.2, you need a .user.ini file in the main phpVMS folder for error reporting to log to the error_log file. Check with your host as not every host needs it. I have no idea what might need to change to make phpVMS 5.5.2.72 compatible with MariaDB 10.2+ - or else I would have already released something. 😀 There is no free ACARS for phpVMS v7. The payware one, by the same developer as phpVMS, is quite good though. You will need a newer PHP version as well. Check the DOCS for more info.

CCF Tracker may not be compatible with phpVMS 5.5.2.72 - there may be some corrections you need to make to the site files. Is error reporting turned on? Any errors in the error_log file related to CCF Tracker? The other issue my be MariaDB 10.5 - phpVMS 5.x has issues with MariaDB 10.2 and above. No fix is available at this time. I suggest you post something in the forums asking if anyone has a copy of kACARS_Free that they will send you. The best version will be kACARS_Free 1.0.1.5 (most current version) as it will work with secure websites and MSFS, P3D, FSX, FSX:SE and XPlane.

What phpVMS version? What PHP version? What MySQL or Maria DB version? Free or paid hosting? Who is the host? Also, you may wish to look around for kACARS_Free as an alternate to CCF Tracker. I personally don't know of anyone using CCF Tracker and "support" from Crazy Creatives has been non-existent for quite some time.

Sounds like something is wrong with your install. Some required parameters aren't being passed to SB. Change back to the default skin - be sure SB module is installed in core or for the crystal skin -and try again. This will determine if SB is working or not. From there, you will know whether its in the Stisla skin or with the SB module itself.

Without the information listed under "What an administrator should do now:" there is no way for anyone to know. Provide that info, and someone may be able to help.

Use the URL instead. Some hosting have issues with large files.

Does your hosting offer PHP 8? The latest DEV version available from Discord, Releases requires PHP 8. Do NOT use phpVMS7 Beta 4. It is too old and has issues.

Look in the "Announcements" channel in Discord. MSFS broke something again and the scenery scan isn't working as intended. There is a work-around posted in that channel.

Reinstall - including a new database. Be sure to use the latest DEV version, available in Discord under phpvms7, releases. The latest release required PHP 8.

Luke - I received this tonight when attempting to access your website. This was from Avast AV. You may want to contact them to get it rectified.

phpVMS v2.x is no longer supported. phpVMS v5.x has very limited support phpVMS v7 is fully supported. What PHP version do you intend to use? What MySQL/MariaDB version do you intend to use? Each version has specific requirements for PHP and MySQL/MariaDB. No idea of any phpVMS versions can be integrated to work with React.

PHP version? phpVMS 5.5.2 will work on PHP 5.4 thru 5.6. It will throw errors with PHP 7.0 thru7.4 phpVMS 5.5.2.72 will work on PHP 7.0 thru 7.2. It will throw errors with PHP 7.3 and above. Any version of phpVMS 5.x will have issues with MySQL above 5.7.4 and MariaDB above 10.1 Mostly this has to do with Strict Mode and/or no default values in the database. MySQL 8.x will not allow phpVMS 5.x to function properly. Consider upgrading to phpVMS v7. It has a steep learni g curve, but is much more robust and is in active continued development.

While I have not verified it, I think someone mentioned that Asobo moved the stock airport file location.

In MSFS, are you using SU9 or SU8 or another SU? Steam version or MS store version? Some have reported issues - check the 'vmsacars, #support' channel in Discord.

Might I suggest following what the text in the error says. Without you supplying that needed info, it's anyones guess.

It's not INTEL, it's INTL - internationalization extension. It is used for locale-aware operations. Check with your host and verify it is enabled.

It seems to be working fine now.

@servetas Maybe this will get you a reply.

Just add a link to simBrief website to the page. There is no stand alone program. Your pilots can also use the simBrief downloader to automatically download the flight plan files they need for their addons.

I see you also posted in the Discord phpVMS v7 channel about simBrief. The module here will NOT work with phpVMS v7. Be aware, there are several different versions of phpVMS. This addon module will work in phpVMS 5.5.2 (and 5.5.2.72 with a small modification) and may also work in phpVMS v2.x. phpVMS v7 is a totally new program. Modules written for previous versions will NOTwork in phpVMS v7. And simBrief is already integrated into phpVMS v7 - for flights that are listed in the DB. If you want to use it for other flights in v7, you either need to use it as a stand-alone or write your own module to integrate it.

Glad to hear you are doing better! I'm sure there will be some re-work on your end due to changes in phpVMS core.

Please post in English. If you wish to post in another language, also include the English translation.

It's more than just a Strict Mode issue. Strict Mode is OFF in the MariaDB 10.2 instance he uses. It probably has more to due with an empty value in the default aircraft table for this specifc instance. Shared hosting is being used and Strict Mode has been verified as OFF by his host. But it's possible a similar hack will work - at least in the short term.

1 - quit changing/adding aircraft, schedules, etc. every 6 months 2 - direct DB manipulation - use caution with this 3 - start planning to upgrade to phpVMS v7 - a big undertaking given your present operation 4 - you already know the other option you've used in the past

That's because your hosting is on MariaDB 10.2. phpVMS 5.5.2.72 has issues with importing with MariaDB 10.2 There is no solution at this point - except direct manipulation of the DB. This isn't for the faint of heart and shouldn't be attempted if you don't know exactly what you are doing. And you should back up the DB before even attempting.