VAMwp

0

VAMwp is a WordPress plugin that provides integration with a Virtual Airlines Manager (http://virtualairlinesmanager.net/) installation on the same server. VVAMwp 1.0.0 is the current v

Version
Last updated
Active installations
WordPress Version
Tested up to
pa_tag
Rating
Total ratings
This plugin is outdated and might not be supported anymore.

Description

VAMwp is a WordPress plugin that provides integration with a Virtual Airlines Manager (http://virtualairlinesmanager.net/)
installation on the same server. VVAMwp 1.0.0 is the current version of the plugin which supports VAM 2.6.2.

VAMwp provides a set of widgets which can be included in any WordPress site using any theme to create a rich WordPress-Based
web site for a virtual airline. The roadmap is to allow complete management of the VAM airline from within WordPress without
the need for end-user visitors or pilots to access the VAM administration portal — which would only be needed for managing
the airline itself by airline staff.

At this time, the widgets provided allow the creation of a visitor-facing web site presenting a rich set of widgets to
present pilot rosters, fleet details, hubs, and flights. These widgets can be combined in many different combinations in
most WordPress sites.

Future releases will provide widgets to allow pilots to book flights, file PIREPs and more.

VAMwp was originally built for the launch of the new Finnair Virtual airline (http://www.finnairvirtual.fi/) but is now being
packaged and released to the wider VAM and WordPress community.

The plugin is also available on GitHub for download as unpackaged source code at https://github.com/likeablegeek/vamwp.
Documentation of VAMwp is available on GitHub in the project’s Wiki.

It is worth noting that VAMwp is a work-in-progress. As such it has some limitations:

  1. The current version presumes WordPress and VAM are installed on the same server in the same virtual host
    (i.e. under the same base url such as http://www.mydomain.com/). The typical installation pattern is that the
    VAM installation directory would be at /vam/ and the WordPress site would occupy the root directory of the
    site.
  2. To fully integrate the user experience with VAM currently requires the creation of a set of rewrite rules
    for mod_rewrite (if using Apache as an HTTP server) or equivalent for nginx or other HTTP servers. This is to
    allow links from various widgets to redirect away from the back-end VAM portal (if desired). This is explained
    with an example in the documentation but is not required to use the plugin.
  3. There is an underlying assumption that users of the plugin fully understand how to use VAM and their VAM
    installation. The plugin and its documentation in no way simplifies or supports the installation of VAM and
    the configuration of a virtual airline based on the VAM platform. Users needing support to install, configure
    and manage VAM should refer to the VAM documentation and the VAM help and support forums.