WordPress Download Manager Pro v4.6.2 released

WordPress Download Manager Pro v4.6.2 has been released. This update comes with improvement with author dashboard feature ( front-end file upload ). Now all users files will be stored in a separate dir inside main upload dir. And using file manager add-on users will able to mange their files too from front end ( demo ). Also the author dashboard UI is redesigned for better user experience. Also another new feature is available in this release, you can now force user to agree with terms and conditions before download your file. There are also some other improvements , all are listed below.

What is new with WordPress Download Manager Pro v4.6.2:

  • Terms and Conditions Lock, force user to agree with terms and conditions before download your file
  • Improved author dashboard, UI redesign
  • Added custom upload dir  support and server file browser access for front-end uploaders
  • Added Data API support for front-end uploaders.
  • Improved social lock options and UI

Get WordPress Download Manager Pro  v4.6.2 from your premium download area.

Comments [ 3 ]

  • connect

    Sadly, this 4.6.2 release (like 4.6.0 and 4.6.1) is still broken on PHP 5.3.3 (which *is* supported by WP core). Hence Download Manager Pro – a paid plugin – is unusable on CentOS 6 (which is supported until 2020). What’s worse is that there’s no way to download older versions either (4.5.6 worked fine on PHP 5.3.3/CentOS 6 for example).

    • Shaon

      Plugins add features, those WP core doesn’t provide already, so sometimes for some plugins, it is not possible to keep same php version compatibility like WP core. You may see another good example: https://docs.woocommerce.com/document/server-requirements/ , also you may check this:
      PHP Versions
      Summery is, actually, we are trying to make WordPress Download Manager better and secure 🙂

      • connect

        That release history table is only for “stock” PHP downloaded from php.net. The PHP 5.3.3 shipped with CentOS 6 includes backported security and bug fixes from later PHP 5.X releases. This is exactly why WordPress core doesn’t say that PHP 5.6+ is required – it’s “recommended” because it’s the oldest PHP that php.net support – but we know that PHP 5.3.3 works fine with the WP core code.

        What inevitably happens though, is that plugin coders get itchy to use PHP language features that are introduced in later releases (CentOS 6 doesn’t backport these), even if it means breaking compatibility with long term Enterprise Linux distros. The fact that older plugin releases (<1 year ago, not from August 2014) worked fine with PHP 5.3.3 shows that it's not the security excuse, but just coding temptation that's the problem.

Leave a Reply