Nabeel

Basically the problem is that in ACARS programs you can't enter a leg, so it's best to be kept with the flight number, makes it consistent

Append the leg to the flight number: VMS1122A VMS1122B VMS1122-1 VMS1122-2 The legs column in the DB isn't used at all. It used to be there in the very first versions, but once ACARS apps came into play, the leg is useless since you can't specify that in an ACARS app, only the flightnum, and parsing it out is a pain. So I just say to append it to the flight number, and it's all treated as one number. So the column is there, but not used for anything. In this next version that column will be dropped

Not in the parent div, but in the table columns (<td>) tags, use a fixed width

Not without changing the code itself, I was planning to make that adjustable, but never got around to it

What do you mean?

Legs were removed a long time ago. If it's the same flight number, then they will just overwrite each other.

As of next beta: http://docs.phpvms.net/_media/development/searching_and_retriving_schedules

Where you give permissions, also add the ACCESS_ADMIN permission

For the adult/children, that can be passed to the next page, and you can do some random logic with the price. For the day of arrival/departure, you have to determine what day of week it is, and search by that, and then arrival/departure. But thanks for reminding me, I was starting to write a multi-search function, which would search on whatever parameters you pass to it: <?php // Returns KJFK flights on sundays $data = array('arricao'=>'KJFK', 'dayofweek'=>0); $results = SchedulesData::getMultiSearch($data); // return VMS flights from KJFK, departing during 18:00-59 hours (% is SQL wildcard) $data = array('depicao'=>'KJFK', 'code'=>'VMS', 'deptime'=>'18:%'); $results = SchedulesData::getMultiSearch($data); This would facilitate any custom searches or modules which want to return specific data, and you can pass in any column to search on which is in that table. I added a ticket for it: http://bugs.phpvms.net/ticket/110 I will probably write a similar function for PIREPS.

You have to also add "ACCESS_ADMIN"

May have found one source of the slowness, I was looking through the vacentral log in the log folder. I didn't implement the throttling code for va updates, so I'll implement that for the next update.

Thanks, I also need the acars.txt file though

There's plenty of code examples around, try taking a crack at it, you have the above as well.

I'll check it again, but it uses the same code.

Fixed admin PIREP list bug, also added some per-airline stats. Mostly minor fixes. Added a different type for showing PIREPS which have already been approved. Using two different style, if you guys prefer the PIREP listing for the ones which have already been approved for all of them, I'll make that the style for all of them, instead of using the old style for PIREPs which are awaiting approval. Fixed the "Reset Distances" to calculate using the arrival and departure airports, instead of basing it on the schedules (which will help for you who are doing "random" flights which aren't in the schedule) And just post the checkinstall.php if you can. Thanks

Revision 819: fixed #90 fixed #108 fixed #101 fixed #82 fixed #10717 December 2009, 1:34 pmfixed #90 fixed #108 fixed #101 fixed #82 fixed #107Source: Revisions of /Download from http://downloads.phpvms.net/phpvms.beta.zip

Thanks, new build is going up right now

I personally would say don't allow non-airline users. Opens up the possibility for spam and other problems

Used fixed width colums

Sorry, here it is <?php /* Uncomment this code if you want only schedules which are from the last PIREP that pilot filed */ if(Auth::LoggedIn()) { $reports = PIREPData::getLastReports(Auth::$userinfo->pilotid, 1, PIREP_ACCEPTED); if(is_object($reports)) { # IF the arrival airport doesn't match the departure airport if($reports->arricao != $route->depicao) { continue; } } }

You can add that bit of code in the template, schedule_details.tpl <?php // under the foreach($allroutes as $route) { if(Auth::LoggedIn()) { $reports = PIREPData::getLastReports(Auth::$userinfo->pilotid, 1, PIREP_ACCEPTED); if(is_array($reports)) { # IF the arrival airport doesn't match the departure airport if($reports[0]->arricao != $route->depicao) { continue; } } }

Seems like maybe you're missing a float in the parent div

Change DEBUG_MODE

Will be fixed in next beta

Good to hear. Always keep backups