Search Results for 'all+downloads'

Hi,

WordPress provides API which allows developers to interact with sites remotely. You may use the REST API v2 of WordPress and follow this to add support for custom post types. As we use custom post type, you can easily get all the downloads file in json format with the API.

Thanks

Hi,

Maybe you use custom template file in the theme folder for all downloads. Please send login to check the the issue. or removing the theme file /themes/rexus-child/download-manager/wpdm-all-downloads.php would solve the problem.

Thanks

The code tags removed all white space.

Defined constants file:

/etc/aws_secrets/site.secrets.php
<?php
define(‘AWS_CLOUDFRONT_ACCESS_KEY_ID’,’*************’);
define(‘AWS_CLOUDFRONT_KEY_PATH’ , ‘/etc/aws_secrets/cloudfront_privk.pem’);
define(‘MY_DOMAIN’ , ‘.example.com’);
define(‘AWS_CLOUDFRONT_USER_DOWNLOADS’,’***********.cloudfront.net’);
define(‘AWS_USER_ACCESS_KEY_ID’,’****************’);
define(‘AWS_USER_SECRET_ACCESS_KEY’,’********************************’);
define(‘AWS_REGION’,’us-west-2′);
?>

// Add to the end of functions.php in your WordPress theme
add_action(‘init’, ‘setMyCookies’);

function setCloudFrontCookies(){

/*
* We’re on app.example.com or http://www.example.com, files are on S3.
* We need to send requests to files.example.com, becuase browsers will not
* accept cookies for S3 or xxxxxxx.cloudfront.net sent from example.com
*
* Therefore, we will set cookies for .example.com,
* so that they’re sent to the CloudFront subdomain files.example.com.
*
*
* User request needs to go like this:
*
*
* User visits *.example.com (our site)
* After authenticating user, our site *.example.com sets cookies for
* .example.com and redirects to files.example.com
* DNS sends request to cloudfront. Cloudfront gets files from S3.
*
* Step: 1
*
* Set Route 53 (DNS) CNAME record for files.example.com that points to our
* cloudfront distribution: xxxxxxx.cloudfront.net.
* Now requests sent to files.example.com from our site will go to cloudfront.
*
* Step: 2
* In our cloudfront xxxxxxx.cloudfront.net add CNAME files.example.com
* Now xxxxxxx.cloudfront.net will respond to requests sent to files.example.com
*/

// Settings
//
// Location of all defined constants used below
require_once (‘/etc/aws_secrets/site.secrets.php’);
//
// AWS SDK User
// Create an IAM user with cloudfront all access for use by the SDK
$user_access_key_id = AWS_USER_ACCESS_KEY_ID;
$user_secret_access_key = AWS_USER_SECRET_ACCESS_KEY;

// AWS Cloudfront Access Key ID
// NOT a regular IAM user.
// In your root account look for “My Security Credentials”.
// Or, from here:
// https://console.aws.amazon.com/iam/home#/security_credential
// Look for Your Security Credentials,Cloudfront Key Pairs, Access Key ID
$key_pair_id = AWS_CLOUDFRONT_ACCESS_KEY_ID;
// The private key .pem file associated with this Access Key ID.
$private_key = AWS_CLOUDFRONT_KEY_PATH;

// Region is a subset of the availbiity zone
// If availbility zone = us-west-2b, then region is us-west-2
$region = AWS_REGION;

// MY_DOMAIN = .example.com
$my_domain = MY_DOMAIN;

// http*:// permits both https and http.
// You can add a restriction in your Distribution Behavior to redirect all http to https.
// Then this code is portable across distributions.
$cloudfront_base_url = ‘http*://’ . $my_domain . ‘/’;

// Path to cookie protected content.
// Change * to your path after the base url http*://.example.com/
//http*://.example.com/$cookie_path
$cookie_path = ‘*’;

// Full URL for cookie protected content
$allowed_resource = $cloudfront_base_url . $cookie_path;

// Cloudfront requires all policies to expire
// This is the policy level expires
$policy_expires_after = (86400 * 7); // 1 week

// Set your own $expires at the cookie level to zero to make it a session cookie.
// Easier to debug a session cookie.
// And users do not need to be told to clear their cookies to get a new policy,
// if you change the cookie policy.
// Users will get the new policy on login.
$expires = 0;

// Initialize AWS SDK for PHP
$site_path = get_home_path();
$aws_path = ‘vendor/autoload.php’;
$aws_package_path = $site_path . $aws_path;
require_once $aws_package_path;

$sdk_params =
[
‘region’ ► $region,
‘version’ ► ‘latest’,
‘credentials’ ► new \Aws\Credentials\Credentials
(
$user_access_key_id,
$user_secret_access_key
)
];
$sdk = new \Aws\Sdk($sdk_params);
$cloudfront = $sdk->createCloudFront();

// Setup CloudFront cookie #1: CloudFront-Key-Pair-Id
$cookies = [ ];
$cookies[ ‘CloudFront-Key-Pair-Id’ ] = $key_pair_id;

// Setup CloudFront cookie #2: CloudFront-Policy
$raw_policy =
[
‘Statement’ ►
[
[
‘Resource’ ► $allowed_resource,
‘Condition’ ►
[
‘DateLessThan’ ►
[
‘AWS:EpochTime’ ► (time() + $policy_expires_after)
]
]
]
]
];

$policy = json_encode($raw_policy);
$cookies[ ‘CloudFront-Policy’ ] = base64_encode($policy);

// CloudFront cookie #3: CloudFront-Signature
$url_signing_params =
[
‘url’ ► $allowed_resource,
‘policy’ ► $policy,
‘key_pair_id’ ► $key_pair_id,
‘private_key’ ► $private_key
];

$signed_url = $cloudfront->getSignedUrl($url_signing_params);
// We just need the “Signature” query string part of the signed URL
parse_str(parse_url($signed_url, PHP_URL_QUERY), $signed_url_arr);
$signature = $signed_url_arr[ ‘Signature’ ];
$cookies[‘CloudFront-Signature’] = $signature;

// Set cookies
foreach ($cookies as $cookie_name ► $cookie_value)
{
setcookie($cookie_name, $cookie_value, $expires, $cookie_path, $my_domain);
}

}

