Nabeel

Due to some... bad decisions... I made when starting phpVMS, template files are pretty much plain-text. Even though I've posted instructions, and included in the default install instructions on how to add the .htaccess, there's still ways of getting someone's template files. This is causing all sorts of problems with theft. So what I'm thinking of doing are two things: Renaming all template files from. tpl to .php - this allows for the PHP code to be hidden Adding a code-check to make sure phpVMS is calling the template, and if not, nothing shows This will be a backwards incompatible change, but I feel like it's worth it. The second part to this is - I will include instructions on how to do this for your current install. I want to make other drastic changes to templates (mainly organization and moving them around), but I don't know if this is worth it - mainly organizing the templates by module in separate folders (which is the standard of how it's done). What are people's thoughts on this? Any guinea pigs?

Changed Files: m .gitignore m admin/templates/groups_grouplist.tpl m admin/templates/pireps_list.tpl m core/common/PIREPData.class.php m core/common/StatsData.class.php Merge branch 'master' of github.com:nshahzad/phpVMS View complete changes Download from here

Changed Files: m core/common/PIREPData.class.php m core/version m install/hashlist m install/sql/install.sql m install/sql/structure.xml fixed #70 umambigious pilot field causes pirep count error View complete changes Download from here

Changed Files: m admin/templates/groups_grouplist.tpl Merge pull request #69 from Vansers/master Fixed issue with users not allowing to edit custom groups. View complete changes Download from here

Changed Files: m admin/templates/groups_grouplist.tpl Fixed the issue with phpVMS users not allowing to edit custom groups, but allows them to edit the core groups. This fix will now allow you to edit custom groups, but not the core groups anymore. View complete changes Download from here

Changed Files: m core/common/PIREPData.class.php Merge pull request #68 from Vansers/master Doh! View complete changes Download from here

Changed Files: m core/common/PIREPData.class.php Fixed SQL Error Syntax View complete changes Download from here

Changed Files: m admin/templates/pireps_list.tpl m core/common/PIREPData.class.php Merge pull request #67 from Vansers/master Fixes the issue with incorrect pilot code being shown. View complete changes Download from here

Changed Files: m core/common/PIREPData.class.php Fixes the issue with incorrect pilot code being shown. View complete changes Download from here

Changed Files: m admin/templates/pireps_list.tpl Fixes the issue with incorrect pilot code being shown. View complete changes Download from here

Search is your friend http://forum.phpvms.net/topic/2791-realschedulelite-beta-10/page__hl__%20multiple%20%20schedules http://forum.phpvms.net/topic/148-aircraft-and-registration-numbers/page__hl__%2Bmultiple+%2Bschedules__fromsearch__1 http://forum.phpvms.net/topic/3066-need-help-scheduling-tail-numbers/page__p__20631__hl__+schedule%20+number__fromsearch__1#entry20631 Also, this has been answered before - you can't do that with the same schedule number. from april 21 you'll have to either change it in the schedule itself, or do it from another airline. It doesn't really matter, since the schedule is just a suggested, it has no bearing on what is put in the PIREP.

I don't know what you mean by excel spreadsheet? Just add two schedules in phpvms, same name, different aircraft and different days. That should do it

Can you try now?

Can you try the reset password again? Thanks

Thanks for the heads up, Dave

Sorry for the delay, you have all been approved. I'm working on the email issues

I'm working it out with my host

Just a quick question, are you guys getting emails at all? Or you are, but they're just blank?

Module

Thanks guys!

Ahh, you're right. So he needs another query to update it: DB::query('UPDATE '.TABLE_PREFIX.'aircraft SET `cond`='.$cond.' WHERE `id`='.$aircraft->id); That means you've got some other syntax error going on. Find and fix that first

After $update = OperationsData::editAircraft($params); Throw a DB::debug() To see if there's an error being thrown

You don't need to include 'minrank' => $aircraft->minrank, 'enabled' => $aircraft->enabled, Have you tried a print_r() on the $eventinfo call to see what's coming through?

Sounds like a daylight savings time issue

No