DisposableHero

What does the log says ? You need to share it to get support I am trying to help one of your friends, probably the admin for the same error. Simply your server is not accepting requests (according to the log your friend provided), so if you can share your log, which can be found on acars/logs folder, we can have a look and compare it for similarities.

Simple logic to see what is needed is to create a manual pirep or check an acars pirep directly from the database, then you can prepare your old data to match the new fields and import via some sql queries. Or of course you can write a custom module, utilizing laravel features to make it more complex if you wish. Most important things is the data units, flight (pirep) times are in minutes and all weight / fuel values are in pounds (lbs) for phpvms v7 database (regardless what you select for display). Also you may need to match your old pilot id's in those pireps with new user_id's you have in your system (don't mix them up with idents, I am talking about the real database indexed id numbers of users) Then you may need to match your old airline codes with your new airline_id's to have more matches / reflecting details. You can probably use the same timestamps for created_at, submitted_at, updated_at fields of v7, it will not harm the system but if you have detailed times you can use them too (created_at is the time a flight is started, submitted_at is the the it gets filed etc.) Pirep type (manual/acars), pirep state, pirep status can be same for all these imported all pireps. In theory if you can match the pilot id's with their old pireps, nightly cron can re-calculate their pirep counts and times according to that data (pilots will be happy). What you will lose is financial details of those pireps (can be done if you want to go that deep but I think this is not important compared to the pirep itself), and detailed acars data (like logs, flown points etc) you may have in that old system. Good luck

Well then there is something else is going wrong, I know it works as designed by defining your route code there

Technically there is/was no need to edit the widget itself, the event "route code" is defined at module admin area and it works both for API endpoint and Event Widget. No need to edit/alter line 16 of the widget controller as it simply reads the above definition.

So you want a "landing page", preferably outside of phpvms v7 namespace, something like a wordpress website which you can edit as you wish. It may not be that easy to achieve, because v7 "pages" system is not designed for that purpose. You can still have it by some tricks and injection logic of laravel but I am not sure that it will give you the best results out of the box. At minimum, you may need a modified app.blade.php which will be used only for that home.blade.php, and in that home.blade you can load a "page" created at admin side by (or maybe you can load more as per your design needs). And then display it without escaping html special chars, so it can be displayed as designed in a WYSIWYG editor. Or you can have a real landing page, with any CMS you like to use (like WP or Joomla etc) and have your phpvms v7 located under a subdomain like many of VA's around. Imagine https://phpvms.net (landing site) and https://demo.phpvms.net (phpvms v7) Good luck

As I wrote in my first reply, it all depends on what you want to achieve, the method will then become relevant... I would not recommend running connections and sql queries inside blade files but in the end it is your va and install, it will be up to you Good luck.

Try using html / iframe or with some php (and laravel) knowledge you can read data with curl (or guzzle) and then process it or you can place widgets to that home.blade.php once and then forget it completely. It all depends what you need and how you want to do it but most of the time anything is possible. Good luck

https://docs.phpvms.net/help#vmsacars

I am not a developer either So we are same, in fact you can be better than me (considering your technical knowledge on Sharepoint), I am an OCC Manager of a real airline, just doing all these virtual aviation stuff and development as a hobby to somehow clear my mind from daily workload What you did was the correct way to be honest, you only missed the cache stuff in the beginning but solved it after getting the server error. Glad to hear that you solved the mail stuff too, in that part, we really can not help people much as it is 99% of the time custom and not generic stuff to advise easily. Enjoy your updated and moved v7

You can change the installation location or file locations without re-installing or deleting the database. Good luck

https://docs.phpvms.net/config/email

Installing methods did not changed, they were always same (only 1st and 2nd suggestion was swapped due to their usage frequency) ... Unfortunately, what you did is the worst and most unsecure method to install / run phpvms v7, and it was always like that. What your friend did back in time was one of the suggested methods and it is still ok to use v7. https://docs.phpvms.net/installation/uploading Hope this helps.

Same logic applies, nothing different Replace the files under phpvms folder of yours with the ones from latest dev (simply unpack latest dev in that folder), then copy over the public folder contents over your public_html folder.

Docs link is at the top already (which you have found too) Good luck with the update

Good news, glad you solved it. It is up to you, update or do a fresh install... Just use latest dev build, how you do it is just a choice for now. If you have nothing to lose, fresh install will be easy, but I would prefer updating to have some practice for future updates