function setMyCookies() {
setCloudFrontCookies();
}

I can see my buckets, but clicking on them does nothing. I see the red “Loading…” and then nothing.

Btw, I have mounted my S3 buckets inside my server at /mnt/s3/ using the aws s3fs fuse filesystem package.
So, I can see, copy, delete, my files and directories just like any local file.

For example, downloads are at:
/mnt/s3/userdownloads/

What I am hoping would get developed in this plugin would be Cloudfront together with S3, so that Cloudfront will serve my protected content.

What I have working is that I copy private user-specific content to:

/mnt/s3/userdownloads/private_content/username

The url is then userdownloads.example.com/private_content/username/

This content is protected by signed cookies.

Here is the code that I have working that does all this.

I hope it can be integrated with the WPDM package permissions.

Defined constants file, change for your site, and set your own $cookie_path as desired:

/etc/aws_secrets/site.secrets.php
<?php
define('AWS_CLOUDFRONT_ACCESS_KEY_ID','*************');
define('AWS_CLOUDFRONT_KEY_PATH' , '/etc/aws_secrets/cloudfront_privk.pem');
define('MY_DOMAIN' , '.example.com');
define('AWS_CLOUDFRONT_USER_DOWNLOADS','***********.cloudfront.net');
define('AWS_USER_ACCESS_KEY_ID','****************');
define('AWS_USER_SECRET_ACCESS_KEY','********************************');
define('AWS_REGION','us-west-2');
?>

// Add to the end of functions.php in your WordPress theme
add_action('init', 'setMyCookies');

