Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.
PLEASE READ - Webmaster Support Forum
This forum will be retired in the near future. Please direct all queries to our dedicated GitHub support page https://github.com/vatsimnetwork/developer-info/discussions 
Here you can find documentation on our services and we are continuing to migrate pertinent information into the Wiki pages https://github.com/vatsimnetwork/developer-info/wiki

VatsimPHP updated to support new data feed JSON v3


Jelle Vink
 Share

Recommended Posts

Jelle Vink
Posted
Posted

VatsimPHP is updated to use the new data feed API, please update at your earliest convenience to the latest 2.0 or 1.0 release. The legacy data feed is deprecated and is slated to be removed by March 1st 2021. 

This is a non-breaking change and should not require any code change on your behalf. File a Github issue or mention me on discord #programming-talk if you experience any issues.

  • Like 4
Link to comment
Share on other sites

Liesel Downes
Posted
Posted

In case this hits anyone else, the date/time format for the time_logon field has changed, at least to the point where our parsing code died. Just use Carbon::parse($variable['time_logon']) and it will work.

https://github.com/czqoocavatsim/czqo-core/commit/de4bb2ad253167a0430f22623015da25490849fa

(Not a breaking change don't worry Jelle lol) 

Liesel Downes
she/her/hers

Link to comment
Share on other sites

  • 2 weeks later...
Jelle Vink
Posted
Posted

@Liesel Downes sorry just notice your post. I have reverted to the old format to keep it backwards compatible as per https://github.com/skymeyer/Vatsimphp/issues/35. Another fix related to expected array keys as been addressed (https://github.com/skymeyer/Vatsimphp/issues/38). Latest v1.x and v2.x have those fixes.

I'm planning a new v3 which will introduce proper objects and get rid of parsing just plain arrays. Since there is finally a better API definition, this will be much easier to do so instead of the guess work and assumptions. I want to keep v1.x and v2.x to function as they were. If you notice anything else off, please file a github issue and I'd be happy to address them.

Link to comment
Share on other sites

  • 3 months later...
Elias Stassinos
Posted
Posted

Can you please the differences between v1.x and 2.x? Thanks.

__________________________________________________________________________________________
Elias Stassinos - Author of PTTBuddy - Automatic volume control while you fly / play /stream
My FS Photos - My MSFS Settings

image.png

Link to comment
Share on other sites

 Share