ProAvia

phpVMS versions 2.1.x - original version - worked with php 4 - no longer in development 2 - legacy support for php 7 - no longer in development 5.5.2 - Simpilot version - works with php 5 5.5.2.72 - Simpilot version updated to work with php 7.2 (possibly 7.0 & 7.1 also) 7.0 - newest version - still in development - probably not good for a production environment for now I would consider 5.5.2.72 as the host has php 7.2 available. You will have to make some corrections to your skin and addon modules. Many of these corrections will be the same - mostly related to $count changes in php 7.2. I can help point you in the correct direction on most of the errors you might see. I updated 5.5.2 to 5.5.2.72 because my host forced us from 5.6 to 7.2 back in March of this year. Changing hosts just wasn't an option at that time. I got really lucky with the conversion - with help from members here and a lot of Google searching. After I had it running successfully for a few months, I made it available as an option for anyone using php 7.2. Version 7.0 is the newest - but skins and addons are still a ways off, as version 7 isn't in general release yet. Older skins and addons probably will need to be fully re-written.

As I indicated, there may be an issue installing on php 7.3 . If it won't install on 7.3, install locally on 7.2 using Wamp or Xxamp and then move to the webhost on 7.3. It's possible that there may be a few issues to fix before adding skins and other addons. You are in unknown territory here, as I haven't tried on php 7.3. Get the base program working correctly first before adding additions skins or addons.

The error log file is named "error_log" - if it is not present, create the file. It is basically a text file without the ".txt" extension. Then when loading the present site, the errors should log to that file. If they do not, you may have to turn error logging on in the php.ini file. As for the "Config::Set" lines - the last one sets the error reporting level. Presently it is set to show all errors except Notices. That setting should be fine - as you will want to fix as may errors as you possibly can before taking the site from development to live status. Copying over a 5.5.2 install to php 7.2 or greater will produce many Warning, Deprecated, etc type errors. I would suggest trying to install phpVMS 5.5.2.72 and see if you can get it to install successfully. Don't just copy the files over from another install - do a fresh install of 5.5.2.72 to a new database. If it does not install to the webhost successfully, maybe install it locally on your machine using Wamp or Xxamp under php 7.2 . Then copy all the files and database from that local install to the webhost and see what errors might present themselves. Of course, moving local install to webhost will require editing of local.config.php file to align with the webhosts names, etc. Be aware, many files in 5.5.2.72 were edited to work with php 7.2 - replacing any of the default 5.5.2.72 files may result in site errors. Although, you may have to make some file corrections to accommodate php 7.3 (just do not use any files from prior versions). You may have to do some editing of any addon skins and modules - usually pretty basic fixes though. It can be done, but its a pain. But sometimes that is your only option. If you can get phpVMS 5.5.2.72 running in php 7.3 without error, I can try to assist in getting the skins and addon modules fixed.

Something isn't adding up. Simpilot version - 5.5.2 - doesn't install and function correctly under php 7 or higher from what I remember. Look in local.config.php around line 14 - there should be 3 Config::Set entries. Those 3 lines provide no personal info and are safe to post here (don't post any of the define('DBASE..... lines as those contain personal info). List the content of those 3 Config::Set lines. In the root of phpVMS there should be a file called error_log - errors are logged there. I think webhosts have differing requirements to enable error logging. Many turn error logging on in the php.ini file. Before moving to php 7.2, my host had error logging on. Once they forced us to 7.2 the error logging defaulted to off and I needed to add to the php.ini file to turn it on. If you have no option to downgrade the php version to php 5.something, consider using phpVMS 5.5.2.72 - pinned at the top of this forum. It will install under php 7.2. Read the readme file first. It won't work under php 7.3 . Version 5.5.2.72 is basically 5.5.2 updated to work with php 7.2 . Maybe the best bet is to see if other php versions are available first. If you have access to the cPanel for the account, look for MultiPHP Manager to see what versions may be available. Once we know that, we can help out further. Don't be concerned with the Warning, Deprecated, etc messages for right now. EDIT - did you just copy the Citylink files over to vlmva or did you do a totally fresh install of 5.5.2 to vlmva?

phpVMS 5.5.2 will not install or run without error under php 7.3 as far as I know. Did you turn error logging off in the local.config.php file? Did you edit phpVMS to work with php 7.3.9? Have you checked the error_log file for any errors? phpVMS 5.5.2 will work with php 5 - up to php version 5.6 if I recall. It will shows lots of errors when attempting install in php 7.0 and above. phpVMS 5.5.2.72 will work with php 7.2 - but shows errors in php 7.3 Please verify what version of phpVMS you are running and what version of php the directory that phpVMS is set for. Also, is error logging on or off?

The coding is in place for ReCaptcha version 2 - you will need to acquire and enter your own Recaptcha keys. Those keys get entered into local.config.php - if there are no entries to pit them there, copy/paste that particular section from app.config.php into local.config.php and enter your keys as indicated.

