Jump to content

ProAvia

Administrators
  • Posts

    1740
  • Joined

  • Last visited

  • Days Won

    78

Everything posted by ProAvia

  1. 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?
  2. 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.
  3. 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.
  4. 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.
  5. What MySQL version?
  6. phpVMS version? PHP version? MySQL/MariaDB version? Shared hosting or VPN?
  7. 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.
  8. phpVMS version? PHP version? MySQL or MariaDB version?
  9. 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"?
  10. Did you set up a subfleet yet? See the docs here: http://docs.phpvms.net/
  11. 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.
  12. 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?
  13. 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.
  14. That error has to do with creating an image and has nothing to do with the issue of this thread.
  15. 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!!
  16. 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 .
  17. 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.
  18. 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.
  19. BINGO!!! Look in your server logs and find the IP addresses behind these registrations - and if you choose, block them.
  20. I believe all free versions of kACARS_Free will work with phpVMS 5.5.2.72. But you need a version that will work with all sims you support and that will work with http or https/ssl. kACARS_Free 1.0.1.5 will work with FSX, FSX:SE, P3D, XP10, XP11 and possibly FS9. It will also work with http and https/ssl. In any case, once you find a version that works for your VA, you will need to edit the kCARS_Free module to reflect the version of the client you are using. Default module setting is for client version 1.0.1.1 .
  21. Others have reported issues with MariaDB 10.2 or higher. Any chance to revert to MariaDB 10.1? As an interim fix, look into disabling strict mode. While it might automatically reset itself if there is a minor update, at least you will know if diabling strict mode will allow full function.
  22. phpVMS - 5.5.2 PHP - 5.6 MySQL - version??? What version of MySQL?? Ok, so line 101 is $this->dbh = new mysqli($dbhost, $dbuser, $dbpassword); correct??? My guess is that there is a problem connecting to MySQL. Are the errors you posted the only errors in the error_log file or in the console? Make sure that local.config.php has the correct entries for: define('DBASE_USER', 'xxxxxx'); define('DBASE_PASS', 'yyyyyyyy'); define('DBASE_NAME', 'zzzzzz'); define('DBASE_SERVER', 'localhost'); define('DBASE_TYPE', 'mysqli'); replace xxxxx, yyyyyyyy, zzzzzz with the correct entries for you install
  23. phpVMS version? PHP version? MySQL or MariaDB version? Paste the contents of line 101 in /home/voloteav/public_html/crew/core/classes/ezdb/ezdb_mysqli.class.php I think it is not able to connect to MySQL/MariaDB - but post up the contents of line 101
  24. Try this - do a complete new install of phpVMS and use that install as a development site. So you will keep your present site and add a new site in a sub-domain. Then use the dev site to work out any kinks. I still think you will have issues at some point with MariaDB 10.3 while using phpVMS 5.5.2 The "Invalid argument...." error is pointing to something in line 78 that will not allow the processing to continue. It has something to do with viewing a PIREP comment (possibly an existing comment). I don't have that line in my pirep_viewreport.php file - so I believe it is specific to the iCrewLITE skin. If you are getting a bunch of errors, first - revert to the default skin (and default admin skin if you changed that). Then work through all the errors with the default skin. Finally, work on the errors with your chosen skin. But don't rush passed reverting to completely default and fixed EVERY error there first.
×
×
  • Create New...