WordPress plugin reference

TradeSender Enquiries is a small WordPress plugin. It prints the embed from a shortcode and can forward Contact Form 7 submissions to the enquiry form's address. It maps no fields itself: the server reads the names.

For the steps a website owner follows, see The WordPress plugin.

At a glance

Where it is

The zip is linked from Settings, then Website and portal, in TradeSender, and is served at:

https://app.tradesender.co.uk/downloads/tradesender-enquiries.zip

The zip is the source. It holds one folder, tradesender-enquiries, with four files and no build step:

The plugin is not in WordPress's plugin directory, so WordPress offers no updates for it. A newer zip is uploaded over the old one.

The shortcode

[tradesender_enquiry]
[tradesender_enquiry accent="#2f6b3a"]

What it prints

With a form key saved, the shortcode returns the embed's placeholder:

<div data-tradesender-enquiry="YOUR_FORM_KEY" data-accent="#2f6b3a"></div>

It also enqueues https://app.tradesender.co.uk/enquiry.js under the handle tradesender-enquiries, in the footer, with the async strategy and no version in the address. The script is added only to pages where the shortcode runs.

From there the form is the embed, with the same behaviour, event and styling.

With no form key saved, the shortcode returns an empty string. A user who can manage_options sees this in its place: "Add your TradeSender form key under Settings, TradeSender enquiries, and the enquiry form will appear here."

The settings page

The page is Settings, then TradeSender enquiries, at options-general.php?page=tradesender-enquiries. It needs the manage_options capability. The plugin also adds a Settings link to its row on the Plugins page.

Options it stores

The plugin creates no tables, post types, scheduled events or REST routes.

How the key is read

The Form key field takes the key, the form link or the form address. The plugin keeps the first run of exactly 24 letters and digits it finds. If there is none, it keeps the key it had and reports "That does not look like a TradeSender form key. Copy it from TradeSender: Settings, Website and portal." Saving the field empty clears the key.

Contact Form 7 forwarding

Forwarding runs on Contact Form 7's wpcf7_before_send_mail action, when all three hold: the option is ticked, a form key is saved and Contact Form 7 is active. It covers every Contact Form 7 form on the website.

The website's server sends one multipart/form-data post to the form address, with Accept: application/json and a timeout of 15 seconds:

• Field names go as they are. your-name, your-email, tel-123 and the rest are matched by the server, and any other field is kept in the enquiry's message. See the enquiry form's address.
• Contact Form 7 sends its own email whatever TradeSender answers.
• The forward happens while the visitor waits for the form to finish.
• Every forward comes from the server's IP address, so the limit of 10 posts in 15 minutes covers the whole website, and other websites on the same shared address.

When a forward fails

The plugin saves the reason and the time in tradesender_enquiries_last_error, and the settings page shows it as a warning until a forward works.

Point it at another server

Define TRADESENDER_ENQUIRIES_APP_URL in wp-config.php to load the script from, and post to, a server other than https://app.tradesender.co.uk. It is there for testing.

define( 'TRADESENDER_ENQUIRIES_APP_URL', 'http://127.0.0.1:3000' );

What leaves the website

Nothing is sent until one of these happens.

Deactivating and deleting

Deactivating the plugin keeps its options.

Deleting it runs uninstall.php, which deletes all three options: tradesender_enquiries_key, tradesender_enquiries_forward_cf7 and tradesender_enquiries_last_error. Enquiries already in TradeSender are not touched, and shortcodes left in pages are not removed.