Jump to content

Nabeel

Administrators
  • Posts

    8142
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Nabeel

  1. Doh!

    writedebug($data);
    print_r($data);

    Didn't remove the print_r()... heh. I changed that on my side so it'll be corrected... Thanks! I end up leaving something, funny thing is, the writedebug() was so I didn't have to do print_r(). Sorry about that...

    Also, don't remove the XLR before the numbers in the pilot ID, just remove it from the CompanyICAO. It's the way I need the complete ID and code of the pilot, while I can change that going forward, it'll take a few places to change it so it accepts both (I've changed other code so now I can take only the ID number).

  2. Your PilotID is doubling - in youre config file, set CompanyICAO to blank (CompanyICAO=)

    As for debug mode, I haven't found a way. I use that log to debug as well.

    What you can do is, the top line:

    pilot=XLRXLR0003&date=2009/01/04&time=23:22:00&callsign=&reg=F-TACB&origin=LFLL...

    Put it in your URL as:

    yoursite.com/action.php/acars/fsacars/pirep/?pilot=XLRXLR0003&date=2009/01/04&time=23:22:00&callsign=&reg=F-TACB&origin=LFLL...

    And you can see the system response (should be "OK")

  3. A new section has been added with tutorials, more will be added as they are created:

    http://www.phpvms.net/tutorials

    If you can create video tutorials, I will post them up, especially if you understand some aspect of the system  ;)

    Roger is working on skinning, I'll do a skinning tutorial as well, and also a tutorial on how some aspects of the systems work.

  4. I also notice when they get sent in with fsacars on the website under the pilots page if you click on a pilot it doesn't show a prep at the bottom as if you were to fill one out on the website. I didn't know if this is in the matter of being fixed but i just thought i would let you know.

    Do you see it in the admin panel, under that pilot?

  5. It does see the OK message (I'm assuming), I send out an OK either way. I don't always get the error. I can't really ask the FSACARS people either about it, since they seemingly closed shop.

    It usually shows up when you click "Send Log", but when you accept the PIREP, it should send the PIREP right then. I haven't had the time to really diagnose it in too much detail.

  6. Ask your host if they can flip that around for you first, usually it's not a big deal since it's an entry in the virtual host section which is already setup for you (I know my host has done it for me).

    To move it, no, just move the files and change the SITE_URL in the core/local.config.php, as well as in your skin files

  7. Yeah, I'm changing this so it doesn't kill your server everytime it does a lookup. As for it setting to zero, that is a mistake I made in create the column (as an integer, not a float value), I'll fix that, but it's gonna count the time based on PIREPs. Flight tim in schedules is just a carry over which was going to be used as a check against a really wrong PIREP flight time.

  8. It'll remove the # sign. Weird, I'll take a look a bit deeper, it was working. Arg.

    And as for multiple backgrounds... right now no... I'll put it on my list though :)

    Oh, you guys know it'll take the size of the background image, so you can adjust the size through the bg image size. If you thought it was too big ;)

  9. Did the background change when you hit the reset.

    Try it without the # sign

    Actually I found an error in my code,

    To fix it for now, open core/common/pilotdata.class.php, around about line 486, theres:

    sscanf($color, Config::Get('SIGNATURE_TEXT_COLOR'));

    Replace it with

    $txtcolor = str_replace('#', '',  Config::Get('SIGNATURE_TEXT_COLOR'));
    
    	$color = sscanf($txtcolor, '%2x%2x%2x');

×
×
  • Create New...