Description
TNS Booking connects your WordPress website to an existing TravelNetSoft (TNS) service. Display destinations, service groups and bookable travel experiences from your configured TNS instance without manually copying the catalogue into WordPress.
A TNS account, an API endpoint and valid PublicKey/SecretKey credentials are required for catalogue, availability, booking and payment-link functionality. A TNS account is provided only after the required separate service agreements have been signed. Installing this plugin alone does not create a TNS account or supply travel products.
The plugin is distributed as one full version. There is no FREE/PRO feature split or plugin license-key activation. The external TNS service is separate and may be subject to the service operator’s commercial agreement and fees.
Features
- Destination and service-group browsing.
- A common service-list layout across destination, group and search flows.
- Search by multiple destinations and service groups, check-in date and duration.
- Checkbox dropdowns with filtering and a compact row in wide layouts.
- Dates displayed as dd.MM.yyyy; search/API values use yyyy-MM-dd.
- Service images, descriptions, itineraries, inclusions and exclusions.
- Availability and dated booking options supplied by TNS.
- Service variants, passenger choices, quantity and price breakdowns.
- A browser-based shopping cart and customer checkout form.
- Server-side recalculation of cart prices before requesting a payment link.
- Automatic Payment Success and Payment Error return pages.
- H1/H2 headings, dynamic page titles, meta descriptions and contextual image/link attributes.
WooCommerce and the TNS Explorer theme are not required. The plugin supplies its own booking/search interface and uses your active theme for the surrounding website.
External services and data use
This plugin depends on an external TNS service. Its purpose is to retrieve travel content and availability, validate booking options and request a payment URL. The API base URL is entered by the site administrator under Settings > TNS Booking; it is not a fixed analytics or advertising endpoint.
Service provider: TravelNetSoft by GOL-IT Consulting GmbH.
Website: https://travelnetsoft.com/
Privacy policy: https://travelnetsoft.com/legality/dataprotection
Terms of service: TNS service use is governed by separate agreements that must be signed before a TNS account is issued. The plugin cannot provide its connected booking functionality without that account. The signed agreements define service access, usage conditions and applicable commercial terms. Contact TravelNetSoft or the operator of the configured TNS instance through the service website to arrange onboarding and receive the agreements. These external-service agreements are separate from the GPL license covering the plugin code; no additional plugin license-key activation is required.
When information is sent:
- When a visitor opens a booking view, the website requests the relevant destinations, service groups, service details, images, itineraries, dates or prices from the configured TNS API.
- Search requests send selected country names, service-group IDs, dates and duration.
- Viewing dated options and submitting checkout send service IDs, travel dates, passenger counts, selected variants and quantities for validation and price calculation.
- Submitting checkout sends the customer’s name, address fields, city, postal code, state/region, country code, phone number, email address and optional TNS customer code, as entered in the form, together with the validated booking/cart data.
- The payment-link request includes the WordPress site’s generated Success and Error return URLs.
- Server-side SEO generation may request a service or service-group record and cache the response in WordPress for approximately five minutes.
The PublicKey, a timestamp and an authentication hash are included in authenticated API URLs. The SecretKey is stored in WordPress settings and used on the server to calculate the hash; it is not included in the plugin’s frontend configuration or sent as a plain SecretKey field. Site administrators must protect their WordPress database and API credentials.
Requests from WordPress expose the website server’s network information to the configured API infrastructure. Images supplied by the API are loaded by the visitor’s browser from the returned image URLs; these image hosts may receive the visitor’s IP address and browser/referrer information. Continuing to payment redirects the visitor to the URL returned by TNS, which may be hosted by an external payment provider. The applicable TNS instance operator, image hosts and payment provider may have additional privacy policies and terms that the website operator needs to disclose to visitors.
This plugin contains no analytics or advertising SDK, does not download executable PHP or JavaScript from the TNS service and does not collect card details in its checkout form. The TravelNetSoft website’s own analytics/cookie notices describe that website and do not mean this plugin installs those tools.
Local storage and retained data
Cart items are stored in the visitor’s browser localStorage, namespaced by website and PublicKey. The cart contains selected service information, travel dates, quantities, passenger counts, options and calculated amounts. The customer contact form fields are not written to localStorage by the plugin.
The cart remains until cleared through the cart interface, browser storage is cleared, or a successful checkout API response returns a valid payment URL. Cart removal at that stage is not proof that payment has been completed. A failed checkout request leaves the cart in place.
WordPress stores connection settings, generated return-page IDs and short-lived SEO content caches. The plugin does not create local WordPress booking/order records. Payment/booking processing and records are handled by the configured backend service.
Deactivation keeps settings and the generated return pages. The plugin does not automatically delete these on removal. Browser carts and records held by an external TNS service are separate from WordPress plugin files. Website operators should describe the actual deployment and external providers in their own privacy notice.
Source Code
All PHP, JavaScript and CSS source used by the plugin is included in this package. No build step, remote executable code or third-party JavaScript framework is required. Bundled browser scripts are in assets/.
Optional TNS CMS homepage
Compatible themes may request homepage groups and offers through this plugin.
No CMS request is made merely by activating the plugin. In TNS Explorer, explicitly
enabling the TNS homepage permits requests to your configured TNS API and loading
of TNS-hosted images. Turn that option off to stop homepage CMS requests.
CMS responses are cached for five minutes; stale responses may be used for one day
on connection failure. Refresh TNS content invalidates only this homepage cache.
The existing endpoint, PublicKey and SecretKey settings authenticate CMS requests
using the same UTC timestamp and SHA-512 contract. Credentials stay server-side.
API service/privacy/account terms are described in External services above.
Identifier rename in 1.1.17
The plugin slug, display name, API field names, DOM classes and translation domain
remain unchanged. Plugin-owned PHP classes/functions, settings names, shortcode
names, cache keys, AJAX action/nonce names, REST namespace, URL query parameters,
script/style handles and JavaScript globals now use travelnetsoft/TravelNetSoft.
This is a name-only release. No migration or compatibility aliases were added.
Existing installations must save their connection settings under the new names
and replace old shortcodes in their pages. For example, [tns_booking] becomes
[travelnetsoft_booking] and [tns_search] becomes [travelnetsoft_search].
Old saved return-page references and cart keys are not read under their old names.
Code outside the plugin calling the old names must use the new names.
Installation
- Upload the TNS Booking ZIP through Plugins > Add New Plugin > Upload Plugin, or place the tns-booking folder in wp-content/plugins.
- Activate TNS Booking. The plugin creates its standard Payment Success and Payment Error pages. Existing plugin-created return pages are reused.
- Open Settings > TNS Booking.
- Enter the API base URL (EndPointHomeUrl), PublicKey and SecretKey provided for your TNS instance. Use HTTPS for a public production site.
- Choose whether to include partner services, according to the content available to your TNS account, then save.
- Create a WordPress page and insert a Shortcode block containing [travelnetsoft_booking]. Publish the page.
- Optionally add [travelnetsoft_search results_url=”/booking/”] to a different page, replacing /booking/ with the URL of your published booking page.
- Check catalogue, search, dated options, cart and the payment flow using your own service configuration before opening the site to customers.
When upgrading from an earlier version, upload this ZIP and choose Replace current with uploaded. Existing connection settings are retained. If no return pages existed, visit the WordPress administration once after updating to run their automatic setup.
Shortcodes
[travelnetsoft_booking]
Complete portal, starting with destinations.
[travelnetsoft_destinations]
Portal starting with destination cards.
[travelnetsoft_services]
Portal starting with service-group cards.
[travelnetsoft_search]
Standalone search widget. It discovers a published page containing [travelnetsoft_booking] for results, or accepts an explicit results_url attribute.
[travelnetsoft_search results_url=”/booking/”]
Standalone search with an explicit results destination. This widget does not replace the containing page’s H1/title/description.
[travelnetsoft_cart]
Cart entry view and cart dialog.
[travelnetsoft_checkout]
Checkout view and booking summary.
[travelnetsoft_payment_success]
Informational success-return content. Added automatically to the generated Payment Success page.
[travelnetsoft_payment_error]
Informational error/interrupted-return content. Added automatically to the generated Payment Error page.
Use one full portal shortcode per page. Subsequent views use query parameters on that page. Standalone search widgets can be placed in posts, pages and shortcode-enabled widget areas.
FAQ
-
Do I need a TravelNetSoft account?
-
Yes. The required service agreements must be signed before your TNS account is issued. You then obtain the API endpoint and credentials from your TNS service operator. Installing or activating the WordPress plugin alone does not issue an account or provide an independent offline catalogue.
-
Where are the TNS terms of service?
-
The TNS service terms are defined in the separate agreements signed during account onboarding. A public terms page is not a substitute for those signed agreements. The plugin code itself is licensed under GPLv2 or later.
-
Is there a paid PRO plugin?
-
No. This is one full plugin version. Access to the external TNS service and any related fees are governed separately by your agreement with the service operator.
-
Do I need WooCommerce or TNS Explorer?
-
No. TNS Booking runs independently. TNS Explorer is an optional theme with additional TNS CMS homepage integration.
-
Where are destinations, prices and availability managed?
-
In TNS. WordPress displays the content returned by the configured service. The plugin revalidates cart prices through that service before requesting a payment link.
-
How does date formatting work?
-
The search interface displays dd.MM.yyyy. The submitted date remains yyyy-MM-dd. Changing the display format does not change the API date contract.
-
How do I connect a standalone search widget to my booking page?
-
Use [travelnetsoft_search results_url=”/booking/”] with the actual URL of a published page containing [travelnetsoft_booking]. Without results_url, the plugin attempts to find a suitable page automatically.
-
Why do I not see SuccessBackUrl and ErrorBackUrl settings?
-
The plugin generates the two return pages and supplies their per-site URLs to TNS automatically. Previously saved manual URLs are no longer used.
-
Does opening Payment Success confirm a payment?
-
No. Both return pages are informational browser destinations. They do not validate a transaction, mark a booking paid, call a payment notification endpoint or alter the shopping cart. Final confirmation is processed by the backend/payment server.
-
Does the Error page automatically retry payment?
-
No. Return to booking is a navigation link, not an instruction to charge a customer. Check the actual booking/payment status with your service before retrying.
-
What happens to settings and return pages when the plugin is deactivated?
-
They are retained. They are not automatically deleted when removing the plugin files. The generated pages need the plugin active to render their shortcode content.
-
Is all interface text translated?
-
The current frontend primarily uses English. Some PHP strings support WordPress translations, but complete interface localization has not yet been implemented. Changing the WordPress language does not translate TNS service content.
-
Does it work with other SEO plugins?
-
TNS Booking supplies metadata for its full portal pages. It does not remove another plugin’s metadata. Review the rendered page head if another tool also manages titles or descriptions.
-
How can I get help?
-
For TNS account, API endpoint, credentials and backend questions, contact the service provider at https://travelnetsoft.com/. Do not post SecretKeys or customer/payment details in a public support request.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“TNS Booking” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “TNS Booking” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.17
- Rename plugin-owned identifiers and their references to the travelnetsoft prefix. No booking, pricing, payment or presentation logic changes.
1.1.16
- Adds an optional server-side TNS CMS provider for compatible themes. Existing booking and payment flows are unchanged.
1.1.15
- Removed the optional Plugin URI header; Author URI remains the provider website. No functional changes.
1.1.14
- Used UTC timestamps for API signatures and escaped HTTP status errors.
- Read public SEO parameters through registered WordPress query vars.
- Recovered return pages without post-meta queries.
- Verified activation, pages, query vars and shortcodes on a clean WordPress 7.1.4 installation.
1.1.13
- Reworked readme with public installation instructions, shortcode examples and FAQ.
- Documented the external TNS service, privacy-policy link, transmitted data and browser storage.
- Added GPL license text and plugin/provider metadata. No functional changes.
1.1.12
- Added automatic Payment Success and Payment Error pages and their API return URLs.
- Return pages remain informational; payment confirmation stays with the backend.
1.1.11
- Made image alt/title and detail-link titles specific to each destination, group or offer.
- Added booking, itinerary, availability and price wording to page titles.
1.1.10
- Moved H1 headings inside the portal and removed duplicate offer headings.
1.1.9
- Added H1/H2 structure, page titles, descriptions and image/link SEO attributes.
1.1.8
- Removed manual payment-return URL fields from the settings screen.
1.1.7
- Corrected dropdown checklist styling in the full portal.
1.1.6
- Unified full-portal and standalone search dropdowns, layout and date display.
1.1.5
- Hid the standalone search heading and introductory text.