Jump to content

ProAvia

Administrators
  • Posts

    1751
  • Joined

  • Last visited

  • Days Won

    78

Posts posted by ProAvia

  1. Do you mean the phpVMS image? 

     

    In /lib/skins/crystal/images - rename topbanner.jpg to topbanner.jpg.ORIG

    Copy/paste your image in this same folder and rename to topbanner.jpg

     

    If you are using an addon skin, you will need to find the associated banner and rename it in that skin folder.

  2. 2 hours ago, donrammer said:

    I had this exact problem myself this morning. It turns out I was missing a few PHP modules, and once installed it was fixed. I am running PHP 7.4, and installed the modules in CentOS by running:
     

    sudo yum install php php-common php-opcache php-mcrypt php-cli php-gd php-curl php-mysqlnd php-pdo php-pdo_mysql

     

    Hope this helps

     

    Thanks

     

    Rich

     

    If you are on shared hosting, you probably can't do any tweaks to PHP. Contact your host and have them set it up.

  3. Did you verify you installed Leaflet/OSM correctly? Maybe check it again

     

    Any chance you tried changing the map or map provider?

    Did you change local.config - Config::Set ('MAP_TYPE'... to reflect "OpenStreetMap.Mapnik"? Line should read:

    Config::Set('MAP_TYPE', 'OpenStreetMap.Mapnik'); <---- need this one

    And the old line either deleted or commented out.... //Config::Set('MAP_TYPE', 'G_HYBRID_MAP');

     

  4. That skin is for the frontend. The Airport Lookup is on the backend - admin panel. If you are using the default admin panel skin it should be fine.

     

    Did you import the phpvms_airports_update.sql file as indicated in the directions?

     

    Do you have error reporting turned on? Check the logs to see if any errors related to Airport Lookup or VACentral are shown - maybe3 a Cross Site Error. Post any errors here.

     

  5. 3 hours ago, cfitz619 said:

    Hello.  Great feature for my new airline!  Does this look right?  Followed the directions for install but the Lookup feature is not working for my airports.  Is it because the vacentral website is down?

     

    Thank You in advance for your assistance.

     

    633605291_phpvmsserver.png.767a799b03ba4538ffd4cfaa9ad2f29a.png

     

    The vacentral server is up and correctly providing airport data. 

    The entry above looks correct - check your other entries to be sure they are correct.

     

    If it still doesn't work....

    What phpVMS version?

    What PHP version?

    What MySQL or MariaDB version?

    Have you changed the default admin skin?

     

  6. In looking at my original module files and what is on my site, I have no idea where the status column came from or what it actually does. It may have something to do with my pilot manager module, which hasa column to mark pilots on leave. If I find out I will post back here.

  7. 5 hours ago, Thomasha said:

    We are still on Version 2.1.v2.1.935.

    This module is working since years for us. If you refer to the "hub"... i added this manualy to the database.

    I also cross checked the installer file with our actual table and they are all correct.

    We now also saw that the "delete" function also don't works anymore 😞

    Unbenannt.PNG

     

    The "You already have an LoA on file...." works on mine.

     

    I don't know anything about the loa table having a hub entry. Mine doesn't have hub - but does have status after reason.

     

    What PHP version are you using?

    What MySQL/MariaDB version?

     

  8. 1 hour ago, LuxuryCEO said:

    the module on my site says theres a critical update with a yellow box 😕

     

     

    Just ignore it. If it really bothers you, you can edit the module files to remove the check for updates. Of course, back up the originals before messing around with it.

    • Like 1
  9. 4 hours ago, Thomasha said:

    Hello Guys, does the feature which checks if the pilot has already submitted an loa works for you?

    For us it didn't but i don't know why...

    Here our files.

    Many thanks in advance for your help.

    BRGDS Thomas

     

     

    LoaData.PNG.45fd00034590ad03f5e7b3f4423c0d82.PNG

     

    ***********************************************************************************************************************************************

     

    LOA.PNG.95688de92ffc0dc4c05ad7d0e19635b5.PNG

     

     

    What version of phpVMS are you using?

    Did you run the SQL file to add to the database? This adds a new table for the LOA module.

     

  10. phpVMS 5.5.2.72 and phpVMS 5.5.2 have been reported as having issues with MariaDB 10.2 and higher. Check with the host to verify that Strict Mode is OFF. That may help fix the issue.

     

    Your pic shows PHP 7.3.6 . phpVMS 5.5.2.72 has issues with PHP 7.3 and higher. Verify which version of PHP the phpvms is set to run on. You may need to set up a subdomain to set it to PHP 7.2 (if the host has 7.2 available).

     

    The URL needs to point to the phpVMS root folder... in your case - https://usvaf.ml/phpvms

    Try with https and http - also with and without the trailing slash ( / ). I see you notrd you already tried that. Maybe try just 

    usvaf.ml/phpvms or usvaf.ml/phpvms/ -- as your screenshot shows "inclusive http://", so may not need the http part in the URL box.

     

    Other than that, I'm out of ideas. Maybe another member who actually uses cacars will chime in.

  11. Is your host doing awaywith PHP 5.6? If not, no reason to use phpVMS 5.5.2.72

    As you can see on your hosting, only PHP 5.6 and PHP 7.0 are available. Both versions are deprecated and no longer receiving updates. 

     

    Are you having any issues with your present install?

     

    I see your host is on MariaDB 10.3 - phpVMS 5.5.2.72 and 5.5.2 presently have some issues with MariaDB 10.2 and higher.

     

    In any case, there is no direct upgrading of phpVMS 5.5.2 to phpVMS 5.5.2.72. You have to start with a fresh install of phpVMS 5.5.2.72, get all your modules and skin working error free and then move you data (only) from your 5.5.2 install over to 5.5.2.72. Do NOT just use your 5.5.2 database as is - there are database changes in 5.5.2.72 that are not in 5.5.2.

     

    As for your present skin - it is not compatible with phpVMS 7 ... which has nothing to do with using PHP 7.0. It only has to do with what version of phpVMS you are using.

×
×
  • Create New...