Jump to content

Nabeel

Administrators
  • Posts

    8151
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by Nabeel

  1. 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.

  2. Once you get used to the way the system is designed it's pretty easy.I think though that the template files should be included in the "skin" folder/file instead of as part of the core package.The way it stands now if I change skinning templates I have to go in and manually change or recreate the template files. I think the one in the CORE files should be the default and any similarly named files in the SKINS folder should override the defaults. However that may be very difficult to code at this stage and I don't feel setting it up that way should be such a high priority that it detracts from the overall work.*Updated* I also wonder how easy it will to upgrade to subsequent versions if the templates get overwritten everytime I install a new build
    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.
  3. 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 icon_e_smile.gifHopefully I should have the next build by this weekend.

  4. Integration with own VA website. I would like to have the ability to intergrate this VA system into a website rather than having it separately.Regards,Zee
    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.
  5. 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.

  6. Download at: http://phpvms.net/docs/downloadsHopefully the problems you guys have reported are fixed.Build 286 04.15 * Rank is now editable * Adding/Editing rank doesn't throw "Not Number" error * Add Schedule form moved out of popup (the form was just too large) - let me know if the popup is a problem anywhere else. * Confirmation done by admin, instead of automatic on email confirm * All accepted PIREPs show up on one map * Installer fix * Rewrote Google Maps code, class based, makes it easier for add-ons and also any other maps * Show some graphs on Pilot Center, like aircraft flown statistics * Database updated to fix hitting integer limit on distance/cruise Known Problems: * Add Schedule form has a giant gap in Firefox * No email is sent out yet when pilot is accepted or confirmed * Default login form is ugly. Yup, it's a problem =DClean install optional, but run these queries to update, change the phpvms_ if your prefix is different

        ALTER TABLE `phpvms_aircraft`    	CHANGE `range` `range` VARCHAR( 15 ) NOT NULL DEFAULT '0',		CHANGE `weight` `weight` VARCHAR( 15 ) NOT NULL DEFAULT '0',		CHANGE `cruise` `cruise` VARCHAR( 15 ) NOT NULL DEFAULT '0';    ALTER TABLE `phpvms_pilots` MODIFY COLUMN `confirmed` INTEGER UNSIGNED NOT NULL DEFAULT 0;

×
×
  • Create New...