Nabeel

Crap, I left out the one field in the installer.sql.That's going up right now.I can't reproduce the javascript.tpl error. It's on the second page right? We've run into this before, I thought I had it fixed.Is the template for that javascript file different?

Here ya go (it's in the original build thread, just updated it to reflect the latest)viewtopic.php?f=13&t=53&p=156#p156Should be fixed.Thanks

Nevermind, I'm uploading the patch/latest build.

Uh oh, you broke it! Is this an install from scratch I'm assuming, not over-writing a previous install?Hmm, the group ID is missing. Interesting...Thanks,I'll check it out. I probably won't have a fix tonight, it'll have to be tomorrow (sorry!)

Ah thats the in the connection test file... Shouldn't affect the installer though. I'll have it fixed. If you open the file install/dbtest.php, just change the line: include 'bootloader.inc.php'; to include 'loader.inc.php'; Thanks!

About time right?http://phpvms.net/docs/downloadsBuild 321 (the V1 build!)Remember to backup and then restore your core/local.config.php** The build was 320 but is now 321, fixing a few installer errors **New Stuff/Changes Updated framework. New Admin panel, sidebar with integrated help, cleaner design. Aiports can be selected as hubs. Pilot selects hub on registration (admin can change). Admin viewing PIREP can see PIREPs only on their hub. API Documentation (http://www.phpvms.net/docs/api) for plug-ins. Public Pilot profile is available. Deleting schedule now asks "Are you sure?". Admin can edit profile fields of a user. User edit tabs fixed up Added link to latest PIREP RSS feed in admin panel. RSS Feed for latest registrations RSS Feed for latest PIREPS Map size can be changed (see below "Additional Settings") Pages enable/disable, public/private options. Admin panel sidebar shows some more stats. Code streamlining (massive!). MySQLi blocker bug fixed; allowed back as an option in the installer. Google map lat/long is centered when route is shown. If a page isn't there (physically), error is properly displayed. Updated Queries ALTER TABLE `phpvms_airports` ADD `hub` SMALLINT NOT NULL ; ALTER TABLE `phpvms_pilots` ADD `hub` VARCHAR( 4 ) NOT NULL AFTER `location` ; ALTER TABLE `phpvms_customfields` CHANGE `public` `public` SMALLINT NOT NULL DEFAULT 'y', CHANGE `showonregister` `showonregister` SMALLINT NOT NULL DEFAULT 'y'; ALTER TABLE `phpvms_pilots` CHANGE `confirmed` `confirmed` SMALLINT UNSIGNED NOT NULL DEFAULT '0', CHANGE `retired` `retired` SMALLINT NOT NULL DEFAULT 'y'; ALTER TABLE `phpvms_pages` CHANGE `public` `public` SMALLINT NOT NULL DEFAULT '0';ALTER TABLE `phpvms_settings` CHANGE `core` `core` SMALLINT NOT NULL; Additional Settings: The following can be added to your core/local.config.php to over-ride the default values: Add them at the end, before the ?> tags. local.config.php is not over-written during updates. // Change the side of the Google Map which shows $Config['MAP_WIDTH'] = '600px'; $Config['MAP_HEIGHT'] = '400px';

Hehe... new build is going up within the next half hour or so.

Yeah sorry about that... if you look at this thread:viewtopic.php?f=13&t=47I'm hoping to have a new build out sometime today, just working out a couple of other bugs.

I'm building a quick FAQ for the "prelaunch".Any tips, etc you have which I can just put up there?This thread will stay open as well for any other tips/suggestions.Yes, this means a release is (somewhat) close!

It pops up a box asking if you're sure. The multiple entries I might implement, but it's quick enough to double click through. RSS feeds are generated on PIREP file. So you can subscribe. I can also generate a feed for pilot joining. I'll see about revamping this to include an email sent. Do you mean just in the list?I took out the sorting while I was revamping that section. It'll be back.

Yep, this has been fixed already

Sure.Extract this to core/commonAuth.class.zipAuth.class.zip[/attachment:2neloho4]That alone above should work, but I included this also (I can't remember if both were needed).Extract this to core/modules/LoginLogin.zip[/attachment:2neloho4]I'll have a new build out by Wed the latest. Most likely Wed night. Thanks, sorry about that! Login.zip

Well since it seems like you're the only one testing hahah I'll just send the patch over to you.

Hmm I just added the code to check that. Lemme see what's going on.

Download: http://www.phpvms.net/docs/downloadsShould be pretty solid.New Stuff Officially sync'd with Codon framework (http://www.nsslive.net/codon) Added license information to source files (GPL'd) Pilot profile shows PIREPs for that pilot Ranks are edit-able Images for Ranks - in the options, enter the URL to the image, full or the path to the image from the root Editable/Deletable schedules Login notifies the unconfirmed/rejected pilots, disallows their login Fixes PIREP/Schedules disconnected so editing/deletion doesn't affect NOTE: This *requires* the updated query below, or else you will loose any PIREPs made on that schedule Pilot profile moved out of popup box (easier to work with) Template over-riding is working properly All of the schedules show up properly Prettied up Admin Panel Reorganized PIREP page Some updates/improvments to Google Maps code PIREP list bugfix CSS bug with huge gap fixed on some forms Settings Added: $Config['PILOTID_OFFSET'] = 1000; Add/Set this in your local.config.php; i.e a setting of 1000 will start your pilot ID at 1000. This only affects the views. Default is 0. Update Queries (Replace phpvms_ with your table prefix) ALTER TABLE `phpvms_pireps` DROP INDEX `flightnum`;ALTER TABLE `phpvms_ranks` ADD `rankimage` TEXT NOT NULL AFTER `rank` ; If the first query does not work, then drop the table and reinstall, sorry. MySQL is sometimes retarded.

D'oh. I wonder how that happened.I'll let you know when it's fixed, I'll do it in a little bit.

I've added ya.

That is how it's supposed to work. Hmm, maybe there's a bug there. I will definitely look into this for this weekend's build. I coulda sworn it was working.The proper way is to copy the template file into the folder of the skin you're using (so if you're using the "default" skin, your updated templates go into that folder, that way it's easy to package up a complete skin with it's own design templates), not in the skins directory root. And that file will be used over the one sitting in the core. I think I need to revisit the main templating engine since I wrote it a while ago for another project, it needs some fixing.But on the next build back up your templates, then put them in the folder of the skin you're using now. Or on the build you're using, try it out. I'll test this as well this week.

Seems like we're both on now.. lol. But yeah, I think I'm gonna change how the flight reports work. It's going to have to be disjointed with ACARS reports as well. I'll add in a edit/delete.Also, what about "schedule on/off" function? Would that help as well?

For the time, you can enter the time in whatever format you want. If you enter the time-zone, etc in, I should be able to manipulate it, though I'm not really sure. If you want though, you can enter both times into the field. It's open-ended really.I put the line changes in my queue, good idea, but it probably won't be for the next build, maybe the one after that. It'll require some database changes, and a new section in the admin panel. I need to plan it out. but my question is - enter a line, or choose the aircraft? I guess I'll have an option for "either/or" . Will there really be this many changes to schedules? Just trying to get some information so I can design this the best way.The problem with editing a schedule though - the schedule is linked to a flight report. So if you change the destination on a schedule, it will change it across the reports. It's linked like this so in some time, there can be some statistics. Maybe I'll have the locations unchangeable, but other data is. But that was my reasoning for not allowing deletes or edits; since one part coincides with another. I'll figure something out. But no problem, lend your input at any time Hopefully I should have the next build by this weekend.

Looks sweet!You can change the navigation, it's all CSS. Just copy the core_navigation.tpl.Also, did you include the stuff listed under "Skin Elements". http://www.phpvms.net/docs/skinningIt might be showing up behind because of the z-index. In the "topNav" class, change that z-index.But I think if you add all the template stuff from the link above in your skin, it should work.Overall, how was the skinning?

Was that in a web-client or in a standalone client?http://phpvms.devjavu.com/ticket/69

What do you mean integrate?This includes an entire shell, with custom pages, etc.You can integrate, if you include core/config.inc.php, that will suck and allow access to the API to get all of the functionality.You can edit the skins to get a common look too.Look through the docs.The API is in core/common; there will be docs on it.

There might not be a build for the next week, or week and a half. I've got finals and exams coming up so have to work on that stuff for a bit (boo)What enhancements would you like to see? So far, I've got these issues lined up:http://phpvms.devjavu.com/roadmap

Yup, this is on its way. Right now it's just news and some stats. I'm making a few static pages under the Pages section in the Admin panel, which will be included into the front page. And you can also add in your TOS, any intro or whatever you want.But the main way to do it is to copy the frontpage.tpl from the core/templates folder, into your skins folder and modify that. That's the template for the front page.In fact, you can copy any template from the core/templates folder, and copy it into the folder for your skin and modify it, it'll show that instead of the default, so you can pretty much customize the look and feel as much as you want. That goes for the navigation (core_navigation.tpl), and you can change things around. You just need to copy it. You can modify it right in that folder, but if there's an update, there's a chance it'll be overwritten.This is the main element of customization which I hope will be taken advantage of.As long as element and field names stay that same, and anything within the PHP tags. Hopefully it'll be pretty straight forward to understand the code and modify it. I tried to keep as much PHP out of the templates as possible.