function setCloudFrontCookies(){

    /*
     * We're on app.example.com or www.example.com, files are on S3.
     * We need to send requests to files.example.com, because browsers will not
     * accept cookies for S3 or xxxxxxx.cloudfront.net sent from example.com
     *
     * Therefore, we will set cookies for .example.com,
     * so that they're sent to the CloudFront subdomain files.example.com.
     *
     * 
     * User request needs to go like this:
     *
     *
     * User visits *.example.com (our site)
     * After authenticating user, our site *.example.com sets cookies for
     *  .example.com and redirects to files.example.com
     * DNS sends request to cloudfront.  Cloudfront gets files from S3.
     *
     * Step: 1
     *
     * Set Route 53 (DNS) CNAME record for files.example.com that points to our
     * cloudfront distribution: xxxxxxx.cloudfront.net. 
     * Now requests sent to files.example.com from our site will go to cloudfront.
     *
     * Step: 2
     * In our cloudfront xxxxxxx.cloudfront.net add CNAME files.example.com
     * Now xxxxxxx.cloudfront.net will respond to requests sent to files.example.com
    */
   
    // Settings
    //
    // Location of all defined constants used below
    require_once ('/etc/aws_secrets/site.secrets.php');
    //
    // AWS SDK User
    // Create an IAM user with cloudfront all access for use by the SDK
    $user_access_key_id = AWS_USER_ACCESS_KEY_ID;
    $user_secret_access_key = AWS_USER_SECRET_ACCESS_KEY;

    // AWS Cloudfront Access Key ID
    // NOT a regular IAM user. 
    // In your root account look for "My Security Credentials".
    // Or, from here:
    // https://console.aws.amazon.com/iam/home#/security_credential
    // Look for Your Security Credentials,Cloudfront Key Pairs, Access Key ID
    $key_pair_id = AWS_CLOUDFRONT_ACCESS_KEY_ID;
    // The private key .pem file associated with this Access Key ID.
    $private_key = AWS_CLOUDFRONT_KEY_PATH;
   
    // Region is a subset of the availbiity zone
    // If availbility zone = us-west-2b, then region is us-west-2
    $region = AWS_REGION;

    // MY_DOMAIN = .example.com
    $my_domain = MY_DOMAIN;
   
    // http*:// permits both https and http.
    // You can add a restriction in your Distribution Behavior to redirect all http to https.
    // Then this code is portable across distributions.
    $cloudfront_base_url = 'http*://' . $my_domain . '/';
   
    // Path to cookie protected content.
    // Change * to your path after the base url http*://.example.com/
    //http*://.example.com/$cookie_path
    $cookie_path = '*';
   
    // Full URL for cookie protected content
    $allowed_resource = $cloudfront_base_url . $cookie_path;

    // Cloudfront requires all policies to expire
    // This is the policy level expires
    $policy_expires_after = (86400 * 7); // 1 week

    // Set your own $expires at the cookie level to zero to make it a session cookie.
    // Easier to debug a session cookie. 
    // And users do not need to be told to clear their cookies to get a new policy,
    // if you change the cookie policy.
    // Users will get the new policy on login.
    $expires = 0;
   
    // Initialize AWS SDK for PHP
    $site_path = get_home_path();
    $aws_path = 'vendor/autoload.php';
    $aws_package_path = $site_path . $aws_path;
    require_once $aws_package_path;

    $sdk_params =
    [
        'region' ► $region,
        'version' ► 'latest',
        'credentials' ► new \Aws\Credentials\Credentials
        (
            $user_access_key_id,
            $user_secret_access_key
        )
    ];
    $sdk = new \Aws\Sdk($sdk_params);       
    $cloudfront = $sdk->createCloudFront();

    // Setup CloudFront cookie #1: CloudFront-Key-Pair-Id
    $cookies = [ ];
    $cookies[ 'CloudFront-Key-Pair-Id' ] = $key_pair_id;

    // Setup CloudFront cookie #2: CloudFront-Policy
    $raw_policy =
    [
       'Statement' ►
       [
          [
             'Resource' ► $allowed_resource,
             'Condition' ►
             [
                'DateLessThan' ►
                [
                    'AWS:EpochTime' ► (time() + $policy_expires_after)
                ]
             ]
          ]
       ]
    ];
   
    $policy = json_encode($raw_policy);
    $cookies[ 'CloudFront-Policy' ] = base64_encode($policy);

    // CloudFront cookie #3: CloudFront-Signature
    $url_signing_params =
    [
        'url' ► $allowed_resource,
        'policy' ► $policy,
        'key_pair_id' ► $key_pair_id,
        'private_key' ► $private_key
    ];

    $signed_url = $cloudfront->getSignedUrl($url_signing_params);
    // We just need the "Signature" query string part of the signed URL
    parse_str(parse_url($signed_url, PHP_URL_QUERY), $signed_url_arr);
    $signature = $signed_url_arr[ 'Signature' ];
    $cookies['CloudFront-Signature'] = $signature;

    // Set cookies
    foreach ($cookies as $cookie_name ► $cookie_value)
    {
        setcookie($cookie_name, $cookie_value, $expires, $cookie_path, $my_domain);
    }

}

