Yes, finally solved!
It only came at a rather bad moment: There was just a large potential customer. He registered on the website, but then it turned out that he chose a user name with a space – and with that it happened that he was not even able to come to the files he was supposed to download. Once I had found out that the space is an issue, he generated a new account, he could see the download file…
…and exactly NOW he had that cryptic “invalid file type…”.
Now also this is solved. And I hope that the potential customer was not that much frustrated from this website experience…
So far I am optimistic, but I just wanted to tell this story with the message that website features are often the location where we make a first impression – and it would be better if that is a good impression!
Regards, Cornelis
Just finding out that the problem has a solution already: see here https://www.wpdownloadmanager.com/support/topic/invalid-file-type-after-update-to-5-3-7/
I can confirm that this same thing is happening on my website! And it looks like not only pdf, but also exe and txt files are now “invalid file types”.
Thanks a lot for your support – I really appreciate it!
I will have a look into your added code and try to understand. I must admit that many workings in such a WP based website are not really clear for me, but step by step I am learning.
With best regards,
Cornelis
If this can be done as an option somewhere: please tell me and I would be happy to do it!
My primary goal is to ensure that protected downloads are never exposed to non-authorized people, even accidentally, and the “Prev” and “Next” buttons seem to be a “gap” in the protection. On top of that, they are not really required for anything at least in my case.
Great – found it – and thanks again!
Actually I had seen this setting before, but I obviously misinterpreted the following explanation:
“Check this option if you want to mask/unmask file download link. If you unmask download link, bots will be able the find any public download link easily.”
I saw that the option was set to “Mask”, and from that explanation I concluded that this is kind of a protection against bots. I did not realize that it is also a protection against users!
Anyway, the download page itself is not public anyway, but only for registered users, so your proposed setting is definitely correct.
Kind regards, Cornelis
Thanks for the hint, but I must admit that I am not able to follow it! Because basically this is what I was looking for without any success before I posted my question here.
“Basic settings”: Do you mean the “Settings” that you find directly in the main menu? Anyway, I cannot find any download related point in any of the submenus
“Settings” submenu in the “Downloads” main menu? Same thing
Any other location?
I would be happy if you could specify slightly more!
Best regards,
Cornelis
Looks great – download is back again!
Anything that I did wrong with some settings, or was it rather a bug somewhere in the plugin?
Thanks a lot Nayeem!
Cornelis
Many thanks for your support – I appreciate it very much! It looks indeed like the problem is solved now.
From this I conclude that the license is linked to the domain, so probably I even do not need to do anything at all!?
Because what I intend to do:
1. migrate the website to another hoster
2. migrate also the domain to that new hoster
The result should be that users will finally reach the website with exactly the same URL – like nothing hat happened.
At least that’s what I would like to see!!
Anyway: If there are still problems with the license I will rely on your very helpful support.
Wow, thanks!
Indeed I will most of the time have packages with one file only, so this is an obvious choice for the option.
Still there is the other point: In the Download Manager settings I am asked to enter my wpdownloadmanager.com settings for automatic updates:
“Enter your WPDownloadManager.com login info”
But if I enter there my login name and password that I am also using on this website – to get my downloads and visit this forum -, I am still only told:
“Error: Invalid login!”
I am sure that also here I am doing something wrong – “it’s a feature, not a bug” -, but I am not able so solve this riddle.
Any helpful hint also for this problem?
Thanks and regards,
Cornelis