Nabeel

As an admin, you do not have to do any additional setup to get FSACARS working. Simply download FSACARS (http://www.satavirtual.org/fsacars/), and install it (make sure you install the update as well).Then log into your VA, in the pilot center, there is a link to "Download FSACARS Config". It will prompt you to download a file; save the file in your FSACARS directory (typically Program FilesFSACARS). Then open FSACARS, select your VA, and get flyin! The FSACARS config file you downloaded contains all of the necessary information to fly.

Worked fine on my test site. The .40 shouldn't do anything since it's treated as a normal string...Can you duplicate it? Maybe it was something else?

Wait what?Blew it up? Meaning..?Then he entered the same thing and it worked? I'm lost... lol

I dunno, it has notes. I mean I can add it... lol. There goes any hope of the update this weekend I'll add it in.

Hahaha... sorry man.You'll need to add the parameter also in the admin/module/operationsdata, it's in there somewhere. Did you add the parameter to the function to pass it? Well this will get overwritten on any update.Wait, I don't think I added the notes field yet.. LOL I can't remember. I'll double check that. Would that do? It's still sitting my 'to-do'.

Well you can add "custom fields" to a profile. I'm thinking of doing a profile picture thing.

There's a notes field. Otherwise to add a field, it has to be done in the sql code and all that stuff, its not completely automatic.

I fixed that for the next update.

Ouch, which FF version?Personally I test on 2.0, and 3.0, and I'm now using 3.1 beta, no problem. Haven't heard from anyone else.But yes, send me your info.Did you try re-uploading the admin folder? Perhaps a css file didn't fully upload.Sorry for the late reply! I remember to check, and then forget again! lol...

Hmm, at this point, it is not.

Good to hear, some hosts offer both 4 and 5, and 5 sometimes has to be enabled through an htaccess or something.

That's interesting.What browser are you using?It shouldn't, the "skin" for the admin panel is separated in the admin folder. But if you think you overwrote something, just re-upload the admin/lib folder.But we can start with, what browser?

Which PHP version? I'm wondering if it has to do with that, though I'm running 5.2 myself.Can you also try running it from the command line as above?

Thanks, sorry for the late reply:Very odd, I don't see any problems.Do you get any errors running the install file from the command line? (it won't install, but might be interesting to see if it errors, to eliminate an apache error).The command would be:/usr/bin/php -f /path/to/install.php

Can you zip up and send install/install.php to me? nabeel at nsslive dot netIt's a really odd error.Edit:I just downloaded the "full install" from the "downloads" section, and checked out the install.php, didn't spot any errors. Just ran the install as well, seemed to work fine.Are you running a Windows or Linux server?

Try reuploading the entire package from scratch (redownload, etc). I've seen that before when a file did not completely upload properly (ftp programs do that often, if there's a hiccup).If that doesn't work we can go from there.

Yeah... shouldn't be too difficult. But I also said that about many things before I actually started them...

Is it per hour based on rank?

Hey there,Interesting. Try reuploading the file. I just checked the line (http://phpvms.devjavu.com/browser/trunk ... ll.php#L29), weird spot for an error. Try reuploading though.Also, just checking, you're running PHP 5?Nabeel

lol.. what do you need?Then try this redirect instead of the header() call: echo '<script type="text/javascript"><!--window.location = "'.SITE_URL.'/index.php/Login";//--></script>';

Don't modify the codon.config.php.You can do this then, though you'll have to re-do the change after an update. Open core/bootstrap.inc.php, and under this line: Auth::StartAuth(); SiteData::loadSiteSettings(); Put: if(!Auth::LoggedIn()) { header('Location: '.SITE_URL.'/index.php/Login'); }

for other pages, you can include the /core/codon.config.php, and then use: if(!Auth::LoggedIn()) { die('You are not logged in'); } // they are not logged in You can also place that in your local.config.php, at the bottom before the ?>. That should do the trick.Sorry for the late reply! Just started new job, been a little hectic.

I think it's hardcoded, I"ll have to check...

Ok, lets hope that works. Though I'm not sure why that would be a problem completely? I'm wondering why you didn't see those files though.

Interesting, I tested on a windows server for a while. I don't see it up yet, but I'll keep checking it to see if I can spot the error. If you do see it, if you can copy/paste the whole thing here that'd be great.ThanksNabeel