function setMyCookies() {
    setCloudFrontCookies();
}

Ok I found a solution. It seems to be a css problem. For some reason after the upgrade, the width of icon was set to 0, so it was dissapeared. With css I set it to width:60px and everything is fine now as you can see below:
https://www.themata4all.com/downloads/%CF%80%CE%B1%CE%B3%CE%BA%CF%8D%CF%80%CF%81%CE%B9%CE%B5%CF%82-%CE%B5%CE%BE%CE%B5%CF%84%CE%AC%CF%83%CE%B5%CE%B9%CF%82-2017/

Hi,

Please update the plugin to the latest version 2.9.70.

And for archive page, first you have to install this addon (https://www.wpdownloadmanager.com/download/wpdm-directory-add-on/). Then use the shortcode:

[wpdm-archive button_style=”default" items_per_page="50" category="category-slug" order_by="title" order="asc"] (change the category slug with your downloads category slug)

Frontend Signin page will work with the pro version.

Thanks

Hi,

With the Advanced Access Control add-on, you can control user-specific access to your files and document downloads. So if you want few users can access a package or download then you can use this addon. If you want to allow access to a specific user role then you might create additional user role with (https://wordpress.org/plugins/user-role-editor/) this free plugin rather than the subscriber, and use it to allow access field.

But as you want to have the download limit in terms of time and download counts the possible solution is to use the Wp Pro Membership addon (https://www.wpdownloadmanager.com/download/wp-pro-membership/). Which you can create multiple membership levels and control the single package or package category downloads.

Also, if you also want to control single package download limit for any user role then you can use this addon (https://www.wpdownloadmanager.com/download/download-limit/). This is also an alternate solution. You can use this and make the package access to specific user role and assign the email of the users to that role to give them access to specific packages.

So as you have access setting for the package for any specific user role, you can send the direct package link to that email. They should log in and download the package from the website with that email. Other users will not have access to that package.

Thanks

Hi,

You have to edit /download-manager/tpls/wpdm-all-downloads.php for this shortcode. You can find details here about modifying the shortcode templates.

You need to remove the page link from line 251 by removing href='".get_the_permalink(get_the_ID())."'

Thanks

Hi,

If you set package access to specific users, only they can access the downloads files. Also, there is a new version of the plugin. Please try to install the latest version.

Sorry, There is no function action available yet to upload the file to the s3 bucket yet. But you can explore following functions.

Thanks

Hi,

WooCommerce membership should differently restrict a page to users. Please set allow access to all users and make the package or category restricted by the membership level. The page should restrict to members only. Please send the login in private to check why the download getting the error.

Here is a reply which can help you get to understand.

Thanks