phpVMS 5.5.2 already has the kACARS_Free site module 1.0.1.1 as default. The kACARS_Free client 1.0.1.1 should work fine. Actually, any of the freware clients will work with site module 1.0.1.1 if you allow all versions in the site file or set the actual client version you will require pilots to use in the site file. I really don't think the section you posted pertaining to "kacars 3.0" will have anything to do with the vlmva issue. I am unaware of "kacars 3.0" - the only payware versions I know of are kACARSI and kACARSII. I'm not sure about the kACARS payware version you have for your VA, but kACARSII payware version will only work with a specific site URL. It will not connect with vlmva as the underlying URL is different. Double check that you set up kACARS_Free client correctly - check the VA and user profiles.... that the URL and pilot info is correct to connect to vlmva. What PHP version is vlmva using?

What version of phpVMS are you using on vlmava.com? PHP version? What version of kACRS_Free site side module? What version of kACARS_Free client? I have not used ccftracker, so don't know what to look for with it.

phpVMS 5.0 Classic is version 2.1.x updated for php versions up to php 7.0 I believe. Not sure if this version is ReCaptcha v2 compliant or not. I think it's best suited for those who already have phpVMS 2.1.x installed and are actively using it on their established VA. You may be better served by installing the Simpilot version - phpVMS 5.5.2? Here's a link: https://github.com/DavidJClark/phpvms_5.5.x . This version is already ReCaptcha v2 compliant - among other updates. If you decide to use 5.5.2, just delete the present files and if the database is new (without any pilots, airports, aircraft, schedules, etc.) delete it also and start fresh. If the database already has some data in it, just make a new database for 5.5.2. As for adding modules, many (most?) freeware modules have been updated to work with phpVMS 5.5.2. Those that are not are pretty easily converted.

What version of phpVMS are you using? What version of PHP? Free or paid hosting?

See the second sticky above - Upgrading ReCaptcha for v2

No reason to feel stupid. We've all been there. And that's how we learn. Glad you got it fixed. Remember - not all modules will show in the plugin manager. I believe the ZIP file needs to include a 'config.txt' file in the original package.

Did you verify that the 3 files referenced are actually in /admin/templates/plugins ?

OP is using phpVMS 5.5.x - the Simpilot version. /core/modules/Pilots/Pilots.php shows $this->set('allpilots', $pilot_list); # deprecated $this->set('pilot_list', $pilot_list); So $pilot_list should work. In looking at http://www.gatewayvirtual.com/index.php/Pilots - there are 3 hubs listed, but no pilots assign to any of them. Try assigning your one pilot to a hub.

What are the contents of /lib/skins/blueice/pilots_list.php line 16? What version of php are you using? What version of phpVMS are you using?

Glad you got it working.

Please answer the questions above. Posting the entire file contents just makes it difficult to find the contents of line 32 in /core/modules/ACARS/ACARS.php ---- and the other info is important to assist you. Additionally, have you made any changes to those 2 files or are they the default, un-edited files?

Is there a file in /core/comon named ACARSData.class.php ? What are the contents of line 32 in /core/modules/ACARS/ACARS.php ? What phpVMS version are you using? What PHP version are you using?

That's good to know - thanks! Some FSX/P3D aircraft lights are also called by non-standard events also. The only actual ones documented in FSUIPC are the PMDG aircraft - but not sure it's worth the time to program an ACARS to align with them.

I guess you would have to try the JARDesign A330 again. Are you saying when you turn the beacon on in the Zibo B728 the ACARS reports it is off? Or when you turn it on, it reports on then off right away?

I just happened to leave mine setting - so sometime between 30 minutes and 2 hours, something must have updated and then at 2 hours I clicked and it submitted. That may be - I was using the default B737-800 that I imported from FSX. And just a short flight from KIAH to KDAL.

Since you are running phpVMS and VAFS, you can't access both from http://www.panamericava.com or http://www.panamericava.com/index.html - that's where the conflict occurred initially when you tried installing phpVMS in the public_html directory. While you certainly can run phpVMS and VAFS concurrently, I don't believe they will share data - as each uses a different database and database structure. I am not familiar with VAFS. As I said earlier - to keep order, each program should be in their own directory in public_html. If you were only running one or the other, there is a way to have the program in its own directory and have an index file in public_html to initially load it from there. But with running the two programs, I don't think that's possible..... hence the need to have the sub directory name as part of the URL to reach phpVMS.

You need to go to http://www.panamericanva.com/phpvms/install/install.php Your phpvms site will be at http://www.panamericanva.com/phpvms

Good luck! Let us know how it works out.

Create a folder inside public_html called phpvms and install it there - public_html\phpvms You can install phpVMS 5.0 (classic - called v2 also) - https://github.com/nabeelio/phpvms_v2 or phpVMS 5.5.2 (Simpilot version) - https://github.com/DavidJClark/phpvms_5.5.x . There are some differences between the two. Personally, for a totally new install, I would go with the 5.5.2 version. Long term, you should consider having your VAFS in it's own folder too - public_html\vafs. Don't create any folders inside of the \home directory - all folders get created in public_html. All that should be in the \home directory is what your host put there.