Table of Contents |
---|
Release notes
From version 1.4.0 the plugin is compatible with the Shopware Plugin Store. Unfortunately, the necessary changes are not backwards compatible, so that BEFORE installing version 1.4.0 or higher, all older versions up to 1.3.9 must be uninstalled manually.
From version 1.4.13, the "Update transaction types" function in the UI should be used so that the manufacturer number can also be transferred.
...
The module is used in the XQueue example instance http://dev-shop1000.maileon.com/shopware/ (Illustration Figure 1).
...
Commissioning name of the module
...
The advantage of this approach is clear: easy installation and very simple information and update options (Illustration Figure 2).
...
Via "Settings" "Plugin Manager" "Installed" "Upload Plugin" can be added to Shopware (
...
Figure 3 and
...
Figure 4).
...
Illustration Figure 4 shows the Plugin Manager after the module has been successfully added. The module can already be configured via the red marked "Edit" button or first installed and activated via the green + symbol. Illustration Figure 5 shows the module after successful activation.
...
The module now only needs to be configured by clicking on the "Edit" button.
...
Illustration Figure 6 shows the configuration page on which the API key and a permission must first be entered. The API key can be created and viewed in the Maileon account under "Settings" "API Keys". Since version 1.1.0, the plugin is sub/language shop-capable. In the settings, there is then a configuration for each subshop, as can be seen in Illustration Figure 6.
Transfer newsletter subscribers to Maileon:
...
If required, the menu item "Marketing" - "Maileon Manager" (Illustration Figure 7) can also be used to view current newsletter subscribers and synchronise all subscribers (also from before the module was installed) with Maileon. Furthermore, the manager shows the settings for the webhooks that have to be set up in Maileon and allows the transaction types to be created manually in Maileon. Otherwise, these would only be generated the first time they are used. However, if you want to have all or individual mailings generated before testing, such as an order confirmation mail, then it is advisable to create the transaction type in advance in order to gain access to its variables in the template.
...
Clicking the "Send all" button (Illustration Figure 8) starts the process. Depending on the number of contacts, the process can take several minutes. Afterwards, the UI notifies about success or errors that have occurred.
...
The configuration parameters for the Maileon webhooks are displayed here, see Illustration Figure 10 and Illustration Figure 11.
Create and update transaction types
...
Furthermore, custom fields can be inserted into the form and transmitted to Maileon. However, this requires an entry in the configuration (last point, Illustration Figure 6).
Finally, a forwarding in case of success can be set up by inserting a hidden form field with the name "redirect":
...
A new webhook must now be added for the "DOI login confirmation" event. For this, the URL and the webhook ID from the "Maileon Manager" (Illustration Figure 10) must be used.
The webhook expects four parameters:
...
Version 1.4.0, 21.09.2021
Updated code to be compatible with Shopware plugin store. Installing 1.4.0 requires complete uninstallation of previous versions
Version 1.3.9, 17.09.2021
Changed to composer version of Maileon PHP API client
Bugfix: Handle if article model not found at order transactions
Bugfix: DOI confirm webhook processes data now correctly, if captcha is enabled
...
Version 1.3.0, 08.02.2021
Change permission logic (added explicit initial permission and DOI, DOI+ process)
Add extended order transaction types (v1.0)
BE AWARE: This update creates new transaction types. Mails bound to the old type WILL NOT be sent anymore. Make sure to first create the types, e.g. from a staging system, create the mails and then install this update on your live system.Add functionality to create all transaction types at Maileon by clicking one button in the Shopware settings
...