ProAvia

The airports table format is different phpVMS v7 than prior versions. If you imported a 5.5.2 airports table directly into 7, it won't work correctly. That's why there is a converter built into v7. But you need a fresh version of 7 uploaded to your server to run the converter/importer. Upload the newest build of v7 and during install you will see the option in the upper right to import the older data into v7. Be patient, it will take some time if you are importing a large database.

Good suggestions. It may be best to post this on his github as he may see it there quicker. Open a new issue for each and post your request as an enhancement. Change map center in admin panel instead of directly in file Log into site using pilot ID or email instead of just email Possibly add directions on how to set up a cron job

simBrief does not have an ATR42 aircraft type available. They do have an ATR72. At the simBrief site, you can create a custom airframe for the ATR42 by using the ATR72 as a base. Then you can share the airframe. Once you do that, you can add the share to your on site simBrief code. I suggest you look in the simBrief support forums for how to create a custom airframe.

Glad you got it sorted.

There you go - he was quicker than I thought. Thanks VD

Actually there is a way to change the php version on the TFDI servers - as one of my fellow developers uses them and is able to do it. It's in a new section. Let me see if he can point you in the general direction.

I am not a big fan of just hiding the errors. The error you are seeing is because you are running php 7.2.29 and not php 5.6 I would suggest asking your hosting company to help you set the phpVMS directory to use php 5.6 - if they have that php version available. Or.... contact me via PM and provide your cPanel login details and I will take a look.

The first thing I would do is to verify that the directory phpVMS is in is using PHP 5.6 and not some version of PHP7. You shouldn't get that error in PHP 5.6 . Create a phpinfo.php file to check the PHP info of the phpVMS directory. https://mediatemple.net/community/products/dv/204643880/how-can-i-create-a-phpinfo.php-page

Post the full link when you hover over the "Bid" button. RIGHT click, copy the link and post it here. Possibly the schedule ID isn't getting passed.

Maybe something in the above post will help.

I deleted your other 2 posts with the same question. Only post in one location. And many times it is better to start a new post than to post in an older post that hasn't had a reply in over 6 months. That being said, hopefully you will receive a reply here in short order.

That would be the issue. The pilots table and a few others have changed to allow MySQL 5.6 and MySQL 5.7 to work. I suggest you install a virgin 5.5.2.72 and then compare the databases - especially the pilots table, news table and pages table. Probably the best way is to copy the data ONLY from the old database to the new database - one table at a time. A little time consuming, but at least the table structure will remain intact in the new database.

Moved to correct forum

If you'd like me to take a look, send me an admin logon via PM.

Did you do a complete fresh install or are you using a database from a prior version?

Change back to default crystal skin and try adding the schedule again. Does it work with the default crystal skin? If you refresh the page after adding the schedule, is the schedule now displayed?

Put the same in for the default joindate. You may get other date type errors - and may possibly need to change those too. If they display date and time... 0000-00-00 00:00:00 ..... use 1970-01-01 01:01:01 Or change all three to what is in my pic above and see if that works. Did you use your old database or is this a totally fresh install?

Try changing that default to 1970-01-01 - and let us know if that works.

What version of MySQL?

Did you install phpVMS 5.5.2 or phpVMS 5.5.2.72? What version of PHP? What version of MySQL or MariaDB? What skin are you using? What addon modules do you have installed?

It can be a LOT of work - especially if one is using a bunch of addon modules. Careful planning is key. Backup the existing site and DB first. Install 5.5.2 as a separate site. Install the 5.5.2 compatible modj,es and edit older modules to work with 5.5.2. Test the 5.5.2 site.... test again... and a third time. Then move/merge the 2.x DB with the 5.5.2 DB. Do site and DB backups every step along the way. Good luck!

Thanks!

This looks interesting.... what versions of phpVMS will this be available for? Do you have pricing worked out yet?

Not exactly.... you will need to update their existing db tables to include any new fields and there are a few table additions too. Certainly can be done if you are confident in your abilities. Be sure to backup the DB first and also do it frequently during the conversion process. You will also need to update a good number of addon modules for them to work correctly. It may be better to leave as is and wait for phpVMS v7 to release. It shouldn't be much longer. Of course, they will need PHP 7 on their host. As is stated in the 5.5.2 readme file - "... This version is not for the faint of heart. If you have modules and other addons that worked on older releases of phpVMS they will most likely break in this version. ..."

Do you mean in the email that goes to the admin to advise of a newly submitted PIREP? If so, you can have multiple recipients by having the initial email go to an email address on your site and then setting up email forwarders to forward that email to multiple email addresses. So set your site admin email to something like "dispatch@my_site.com". Then go into your cPanel and be sure that email address exists - if not, creat it. Then set up email forwarders from "dispatch@my_site.com" to the multiple recipients desired. As for the info contained in that email, you would need to edit /core/common/PIREPData.class.php to include the info you want. Look near line 757 for - # Send an email to the admin that a PIREP was submitted - and edit the area immediately below it. Be sure to backup the file first before editing it.