IMPORTANT: If you are running phpVMS 5.5.x, move all the PHP template files from ‘php_templates’ into the main skin folder before uploading.
This skin is designed using the Bootstrap framework, meaning it is fully responsive and works well on all sized devices, including desktops, tablets and phones. CrewCenter is not a complete website skin, it is only a pilot center application, designed to be installed onto a phpVMS installation on a subdomain (e.g. crew.yourva.com) in addition to your ‘front page’ on your main domain, with a link to CrewCenter.
Please note that this skin is still being developed, and I hope to update it and add new features over time. You should be able to just overwrite the existing files to update it. It may also have bugs and issues. If you find, feel free to post an issue report on GitHub or reply to this topic.
If you have any feature, plugin skinning or custom VA branding requests, feel free to post a reply below or email me.
Try changing all the files to .php and change any reference from .tpl to .php.
Please note this will not work as each page has a PHP header to include ‘app_top.tpl’ and ‘app_bottom.tpl’. You would have to change every page to include the .php versions.
I am still considering creating a version of CrewCenter for phpVMS 5.5.x, so if many people want a version for it, let me know.
Sorry for the delay. I have taken the liberty of creating PHP versions of all the template files, and put them in the ‘php_templates’ folder.
If you are using Simpilot’s phpVMS 5.5.2 and need the PHP templates, just drag in all the files from ‘php_templates’ into the main skin folder, all done!
If there are any problems please let me know. I’m now working on skinning the bid overview and comments pages.
Is ther any way of linking the 2 sites so you don’t need to input all the information again?
Not quite sure exactly what you mean, I’m assuming you want to transfer an existing user database to a new phpVMS installation.
You should just be able to export tables (for users, fleet, airports, schedules etc.) through phpMyAdmin and import them to the new database. An alternative is copying the entire phpVMS installation over to the subdomain and changing the Site URL to the new URL of phpVMS in the config file.
thanks for the info, But cant you make it as a module with its own template, so we can install it in our main va’s site?
I don’t have any intentions at this stage to do something like that, however, I have successfully just tried and tested this:
Install another phpVMS installation on your subdomain (crew.yourdomain.com), then change the database to the exact same as the main site you’re currently using. The only issue would be that both of the skins your using on both sites would need to have the same name. In other words, you’d need to change your current skin’s name on your main site to ‘crewcenter’ as well, since the configuration options are stored in the database.
Essentially, you would have 2 sites of phpVMS controlling the same database, so you can have a live ACARS map on both sites, main (for public viewing) and CrewCenter. You could even have some pages, like the profile edit page, on your main site, and have the schedules and PIREP pages on the CrewCenter if you wanted to. This is completely customizable to your needs, it just requires some HTML tweaking.