Nabeel

You're already within PHP so change that <img src into an echo statement... I just posted the general format of it for you

For hiding those look in the other thread

Changed Files: m core/version m install/hashlist m install/sql/structure.xml m install/update.php m unittest/Tests/UserTest.php fixed update script for proper groups View complete changes Download from here

Changed Files: m admin/templates/groups_grouplist.tpl m core/common/PilotGroups.class.php m core/version m install/fixtures/install.sql m install/fixtures/update.sql m install/hashlist m install/sql/install.sql m install/sql/structure.xml mandatory groups added in View complete changes Download from here

The best way would be to rename it to the ICAO, so you can do something like: <img src="<?php echo fileurl('/lib/images/airlines/'.$airline->icao.'.gif'); ?>" alt="<?php echo $airline->name;?>" /> In a place where there is that $airline variable

That will get overridden in updates, try adding it to the very end of you local.config.php file

In that version there's no correlation between that active/inactive status and the groups that's why that's happening. I'm correcting that in 3.0

if($pilot->retired) { continue; } That line goes into the existing template's foreach loop

Just bumping this one up since it's the more recent

Changed Files: m admin/modules/PilotAdmin/PilotAdmin.php m admin/templates/pilots_detailtabs.tpl m install/update.php fixed #39 group tab refresh View complete changes Download from here

Status types has been expanded a bit: Config::Set('PILOT_STATUS_TYPES', array( /* DO NOT CHANGE THIS ACTIVE NUMBER OR STATUS OR THINGS WILL BREAK!!! */ 0 => array( 'name' => 'Active', # The title to show in the dropdown 'message' => '', # Message to show if they can't login (below is false) 'default' => true, # Should this be their default status? 'canlogin' => true, # Are they allowed to log in 'active' => true, # Are they an active pilot? 'autoretire' => false, # Use this status for the auto-retire functionality 'group_add' => array( # ID or name of the group this user is added to with this status 'Active Pilots', ), 'group_remove' => array( # ID or name of the groups this user is removed from with this status 'Inactive Pilots', ), ), // etc ));

Yea that's been fixedin 141, that thread just has been pushed down since this one's been replied to

Changed Files: m core/app.config.php m core/common/PilotData.class.php m core/common/PilotGroups.class.php m install/fixtures/install.sql m install/fixtures/update.sql m install/includes/Installer.class.php m install/update.php m unittest/Tests/UserTest.php added automatic group add to retired statuses, installer updates View complete changes Download from here

You have to redownload that package every time there is a beta. Older ones aren't available

Thanks I'll take a looksie

Yeah, which version? There were some issues which were corrected. This has been improved a bit to in the latest. But the mailer mainly goes off of groups. The active/inactive changes the status, but doesn't place them into a 'group' which might be marked active/inactive. THis is something I can look into for the next version too, since the statuses are a bit more flexible, I can have a setting for which group they should also be placed in once the status changes

Changed Files: m admin/modules/Dashboard/Dashboard.php m core/app.config.php m core/common/FinanceData.class.php m core/common/LedgerData.class.php m core/version m install/hashlist m install/sql/structure.xml m install/templates/config.tpl m install/update.php fixed finances, version code/template for installer View complete changes Download from here

If the setting is enabled to hide flights on bid, the it won't show up if someone places a bid on the flight

Changed Files: m core/common/Auth.class.php m core/modules/Login/Login.php + core/templates/pireps_airportdropdown.tpl fixed pilot login error View complete changes Download from here

https://github.com/nshahzad/phpVMS/issues/38 That explains the changes. Let me try to track that message

You don't have to update them now (or at all), since the old variables are also left in there It's more for if you're starting from scratch/fresh install

Changed Files: m core/version m install/hashlist m install/sql/structure.xml refreshed checkinstall hashes View complete changes Download from here

Try http://downloads.phpvms.net/phpvms.beta.zip Ignore the checkinstall errors. Otherwise, restore to a backup which was non-beta

If you look at the existing templates, you should have an idea

You have to upload all of the files, as if you're doing an upgrade install, esp the last several commits, or things will be severely broken Those filters should still be working, check your config