Jump to content

ProAvia

Administrators
  • Posts

    1646
  • Joined

  • Last visited

  • Days Won

    71

Posts posted by ProAvia

  1. 2 hours ago, ProSkyDesign said:

    Open admin/modules/Import/Import.php and go to line 446

    Replace this:

    
    # Check if the schedule exists:
                if (($schedinfo = SchedulesData::getScheduleByFlight($code, $flightnum))) {
                    # Update the schedule instead
                    $val = SchedulesData::updateScheduleFields($schedinfo->id, $data);
                    $updated++;
                } else {
                    # Add it
                    $val = SchedulesData::addSchedule($data);
                    $added++;
                }

    with this:

    
    # Ignore duplicate schedules:          
    $val = SchedulesData::addSchedule($data);
    $added++;
             

    this will allow you import schedules with duplicate flight code but I guess you should delete first all your schedules and then import news because this won't update the duplicate flights this will append data.

    But you will loose the ability to update the schedules. And if you just delete the schedules to upload a full set again, if the DB is set to auto-increment the record number (which is the usual default), all your old data will be screwed up. For example - you upload 100 routes to a blank schedules table, so record number 1-100. Now, since you can't update any longer, you delete the old schedules and add the new/updated ones back. The record number will start with 101 - so any data stored in other tables referencing the record numbers of the previous schedules won't be able to locate that data cause you deleted it.

    Seems way more trouble than it's worth - unless you want to manually edit the DB directly.

  2. You can import flights - schedules - thru the admin panel. There is no facility in the admin to import PIREPS or pilots.

    You should be able to export your PIREPS from your present database using phpMyAdmin. You would then convert that export to the format used for phpVMS v7 and import that into the phpVMS database using phpMyAdmin. Be advised, there may be some fields present in your current database that aren't in phpVMS. Likewise, phpVMS may have some fields that your current software doesn't have.

    In any case, you will have to convert most all of your database tables as the format most likely will not match that of phpVMS.

  3. What version of phpVMS are you using?

    In 5.5.2.72, there are comments in local.config on where the Google map keys go.

    Add the key to core_htmlhead - in the skin folder if that file is there. Otherwise add it to core_htmlhead in /core/templates.

  4. Are you using a Windows operating system on your computer? If not, what operating system are you using?

    As I mentioned, I have had issues using Excel. OpenOffice or LibreOffice are good alternatives for Windows based systems - and both are free. 

    If you are not using Windows operating system, may e someone will have another alternative to Excel.

  5. According to their website images for that skin, it lookslike you can do it thru the admin panel.

    https://www.crazycreatives.com/downloads/phpvms-theme-jetset-basic/

    Or look in that skin folder for app_top.php or possibly core_navigation.php to directlyedit the menu. Of course,they may have named the files differently too.

    The forum over there is a mess. Neither the owner nor his moderator spend much time there. 

    EDIT - ok, the pics there seem to indicate you can change position of the nav bar, not necessarily add items to it. You may have to look in each file of the skinto see where the menu is called. Use something like Notepad++ and search each file for one of your present menu items. Once you find that one item in a file, you should be able to see how each item is coded in and add what you want.

  6. Download Composer manually to your desktop and install to your computer from there.

    You run composer in a command prompt on your computer - not on ypur shared hosting. You don't do anything with your shared hosting until you upload all the files to your site.

    Follow the steps above, you don't do anything with your hosting until the last 2 steps.

    Are you aware that phpVMS v7 isn't released yet and shouldn't be used for a live production site? There are no skins, modules or ACARS for it yet. 

    If you want to start up / run a VA right now, I suggest you use php 5.5.2 (simpilot version).

  7. Here is how I did it...

    How to install phpVMS version 7 

    • Get and install Composer to computer - https://getcomposer.org/download/ - if you haven't already done so
    • Download the latest dev of phpVMS7 - https://github.com/nabeelio/phpvms/branches - click on 'dev' under default branch
    • Unzip the downloaded file to a folder on your computer
    • Open a CMD prompt
    • In the CMD prompt, navigate to the folder you unzipped phpVMS v7 to
    • In the CMD prompt, type 'composer install' - and let it finish downloading the dependencies
    • Copy the contents of the folder with phpVMS v7 and all the dependencies to the destination folder on your host
    • In your browser, go to https://<Your_URL>/<directory_phpVMS_v7> - there is no installer like older versions, just open it and it will say something about phpvms not being installed. Press the green box to continue and follow along on the install process.

    This works for me - no guarantee it will work for others.......

  8. Logs are in .../storage/logs

    Flarum? Isn't that forum software? That has nothing to do with phpVMS v7.

    Did you install Composer on your computer first?

    So you downloaded phpVMS v7 and extracted locally, ran Composer on the extracted phpVMS folder, then uploaded the entire contents of the phpVMS v7 folder to your desired folder on your shared host?

    See post #4 here for how I did it... https://forum.phpvms.net/topic/26751-can-someone-help-me-for-installation/

     

    • Like 1
  9. On your site, go to Admin, Site & Settings, Maintenance Options. Scroll to bottom of page and look under Cron for advice on how to set up a cron job.

    The path shown there is for the maintenance script. You will need to change that to run your script. Take note of change you need to make to local.config

    Additionally, I believe if you log into your hosting account (cPanel), you should have the option to set up Cron jobs. Not sure if you need to set  it up in phpVMS and on your host.

    As for how to set up this specific cron job, you will need to rely on the documentation and/or their forums for support of your payware module.

    Once you get it working, please post back here with specifics on how you got it working. This will help other members in the future.

  10. Are you planning to use v7 for just testing purposes? It is still in developmemt and probably shouldnt't be used for a live site. And we are still waiting on skins and modules to help customize it.

    An updated development version was released this morning.

    I download it locally, extract the files and run composer locally too. Then I upload the entire thing to my host. Seems to work fine when doing that. I've never tried any other way.

  11. It may be a while until you see any ACARS for v7 that supports Linux or MAC. In any case, they are going to have to get their data via XPUIPC or their own proprietary plugin.

    I was hoping the XPUIPC developer was going to update it again - but his website hasn't changed in quite some time. Hmm - maybe someone can convince Pete Dowson's son to look into XP support. 😁

  12. 1 hour ago, bbuske said:

    Any news or updates on this?

    It looks really nice and we are looking for an XP ACARS that is not using FSUIPC.

    Cheers

    I'm pretty sure there is no ACARS for X-Plane that uses FSUIPC. But there are some that use XPUIPC. There are also other addons that require XPUIPC when used with X-Plane. 

  13. Are you using phpVMS version 2.1.x or 5.5.2 (Simpilot version)?

    There are several files to compare.... 

    • /core/modules/news/news.php
    • /core/templates/news_newsitem.tpl - may end in .php instead of .tpl - this one may be in your active skin folder, which will take precedence over the one in /core/templates/
    • /admin/modules/SiteCMS/SiteCMS.php
    • /admin/templates/news_additem.php - may end in .tpl instead of .php
    • /admin/templates/news_list.php - may end in .tpl instead of .php
    • /core/common/SiteData.class.php
    • /core/common/LogData.class.php

    Compare the above files on your site to the ones in a default install (or non-edited files from a download of your version of phpVMS).

    Don't change the file names or extensions - just compare to default. Let us know what you find out.

     

×
×
  • Create New...