Forum Replies Created
Thank you again for fixing the problem!
Could you please give me some more details about it, since I have to fully report to my client:
Why exactly did the problem occur over night without a plugin update and why were only zip files affected?
Why did the error message change from ‚invalid‘ to ‚not attached‘ over night?
Will the problem occur again after the next plugin update, or will there be a permanent fix in the next update?
What can be done from our side to prevent this problem from occurring again?
Thank you very much for taking the time to answer our questions.
Best regards
Sebastian
Hi!
The download of zip files is working again!
No more error messages.
Thank you very much for your help!
Could you please tell us what was causing the problem.
Hello,
since yesterday we are having the same issue [ Invalid File Type (*.|=|)! ] when trying to download zip files, but we can not solve it with the here mentioned work around.
Allowed file types to upload are currently set to ‘jar,exe,zip,pdf’ which always worked perfectly.
Since yesterday the download of zip files doesn’t work anymore and triggers the mentioned error message.
Downloads of jar files are working as expected.
We already tried:
* setting allowed file types to ‘*’ or to ‘All’ > no success, same error
* deleting the zip file from server, re-uploading it and re-attaching it from server > no success, same error
* renaming the file to have no special characters > no success, same error
* adding another zip file to the package > no success, same error
* deactivating the email lock function > no success, same error
* deleting the complete download package and setting it up from scratch > no success, same error
Please note that the current setup has worked flawlessly in this form for many month/years.
Download .jar files is still working as expected.
Download .zip files all of a sudden generate the above mentioned error message.
No changes were made to the setup from our side.
We are using the Pro version 6.2.9 with E-Mail-Lock activated.
We are really at a loss and please urge timely support.
Thank you
Sebastian
Never thought that this template was causing the problems.
Thank you so much for pointing me in the right direction for solving the problem on the live site!
Kind regards
Here’s the updated error report with v6.2.2 in use:
Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 183 der Datei /usr/www/users/msckso/wp-content/plugins/download-manager/download-manager.php verursacht. Fehlermeldung: Uncaught Error: Class ‘WPDM\__\Session’ not found in /usr/www/users/msckso/wp-content/plugins/download-manager/download-manager.php:183
Stack trace:
#0 /usr/www/users/msckso/wp-content/plugins/download-manager/download-manager.php(153): WPDM\WordPressDownloadManager->__construct()
#1 /usr/www/users/msckso/wp-content/plugins/download-manager/download-manager.php(577): WPDM\WordPressDownloadManager::instance()
#2 /usr/www/users/msckso/wp-settings.php(428): include_once(‘/usr/www/users/…’)
#3 /usr/www/users/msckso/wp-config.php(62): require_once(‘/usr/www/users/…’)
#4 /usr/www/users/msckso/wp-load.php(50): require_once(‘/usr/www/users/…’)
#5 /usr/www/users/msckso/wp-admin/admin-ajax.php(22): require_once(‘/usr/www/users/…’)
#6 {main}
thrown
Fixed by adding allowed file types for upload(!), removing *.
Not a good user experience after an update though.
Same here! After click on Download-Button fullscreen message ‘Invalid File Type’. Please tell us, how we can fix this! Thank you!
Hi Max!
I don’t know if there is a user-friendly method from within the backend, but you can simply overwrite the “download-manager”-folder inside your plugins-folder with an older version from one of your recent backups. All packages and settings will remain the same, since all this data is stored in the database.
So if you are familiar with ftp-access and the folder-/file-structure this method should work for you.
Always make a backup, before you start changing file via ftp.
Sebastian
Hi,
we are facing the same problem after the latest update 5.1.20!
All the Download-Buttons in the frontend hab noch function anymore, the Package-Management-Screens in the backend were messed up (no tabs, no icons, …).
We hab to revert to version 5.1.18 to get the site up and running again.
Please check the problem and maybe release a fix with version 5.1.21. Thanks!
Yes, you are right. The file isn’t there anymore.
Now please tell us: How could this happen?
What can I tell my client?
I downloaded the plugin yesterday and today from this site via my account (Download Area > Purchases > Order Details > Download). Both packages had the infected file included. After your comment above I downloaded the package again and now the file is missing.
I just checked – the malicious file (pack.zip) is NOT included in the latest version of the free plugin (v.3.0.96 – wordpress.org/plugins/download-manager/). It looks like it is only included in the pro version 5.0.9.
I ask again … how can something like this happen?
We just checked the file (/wp-content/plugins/download-manager/assets/css/themes/default/pack.zip) with Virus Total (https://www.virustotal.com/) and it hit 17 detections for a PHP.Backdoor.Webshell.
How can this happen?!
We need a statement and a security advise immediately!
What do we have to do? How can we protect our clients data?
Same here!
The latest update reset the link template for all packages!
At first it wasn’t possible to set the link templates back to our custom template, because it couldn’t be found in the dropdown.
So we checked the templates and the custom template was still listed.
We had recreate the custom template and save it under a different name.
Only after that our previous template could be found and selected.
Very frustrating situation! On top we are using the paid pro version!
Same here!
Our client just received a malware warning from his provider stating that the above mentioned file is malware infected.
The virus signature ‘Win.Trojan.Hide-1’ was detected!
What is the problem here! This is totally unacceptable! On top of that we are using the paid pro version!
Please provide a statement to this situation as soon as possible!
Thank you. That worked well for me!