Product Downloads and Product Links
Technical Information
Highlights
-
Product downloads as a link or with image, including title & description
-
Flexible placement: separate tab or no tab
Features
-
Import also possible via API interface
Product Downloads
- Downloads of files at the article
- offer explanations, software and manuals
- Formats like JPG, GIF, PNG and PDF possible
- In Shopware Standard, the following file types are possible for file upload in Media Manager:
jpg, jpeg, png, webp, gif, svg, bmp, tiff, tif, eps, webm, mkv, flv, ogv, ogg, mov, mp4, avi, wmv, pdf, aac, mp3, wav, flac, oga, wma, txt, doc.
If you want to upload special documents with other extensions, then this will be blocked by Shopware
A simple adjustment of the Shopware configuration file makes this possible:
Starting from the Shopware root > config > packages > shopware.yaml
(edit if present, create if not present - this is a simple text file and can be edited with a Notepad++ or similar)
Please copy this entry in or adjust entry accordingly:
shopware:
filesystem:
allowed_extensions: ["jpg", "jpeg", "png", "webp", "gif", "svg", "bmp", "tiff", "tif", "eps", "webm", "mkv", "flv", "ogv", "ogg", "mov", "mp4", "avi", "wmv", "pdf", "aac", "mp3", "wav", "flac", "oga", "wma", "txt", "doc"] - We have created a plugin to extend the file extensions without manual adjustment of shopware.yaml - you can request this from us for free via support.
Product links (from plugin version 3.x)
From plugin version 3.x we have created the possibility to manage links.
Here links can be displayed in different positions (e.g. show link in own tab, link tab before or after ratings, show link in no tab,...).
Links can be provided with a title and a description, it can also be set whether the link should open in a new tab.
Basic setting
Via Settings > System > Plugins > AcrisProductDownloads
Set the position of the download products
Enter media path for import
Configuration
A module for download articles is offered in the product with downloads
As with media, files can be stored there.
Images and files can also be uploaded directly via a URL
Title, description and position of the files can be changed later
The download files can be displayed in different position
- In a separate tab
- Before the description
- Between the description and the technical data
- According to the technical data
Import via Shopware API - API Documentation
1. Uploading the downloads via FTP
First, an FTP path must be entered in the plug-in settings. The download files from the ERP system must be uploaded to this directory.
Example path: file:///var/www/clients/clientX/webX/private/media/documents/
2. Importing the downloads via Sync-API
The JSON call for the sync API:
POST http://www.my-shop.com/api/_action/sync
[
{
"action": "upsert",
"entity": "product",
"payload": [
{
"id": "b851fd3085054856b83e1e693b5bbd1b",
...
"acrisDownloads": [
{
"fileName": "ACRIS_12345_1_DE.pdf",
"title": "Benutzerhandbuch",
"position": 0,
"languages": [
{
"id": "2fbb5fe2e29a4d70aa5854ce7ce3e20b"
}
]
},
{
"fileName": "ACRIS_12345_1_EN.pdf",
"title": "Manual",
"position": 0,
"languages": [
{
"id": "01896943f9847021b988cede9f40d445"
}
]
}
]
}
]
}
]
Field description
- id: Mandatory field. The ID corresponds to the UUID of the product.
- fileName: Mandatory field. Please enter only the file name including file extension. The file must be located on the server in the directory specified in the plug-in settings.
- title: Optional. The title can also be translated analogous to the other translations as they are usual in Shopware 6.
- position: Optional. Defines the display position in the shop.
- languages: Optional. Downloads can be restricted to languages. If languages is omitted or passed empty, the download file is available for all languages.
Replace downloads when re-importing
So that downloads are not assigned more than once when they are imported again, an id (UUID) can also be entered in the "id" field before the "fileName" field.
3. Result
If the download file exists on the server and was found, Shopware imports the file into the media management of Shopware 6 into the folder "Product Media".
If the download file already exists in the media management, it will be replaced.
User guide
- Plugin Manager via Settings > System > Call up Plugins
- Upload, install and activate the plugin
- After activation, the files section appears in the article administration under Downloads
Frequently Asked Questions
Example for JSON-call via Sync-API: POST http://www.mein-shop.de/api/_action/sync
[
{
"action": "upsert",
"entity": "product",
"payload": [
{
"id": "b851fd3085054856b83e1e693b5bbd1b",
...
"acrisDownloads": [
{
"fileName": "ACRIS_12345_1_DE.pdf",
"title": "Benutzerhandbuch",
"position": 0,
"languages": [
{
"id": "2fbb5fe2e29a4d70aa5854ce7ce3e20b"
}
]
},
{
"fileName": "ACRIS_12345_1_EN.pdf",
"title": "Manual",
"position": 0,
"languages": [
{
"id": "01896943f9847021b988cede9f40d445"
}
]
}
]
}
]
}
]
Example for the API pattern of how should be links imported to the product via Sync-API.
[
{
"action": "upsert",
"entity": "product",
"payload": [
{
"id": "b851fd3085054856b83e1e693b5bbd1b",
"acrisLinks": [
{
"url": "https://www.acris-ecommerce.at/",
"linkTarget": true,
"title": "Title for Link",
"description": "Description for Link",
"position": 1,
"languages": [
{
"id": "2fbb5fe2e29a4d70aa5854ce7ce3e20b"
}
]
}
]
}
]
}
]
If the downloads have already been uploaded to the media in the Shopware Admin, then I can assign the downloads via API as follows:
{
"id": "f947b036a41c4be38cdad7fddf13bd1d",
"acrisDownloads": [
{
"mediaId": "11d0ac3beb2e4f738f72732739e108b0",
"title": "Test file",
"position": 0,
"languages": [
{
"id": "2fbb5fe2e29a4d70aa5854ce7ce3e20b"
},
{
"id": "7a6b724e70614488bc10740313df0409"
}
]
}
]
}
Example of a JSON call for the Sync API (UUID of the product, language and download entry must be known): POST http://www.my-shop.com/api/_action/sync
[
{
"key": "write",
"action": "upsert",
"entity": "product",
"payload": [
{
"id": "0189f245a8047d0e928c3d3a702eeedc",
"acrisDownloads": [
{
"id": "0189f2466f197d7b808601c970f8d034",
"title": "Download Title EN (default language)",
"description": "Download Description EN (default language)",
"translations": [
{
"languageId": "2fbb5fe2e29a4d70aa5854ce7ce3e20b",
"title": "Download Title EN (default language)",
"description": "Download Description EN (default language)"
},
{
"languageId": "0189d01b707a7298885830df99fcd93f",
"title": "Download Titel DE",
"description": "Download Description DE"
}
]
}
]
}
]
}
]
Example of a JSON call for the Sync API (UUID of the download entry must be known): POST http://www.my-shop.com/api/_action/sync
[
{
"action": "delete",
"payload": [
{
"id": "0189f2466f197d7b808601c970f8d034"
}
],
"entity": "acris_product_download"
}
]
Attention: The medium itself is not deleted with this call. It must be deleted via an additional call with the known UUID of the medium:
DELETE http://www.mein-shop.de/api/media/0189f2466ded7927a13d3904b7d1a0a2
Yes, a download can be assigned to a download group. This download group in turn can only be made accessible to certain customer groups via a stored rule. Other rules and conditions are also possible here.
The API documentation is available at: https://api-docs.acris.at/#ab6cf374-b77f-4cad-8e67-00f7c6f20636
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 6.3.2 | 2 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.1 | 26 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.2.0 | 17 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.0 | 11 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.0.10 | 17 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.0.9 | 12 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.0.8 | 20 August 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.0.7 | 4 August 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.6 | 1 August 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.5 | 30 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.4 | 11 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.3 | 8 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.2 | 3 July 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.1 | 26 June 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 6.0.0 | 13 May 2025 | >=6.7.0.0 < 6.8.0.0 |
|
| 5.1.1 | 27 April 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 5.1.0 | 11 December 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.23 | 20 August 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.22 | 7 July 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.21 | 26 June 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.20 | 28 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.19 | 23 April 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.18 | 26 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.17 | 25 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.16 | 24 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.15 | 13 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.14 | 11 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.13 | 19 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.12 | 14 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.11 | 10 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.10 | 6 February 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.9 | 21 January 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.7 | 25 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.6 | 8 October 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.5 | 12 August 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.4 | 24 June 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.3 | 11 June 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.2 | 21 May 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.1 | 3 May 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.0.0 | 22 March 2024 | >=6.6.0.0 < 6.7.0.0 |
|
| 4.3.6 | 30 June 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.5 | 28 April 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.4 | 23 April 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.3 | 22 April 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.2 | 10 February 2025 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.1 | 28 November 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 4.3.0 | 24 October 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 4.2.8 | 21 May 2024 | >=6.5.0.0 <6.6.0.0 |
|
| 4.2.7 | 11 March 2024 | >=6.5.0.0 |
|
| 4.2.6 | 19 February 2024 | >=6.5.0.0 |
|
| 4.2.5 | 13 February 2024 | >=6.5.0.0 |
|
| 4.2.4 | 17 January 2024 | >=6.5.0.0 |
|
| 4.2.3 | 19 December 2023 | >=6.5.0.0 |
|
| 4.2.2 | 21 August 2023 | >=6.5.0.0 |
|
| 4.2.1 | 8 August 2023 | >=6.5.0.0 |
|
| 4.1.3 | 13 July 2023 | >=6.5.0.0 |
|
| 4.1.2 | 16 June 2023 | >=6.5.0.0 |
|
| 4.1.1 | 16 May 2023 | >=6.5.0.0 |
|
| 4.1.0 | 2 May 2023 | >=6.5.0.0 |
|
| 4.0.0 | 13 March 2023 | >=6.5.0.0 |
|
| 3.6.3 | 11 March 2024 | >=6.4.0.0 |
|
| 3.6.2 | 16 May 2023 | >=6.4.0.0 |
|
| 3.6.1 | 2 May 2023 | >=6.4.0.0 |
|
| 3.6.0 | 15 March 2023 | >=6.4.0.0 |
|
| 3.5.1 | 15 February 2023 | >=6.4.0.0 |
|
| 3.5.0 | 26 November 2022 | >=6.4.0.0 |
|
| 3.4.0 | 26 November 2022 | >=6.4.0.0 |
|
| 3.3.0 | 26 November 2022 | >=6.4.0.0 |
|
| 3.2.0 | 26 November 2022 | >=6.4.0.0 |
|
| 3.1.1 | 26 November 2022 | >=6.4.0.0 |
|
| 3.1.0 | 26 November 2022 | >=6.4.0.0 |
|
| 3.0.4 | 26 November 2022 | >=6.4.0.0 |
|
| 3.0.3 | 26 November 2022 | >=6.4.0.0 |
|
| 3.0.2 | 26 November 2022 | >=6.4.0.0 |
|
| 3.0.1 | 26 November 2022 | >=6.4.0.0 |
|
| 3.0.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.4.3 | 26 November 2022 | >=6.4.0.0 |
|
| 2.4.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.4.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.4.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.3.3 | 26 November 2022 | >=6.4.0.0 |
|
| 2.3.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.3.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.3.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.3 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.5 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.4 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.3 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.0.0 | 26 November 2022 | >=6.4.0.0 |
|
Login
Super freundlicher Support und schnelle Umsetzung von Anpassungen. Wirklich top!
-
Vorbildlicher Support
Sowohl bei aufgetretenen Bugs als auch bei Feature Requests hat Acris wiederholt zügig, freundlich und professionell reagiert und zeitnah ein funktionierendes Update geliefert.
Support wird hier noch großgeschrieben
Danke für die Schnelle Hilfe, da können sich andere Firmen mal ne Scheibe von Abscheiden :-)
Top!!!
Diese Erweiterung ist Spitzenklasse für PDF-Downloads.
Super einfach und genial zu bedienen.
Optimal zur Ergänzung von Downloads zu einem Produkt
Für uns war wichtig, dass die Dokumenet auch via API gepflegt werden können. Das klappt mit dieser Erweiterung sehr gut.
Feedback und Wünsche nimmt Acris immer gerne an und setzt diese oft und schnell um. So macht eine Zusammenarbeit wirklich Spaß!