freshJet Posted December 12, 2011 Report Posted December 12, 2011 The inactive pilot system within phpVMS is atrocious. Honestly. I'm sorry to say it but it really is. I have a pilot who can no longer login. He filed 2 PIREPs recently yet the system says he's inactive. I reset him to active and it went back to inactive. My local.config.php states that inactive pilots should be able to login, yet this doesn't work. I'm getting really annoyed about this and something needs done. I have a bunch of pilots who can't fly because they can't login. This needs fixed - and fast. Quote
Tom Posted December 12, 2011 Report Posted December 12, 2011 Turn it off? Obviously if it's not working and there's no clear immediate fix you just turn it off until you know it works... Quote
freshJet Posted December 12, 2011 Author Report Posted December 12, 2011 How do I turn it off? No doubt that won't work either Quote
Tom Posted December 12, 2011 Report Posted December 12, 2011 # After how long to mark a pilot inactive, in days Config::Set('PILOT_AUTO_RETIRE', false); Quote
freshJet Posted December 12, 2011 Author Report Posted December 12, 2011 Still won't work. Do I need to set all pilots to active again? Quote
freshJet Posted December 12, 2011 Author Report Posted December 12, 2011 OK, I've done that using phpMyAdmin. It worked. But now I can't access the Admin Panel due to unauthorised access. Quote
freshJet Posted December 12, 2011 Author Report Posted December 12, 2011 There is nothing to determine admin access or not in the pilot database, how come it affected it? I changed all pilots to 0 in the retired field, and I changed all of the signature backgrounds - that's it! Quote
freshJet Posted December 12, 2011 Author Report Posted December 12, 2011 Anyone? I need my Admin Panel back!!! Quote
TennShadow Posted December 13, 2011 Report Posted December 13, 2011 Anyone? I need my Admin Panel back!!! By default the administrator group id is 1. If you look at the phpvms_groupmembers table is your group id 1? Quote
Strider Posted December 13, 2011 Report Posted December 13, 2011 If you are using a beta, this is what can happen. Don't use beta's as working sites. Only use them as test sites, to test the beta and report the bugs you find. Quote
freshJet Posted December 13, 2011 Author Report Posted December 13, 2011 OK fixed. What's the latest full version? Quote
Jeff Posted December 13, 2011 Report Posted December 13, 2011 Version 2.1.934 (Located in the bottom right of your Admin Center) Quote
freshJet Posted December 13, 2011 Author Report Posted December 13, 2011 That's what I'm running Quote
Administrators Nabeel Posted December 15, 2011 Administrators Report Posted December 15, 2011 An ID or something must have changed when you were editing it. That's weird - there are no FK relationships for that to cascade. The retire pilots doesn't work very well, true - any suggestions on what/how to fix it? Quote
Guest lorathon Posted December 16, 2011 Report Posted December 16, 2011 I completely changed the "Stable" code to retire pilots. The one thing that I never liked was that if a pilot never logged in the pilot would not be retired.So I change the query to be based on join date not the last log in date. Here are the 2 queries. // Retire pilots who have never logged in after x days from joining $sql = "SELECT * FROM ".TABLE_PREFIX."pilots WHERE DATE_SUB(CURDATE(), INTERVAL {$days} DAY) > `joindate` AND `totalflights` = 0 AND `retired` = 0"; $results = DB::get_results($sql); // Retire pilots who have not flown in x days $sql = "SELECT * FROM ".TABLE_PREFIX."pilots WHERE DATE_SUB(CURDATE(), INTERVAL {$days} DAY) > `lastpirep` AND `totalflights` > 0 AND `lastpirep` != 0 AND `retired` = 0"; $results2 = DB::get_results($sql); Quote
RogerB Posted December 16, 2011 Report Posted December 16, 2011 This is funny..made me laugh...not sure why.. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.