ProAvia

No more flash. Try Google charts or Morris charts.

phpVMS 5.5.2 will not work correctly with PHP 7.0

Is that phpVMS 5.5.2 or 5.5.2.72? phpVMS 5.5.x is not quite descriptive enough as there are various versions which could affect your desired outcome.

There are instructions on the forum to use Leaflet/OSM maps for phpVMS. You can easily adapt those to work with this (and other) skins.

phpVMS version? PHP version? MySQL/MariaDB version? Your topic title states: Pilot List Empty [Admin Panel] But the included picture is active schedules What exact issue are you having? Has it ever worked correctly or is this a new issue?

Was the csv exported from the latest dev build of phpVMS v7? Does the file format match that of the phpVMSv7 aircraft database table?

If you installed on PHP 5.6.40, you did not read the requirements for installing phpVMS v7 https://docs.phpvms.net/

PHP version? MySQL/Maria DB version? Did you follow the install directions in the docs?

MODERATOR NOTE: Moved from v2,v5 forum to v7 forum..... It is recommended NOT to use phpVMS v7 beta 4. Instead, download the latest dev build available from the phpVMS Discord releases channel. Be aware that phpVMS v7 is still in testing and new releases are possible several times a week or more.

Maybe @Strider can assist in where to place the INSERT IGNORE

Free hosting puts limits on required PHP functions and other stuff. It's free for a reason - very basic function. If you are serious about running a VA and want to attract quality pilots and staff, free hosting isn't going to get you there. If you don't want to spend the money, think about joining one of the many quality VA's already established.

Free hosting always causes issues. Free hosts limit access to certain required items. If you are serious about your VA, get paid hosting. If you are just setting up your VA for testing, use WAMP or XXAMP running on a local machine. Look in /core/common/SchedulesData.class.php and /core/modules/Schedules/Schedules.php. one of those files should have a "view" function in it.

Suggest you contact your hosting company and ask them what MySQL or MariaDB version you are using. Are you using paid or free hosting? The Warning is basically saying that the Schedules module does have the method "viewaction.php". No idea how or why you are calling that. The default Schedules files do not contain that method. There is a "view" call - but no "viewaction.php". Are you attempting to display schedule search results?

Revert to default skin and try again. Does it work or do you get the same error? phpVMS version? PHP version? MySQL or MariaDB version? What skin are you using?

Maybe try reverting to the original style with the original files of the module to see if it works. If it does, you will need to review your style changes.

Do not post code from payware modules. You may ask general questions and members who have the same module may respond to you via PM. Just don't post specifics in the open forums. We realize that support is limited to non-existent at times from CC. But you can't post payware code as it violates the module license. Thank you for your understanding.

That is addBid - and has nothing to do with PIREP filing

So switching to default skin didn't work either.... You will need to dig into the code for PIREP filing. Once you locate that code, look for INSERT and replace with INSERT IGNORE

Did you try what I suggested above? It is unclear from your response.

On the File a PIREP page, you show these errors You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors. Google Maps JavaScript API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys Google Maps JavaScript API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required DevTools failed to load SourceMap: Could not load content for https://crew.vsundair.de/lib/skins/FireCrew3/assets/js/chartist.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE All but the last definitely have to do with Google Maps. You are calling the Google Maps API multiple times on this page. The default install doesn't do this - so it's probably the skin or a core file you edited. You don't have any Google Maps API keys installed - this is required for the map to work correctly. No idea if smartCARS uses this or not. You have "sensor=true" set - don't include the "sensor=true" part as the present Google Maps API doesn't use it. No idea what this is.... something in your FireCrew3 skin. In any case, I would revert back to the default skin, fix the Google Maps errors and try again. Once you have all the errors fixed using the default skin, install smartCARS and see if it works. If it does, then try with an addon skin. You need to be very systematic. Get the default install working correctly first. Then fixes will be easier.

I'd suggest placi g a blank text file named error_log in both of those directories. Only name it "error_log" - no file extension. Then try filing a PIREP again and see if there are any errors in the file. Also, using GoogleChrome browser,open the console prior to accessing the PIREP page - go to the page (with console open) and see if any errors show in the console

Is error reporting turned on in the php.ini or user.ini file? Is anything logging to the error_log file in /core or /admin?

Can you identify the file that is causing the error? According to the error, it is near ')' in line 2 - but it doesn't say what file. Is the error shown on the screen when submitting a PIREP? Is error logging ON? Any clues in the error_log file? Have you check the console (in Chrome browser) for any clues? I have never turned error reporting off - so I am of no help to you on that front.

Instead of hiding errors, you may be better served to install a fresh copy of phpVMS to a subdomain and link smartCARS to it to see if the error is still there. Of course, leave the new install totally default, including the default skin. If it works in a default phpVMS setup, you will then know that either your skin or possibly one of your modules or other edited file is causing the issue. Then it's just a matter of determining which one. If it doesn't work with a default install of phpVMS on your hosting, chances are your hosting isn't set up correctly. I am not a fan of hiding errors. That tends to cause further issues in the future - when your host updates their software.

Told by whom? The most current dev build will be the best for you to use. It's not unstable, but it may still have a few issues. In any case, it is MUCH better than Beta 4.