Configuration

This guide covers the configuration of CruiseAppy plugin options, environment variables, and integration settings to ensure optimal performance and compatibility with TravelTek and WordPress.

Plugin Options

  • Accessible via the WordPress admin dashboard under CruiseAppy Settings.
  • Key options include:
  • API Credentials: Enter TravelTek username, password, and endpoint URL.
  • Default Currency & Market: Set the default currency and market ID for cruise searches.
  • Cabin Selection: Enable/disable advanced cabin selection features.
  • Payment Gateway: Configure supported payment gateways and passthrough settings.
  • Search Settings: Adjust search filters, smart package options, and result limits.
  • Language & Localization: Set default language and enable WPML integration for multilingual support.

Environment Variables

  • Defined in wp-config.php or via server environment.
  • Common variables:
  • CA_DB_NAME: Database name for CruiseAppy data.
  • CA_DB_TABLE_PREFIX: Table prefix for plugin tables.
  • CA_WEBSITE_URL: Base URL for the site.
  • CA_WORDPRESS_PATH: Absolute path to the WordPress installation.
  • CA_TT_USERNAME, CA_TT_PASSWORD: TravelTek API credentials.
  • CA_TT_LANGUAGE: Language code for API requests.
  • CA_PRICES_FALLBACK: Enable fallback pricing logic.

Integration Settings

  • TravelTek Integration:
  • Configure API endpoints and session management.
  • Set FTP credentials for automated data import.
  • Adjust import schedules via cron jobs or WP-CLI.
  • Advanced Custom Fields (ACF):
  • Define custom field groups for cruise, cabin, and booking metadata.
  • Automation Scripts:
  • Ensure script paths and permissions are correctly set in the plugin configuration.
  • Update .htaccess and .htpasswd for secure access to XML and import directories.

Security & Compliance

  • Enable PCI DSS and GDPR compliance options as required.
  • Restrict access to sensitive directories using .htaccess and user roles.
  • Regularly update API credentials and review access logs.

Best Practices

  • Always back up configuration files before making changes.
  • Test configuration updates in a staging environment before deploying to production.
  • Refer to the technical specification PDF for recommended settings and integration workflows.