Wayu Shipping Orders and Tracking

This plugin is a lightweight client for connecting your WordPress site to Wayu's central shipping order and tracking service. After entering the service URL and API key provided by Wayu in the plugin settings, two shortcodes become available:

• [wms_ship_order_form] — a shipping order form. The form fields are fetched dynamically from Wayu's central service, so no coding is required.
• [wms_ship_tracking] — a shipment tracking form (requires the visitor to be logged in to your site).

All communication with the central service happens server-to-server; the API key is never exposed in the visitor's browser. Features

• Dynamic form: fields are generated automatically based on your Wayu account configuration.
• Built-in Jalali (Persian) calendar date picker, with no external dependency.
• Automatic sum of numeric fields, and smart show/hide for dependent fields.
• Tracking is restricted to logged-in users.

1.0.0

• Initial release.

1.1.0

• The order form no longer requires a forced login; specified fields are auto-filled from the logged-in user's info when available.
• Added a configurable number of form columns (1 to 3) in the plugin settings.
• Added support for new field types: landline phone, website, time, single choice, multiple choice, star rating, emoji satisfaction rating, terms agreement, map (via a locally bundled Leaflet/OpenStreetMap library), digital signature, and user file upload.

1.2.0

• The order form's login requirement is now optional; login is only used for auto-fill.
• The terms-agreement field now shows a fixed text in an inline box instead of linking to a separate page.
• Added a "Refresh form now" button in settings to clear the cached form schema after adding new fields on the central service.
• Bundled the Leaflet map library locally instead of loading it from a remote CDN.
• Removed the unnecessary load_plugin_textdomain() call (translations are handled automatically by WordPress.org).

1.3.0

• Server-side validation added for the image upload / digital signature fields: only a strict data-URI format (JPEG, PNG, or PDF, base64-encoded, max 2MB) is now forwarded to the central service, instead of raw unvalidated POST data.