Search Results for 'all downloads'

According to the documentation on Media Protection there are options for Advanced protection that ensure signed, single-use URLs etc.

However, in the admin UI of my site, when I go to Downloads ► Settings ► Media Protection, the only panels I can see are Server Information, Protection Method and Private Storage Status. Nowhere mentions the Advanced mode referenced in the documentation. I’m also not sure why Private Storage Status is appearing when I am using the PHP Proxy protection method.

Additionally, the docs talk about a Protect Media button appearing in the regular WordPress media library, but I do not see this button. I’m not sure if I’m looking in the right place, though, because the package I have created does not involve a file stored in the media library (I uploaded it to the WPDM Package directly and so it is stored in the download-manager-files folder).

Hello,
the layout of the individual file-download page looks completely crazy. All kinds of unwanted stuff is being displayed really large: categories, tags, similar downloads (which are not similar at all except being PDFs as well!). See for yourself https://ibb.co/QFNvMX6V and https://ibb.co/q3FgZPtz. Even files of different languages are mixed together. AAAWFUL! Shortcodes are being corrupted which makes downloads fail. What is wrong with the plugin???

Hi community,

please see my empty download table:
https://compenser.de/en/downloads-industrial-shock-absorbers/

With recent Update from V3 to V7, this download list is empty.
Theme: DIVI Version: 4.24; DiviAiO Version 6.9.4

Catgories and Slug remain unchanged, ONLY difference, Version of WPDM.

Categories linked to pages:
category/slug: down, site:
https://compenser.de/en/downloads-industrial-shock-absorbers/download-certificates/

category/slug: date, site:
https://compenser.de/en/downloads-industrial-shock-absorbers/download-data-sheets/

category/slug: manu, site:
https://compenser.de/en/downloads-industrial-shock-absorbers/download-assembly-instruction-and-operating-manual/

category/slug: docs, site:
https://compenser.de/en/downloads-industrial-shock-absorbers/download-documents/

category/slug: manu, site:
https://compenser.de/en/downloads-industrial-shock-absorbers/download-assembly-instruction-and-operating-manual/

Shortcode example in use: [wpdm_all_packages items_per_page="50" categories="date" jstable="1" order_by="field_name" order="ASC/DESC" cols="title,file_count|update_date|download_link" colheads="Title|Update Date|Download"]

Addons: WPDM – Advanced Custom Fields

What can be the issue here? Thanks.

Hello,

How does the stats of downloads actually work? I’m seeing weird numbers like 226 downloads per user.

I have 2 issues and both are for this page which is using the Archive plugin.

Resources

Some of the packages are showing up multiple times with different numbers of downloads showing but there is only one copy of the package in the backend. Example in this case is the BPR Etude Hydraulique du ruisseau Bouchard 2010 package. The one with 164 downloads is what is in the backend and clicking on View for any of the 3 copies takes you to the details page for version saying 164 downloads so it goes to the correct file. It does this for a few of the packages, not all of them.

I use WPML and when I switch the French version of the details page for this, it shows me a version the file that has 111 downloads.

Also, when I click on the view details button (Afficher) on the French side, it takes me back to the English page.

Hi – we have been using links on a menu to display categories, but since the update to 7.0 (and after), these links are no longer working.

An example of the link is: https://wptest.wprnd.net/downloads-index/?wpdmc=awards

This link used to list just the downloads in the “awards” category – but not it just redirects to a page with all downloads listed.

Can you tell me how to alter these links so they continue to work w/ the upgrade? Or what we need to change them to?

Tks

Hello,

I would like to report what appears to be a bug in WP Download Manager Free 3.3.51.

We are seeing a very large number of PHP warnings like this:

preg_match(): Delimiter must not be alphanumeric or backslash

The warning points to:

/content/plugins/download-manager/src/__/__.php

After debugging, the warning appears to originate from:

WPDM\__\__::sanitize_var($value, $sanitize = '')

In the default branch, the method does this:

if($sanitize !== ” && $value !== ” && @preg_match($sanitize, ”) !== false) {
$value = preg_replace($sanitize, ”, $value);
}

In our case, $sanitize is repeatedly the string:

"array"

Since “array” is not handled by any explicit case in sanitize_var(), it falls into the default branch, and the code effectively does:

@preg_match('array', '')

which triggers:

preg_match(): Delimiter must not be alphanumeric or backslash

We added temporary debugging and a backtrace. The relevant call chain looks like this:

– do_shortcode()
– WPDM\Package\Shortcodes::singlePackage()
– WPDM\Package\Package / PackageController::fetchTemplate()
– PackageController::metaData()
– wpdm_sanitize_var()
– WPDM\__\__::sanitize_var()
– WPDM\__\__::sanitize_array()
– WPDM\__\__::sanitize_var() again, this time with $sanitize = ‘array’

This happens while rendering pages with WPDM shortcodes. In our test, a single page with 6 download packages already triggered many repeated occurrences.

We are seeing the same issue in two separate projects. We use a monitoring system that still captures these warnings despite the “@” operator, so the logs for both projects are being flooded. Because even a page with only 6 downloads already produces many repeated warnings, this becomes a real operational problem in monitoring and log volume.

So it looks like “array” is being used as a sanitize/validate value somewhere in the package metadata/template flow, but sanitize_var() has no case for “array”, and the default logic incorrectly treats unknown sanitize values as regex patterns.

This does not look like an isolated site-specific regex issue, but like a plugin-side fallback bug for unknown sanitize values.

Suggested fix:
– add an explicit case ‘array’, or
– do not treat unknown $sanitize values as regex patterns in the default branch

For example, the default branch could simply skip preg_match()/preg_replace() for unknown sanitize values.

Could you please confirm whether this is a known issue?

Best regards