ProAvia

Be aware that you are posting to a 10+ year old thread. Start a new post explaining exactly what you wish to do.

We need to see the entire error and also the code on "line 793". You also may want to contact iCrew to have them help you with the issue.

Here is the fix for the date/time https://github.com/ProAviaAZ/phpvms_5.5.2.72/issues/2 This fix has been implemented in phpVMS 5.5.2.72. You can make the same changes in 5.5.2 manually. There may be other issues with strict mode which were not addressed in the above link.

phpVMS version? PHP version? MySQL or MariaDB version? Shared or dedicated hosting? VPN?

There is no phpVMS 5.6 - there is 5.5.2 and 5.5.2.72 Verify which phpVMS version you are using. What PHP version? What MySQL or MariaDB version? Free or paid hosting? Shared hosting, dedicated, VPN?

phpVMS version? PHP version? MySQL or Maria DB version? Explain what this home page is that is outside of the phpVMS install and why you think you need it. Is this home page WordPress related?

It would be nice if you had left your initial post and also shared what you did to resolve it. It may help someone else in the future.

I believe the latest build is PHP 7.3 and 7.4 Can't hurt to change to PHP 7.2 and try that. I haven't heard if it works with MySQL 8 though.

Check what web541 suggests above, then...... Since you have MySQL 5.7 - check to see if strict mode is on or off. If on, set it to off. Several reports of strict mode errors in many different areas of phpVMS.

What MySQL version?

phpVMS version? PHP version? MySQL/MariaDB version? Shared hosting or VPN?

Congrats!!

That's what I thought - you posted in the legacy (v2, v5) forum. I will move it for you and merge it with your original post in the v7 Support forum. Also, no need to type the subject of your post in ALL CAPS or to post the same message in two different locations. Your answer won't come any quicker.

phpVMS version? PHP version? MySQL or MariaDB version?

My bet is the use of MariaDB 10.4 is messing it up. Can you revert to MariaDB 10.1 or switch to MySQL 5.6? Or ask your host to disable "strict mode"?

Did you set up a subfleet yet? See the docs here: http://docs.phpvms.net/

There are so many variables that it would be impossible to try to cover them all. No telling why your record is messed up. I've also run into that key constraint error way too many times.

Hopefully you come up with a viable solution. If you do, any chance you will share it with the community? Do you have a present solution that works with PHP 7.2 and phpVMS 5.5.2.72?

Are you using VAM or phpVMS? What is your URL? Sure would be great if you showed credit to the CMS developer on the front page or had a "Credits" link to a page with info on who the CMS, modules, skins, etc. developers are.

That error has to do with creating an image and has nothing to do with the issue of this thread.

I guess that may be one reason. This is the first time I have heard of issues with it though. I know of several sites that use gmail as the email provider and have no issues. I use an on site email address for mine though. There are so many variables, it's difficult to account for them all. And it is virtually impossible to build in "fixes" for every possibility. Don't forget, we are dealing with a 10+ year old program. We are lucky that it still (mostly) works in today's environment. Glad you were able to sort it!!

Your fix may only be specific to your server, server software or how you have things set up on your site. phpVMS 5.5.2.72 uses PHPMailer 6.0.7 and seems to work correctly for the majority of users under PHP 7.0-7.2 . The PHPMailer version in your fix appears to be 6.0.7 - maybe with a few edits?? phpVMS 5.5.2 (Simpilot) includes PHPMailer 5.2.8 .

Change back to the default crystal skin and see if the issue persists. Chances are you may need to format the Top Pilot page so it shows as you would like.

Probably not - unless someone writes an addon module for frequent flyer points. There is no way for passengers to log the flight time and pilots don't get frequent flyer points.

BINGO!!! Look in your server logs and find the IP addresses behind these registrations - and if you choose, block them.