Jump to content

ProAvia

Administrators
  • Posts

    1740
  • Joined

  • Last visited

  • Days Won

    78

Everything posted by ProAvia

  1. @PaintSplasher Thanks for your continued efforts and support! Looking forward to your other importers as well. Please provide a comprehensive list of the v5 modules you use and/or that your importers will work with. Different modules that provide the same basic functions can/do name their database fields differently.
  2. Not sure if it's practical or worth the time to go thru all the v2/v5 posts to lock unsolved ones. New users should be using phpVMS v7 - and old users have usually solved their issues even if they don't post their resolution. Based on increasing issues that v2/v5 users are experiencing (mostly do to shared hosting updates), it's probably time to move on to v7. In any case, as long as phpVMS v7 airport lookup is working, the above update to the v5 files (via updated VACentral API update) should allow the airport lookup to work. Not so much using the "virtualairlines.eu" website airport lookup as the website is sometimes unreachable and the OP author hasn't been on this forum in over 4 years.
  3. While you replied to a 3 year old post to a 2 year old prior post, a better solution is: At least this will work as long as the phpVMS airport lookup API is up. This phpVMS airport lookup API is the same one in use for phpVMS v7 - and has been adapted to work with phpVMS v5.
  4. Are you using the latest v7 dev version available from the v7-releases channel in discord? List the full version number here. I haven’t noticed any of what you are experiencing with users or pagination - and I’ve done the legacy import at least 3 dozen times over the last several months while helping to update and improve the legacy importer. As for any 500 errors - you will need to look on the phpVMS logs. See the phpVMS docs for their location.
  5. You are posting to a six and a half year old post started by a member who hasn't visited the forum in over four years. The website is still up, but it appears a user can't log in or reset their password.
  6. API is undergoing an update. Check discord for info and status.
  7. Be sure to use the latest phpVMS v7 dev release - not the beta.
  8. No - but it's not difficult and should take less than 1 hour. See the docs for info - https://docs.phpvms.net/
  9. Your current skin in v5 will NOT import to v7 as a theme. However, you can customize the default, use the Disposable freeware theme or do your own theme to closely mimic your present look and feel. Airports, airlines, flights (schedules in v5), PIREPS, pilots will all import. Your best bet is to install v7 using option 1 to a subdomain via the legacy import and see what it looks like and what it moves over from v5. This way, you can play around with it and tweak it without affecting your present live v5 site. Just process all PIREPS, make a backup of the v5 database and use that backup db for the legacy import. There is also an addon to import awards - although it may be for a specific v5 awards module. The same developer who did the awards import addon is working on other addon imports as well.
  10. phpVMS v2/v5 is over 15 years old. Much has changed in that period of time. It's had a good run. No software works forever. Time to move forward. phpVMS v7 is the first major rewrite in 15 years.
  11. Your current v5 modules will not work in v7. Design wise - you can customized the theme in v7 to closely mimic your v5 site.
  12. PHP 5.6 will work with that phpVMS version. You will still have functionality issues with MariaDB 10.6 though. I'd suggest installing the latest dev release of phpVMS v7 to a subdomain and looking into what is actually included and what addons are available. You may find that some of your v5 addons aren't needed. As hosts update PHP and MySQL/MariaDB versions, phpVMS v5 will have more issues and eventually cease to work. About the only way around that is to run your own VPS.
  13. V5 modules will not work in V7. They can not be easily converted and would likely need to be fully re-developed. Chances are that with MariaDB 10.6, you will find that some needed fuctions don't work as expected or at all. Check out v7. Many items that required modules in v5 are included in v7. Once v7 is in general release, I anticipate that new modukes will be developed. Go to the admon page and look in the lower right corner. What phpVMS version are you using?
  14. For phpVMS version, go to /public_html/core and look in the version file. Report back here with the contents. How old is this install? There is no phpVMS 5.6 - there is 5.5.2 and 5.5.2.72 Neither will fully work with PHP 7.4 and/or MariaDB 10.6 For full functionality of phpVMS 5.5.2.72, PHP version from 7.0 to 7.2 and MySQL 5.6 to 5.7.4 or MariaDB up to 10.2 . For phpVMS 5.5.2, PHP version 5.4 to 5.6 and MySQL 5.6 or MariaDB up to 10.2 . If your database for this install is intact, time to move to phpVMS v7 by doing a legacy import. Check the docs link in the menu at the top of the page for minimum requirements. Check if your host support all minimum requirements. I guess you could try recreating assets, airports and admin. But it may not be worth the time it takes and there may still be other issues.
  15. @Alexan If you can supply the info in the above post, we may be able to assist you.
  16. A few things. 1 - you posted in the phpVMS v7 section of the forums not the v5 section. I will move this to the v5 section. 2 - we need to know PHP version, MySQL/MariaDB version, exact phpVMS version. 3 - new install or existing install? 4 - what was the last thing you did that caused the error? 5 - did you make any changes to app.config.php at any time?
  17. Config maps? https://docs.phpvms.net/acars/configmaps What version of phpVMS and vmsACARS are you using?
  18. Don't use beta 5. Use the latest dev release available from the discord #v7-releases channel. Directly upload that package and extract to the chosen phpvms folder. If you set up a sub-domain for phpVMS, use option #1 in the docs to install.
  19. Are you using the latest dev version of phpVMS available in the discord v7-releases channel? If you can go to your website in a browser, your database settings are correct. You could possibly be missing the departure and/or arrival airport in your database.
  20. ProAvia

    Stored pages

    Each page is stored separately in the database. You can edit them thru the admin panel or (after backing up the database) directly using phpmyadmin - although it is safer via the admin panel. They are NOT stored in a file like they were in previous versions as far as I can tell.
  21. ProAvia

    Stored pages

    However you access your v7 database. Different hosts use different panels or access methods.
  22. ProAvia

    Stored pages

    Look in that database table - your answer is there.
  23. ProAvia

    Stored pages

    Database, 'pages' table
  24. Care to share exactly what you edited for other users that may want to do the same?
  25. The env.php file has been replaced by the .env file. All the email settings are in there. Return the config.php file to its default state. In addition to the link kindly provided by @DisposableHero , your hosting panel should provide an Email Accounts area with valuable info. If your hosting provides cPanel, have a look at this article to set up SMTP https://cpanel.net/blog/tips-and-tricks/setting-up-and-troubleshooting-smtp-in-cpanel/ I would suggest updating any phpVMS v7 sites you help with to the latest dev build, available in the #v7-releases channel of the phpVMS discord.
×
×
  • Create New...