midihead7

You have not recently logged in to check my staging site so you can’t say that it is working fine on MY site. I can see when you log into my staging site and the last time you logged in was on October 5, 2020 at 8:45 pm Pacific Time.

I just created a new IAM access key and secret key specifically for WPDM and I followed the instructions that you provided exactly and entered the new keys in the WPDM Amazon S3 settings and saved the settings.

Group User: https://snipboard.io/OKuRX3.jpg
Group Permissions: https://snipboard.io/AEeNWD.jpg

Even after doing this, no other folders in the whmediacentral bucket are visible other than the AUDIO FILES folder. https://snipboard.io/sbdXIk.jpg

I just tried creating a new folder called another-folder in the whmediacentral directory (bucket) using my Amazon S3 account directly. The new folder still doesn’t show in the Amazon S3 Manager built into WPDM Amazon S3. I also tried creating a new directory from within the Amazon S3 Manager window in WPDM Amazon S3. I can see that the folder gets created in my Amazon S3 account itself but the newly created folder still refuses to appear inside of the whmdediacentral directory (bucket).

Please disregard the very last reply about the Console errors (I had pasted a link to this ticket in the Editor and I suspect it was throwing the Console errors because this thread is password protected).

Please address the folder access issues and the Page Template/Link Template issues (mentioned previously) as soon as possible. If we don’t come to a resolution soon, I’ll need to switch to another solution and discontinue using your products.

As I’ve said, I have already checked the permissions. The permissions for the AUDIO FILES folder and the VIDEO FILES folder are exactly the same. If I roll back the WPDM Amazon S3 plugin to version 2.7.8, then I can see the VIDEO FILES folder (and the files inside it) on the Edit Package screen (although I can’t add files to the package because that version isn’t compatible with Download Manager 5.2.3). The problem is not my Amazon S3 permissions. The permissions are the same as they have been for at least 4 years. The issue didn’t start until your developers made changes to both Download Manager and WPDM Amazon S3.

Several years ago, there was an issue where spaces in Amazon S3 bucket and folder names caused issues with WPDM Amazon S3 being able to display buckets (which was fixed in an update to the plugin). Since my Amazon sub-folder names do have spaces, perhaps there is something going on in your software again related to this?

Please escalate this ticket to advanced support as soon as possible. Thank you.

I didn’t deactivate the credentials previously provided. I just logged in with them and they worked fine. Please try again and address the issues ASAP.

I have downloaded and installed the latest WPDM Amazon S3 plugin (version 2.8.2) and have updated to Download Manager 5.2.3. I can now attach files to a package however the Amazon S3 plugin is only showing ONE of my buckets that is inside of the parent bucket. I have a parent bucket called “whmediacentral” with two sub-buckets inside of that (called AUDIO FILES and VIDEO FILES). Only the AUDIO FILES bucket is accessible via the WPDM Amazon S3 plugin interface. I have clicked the SAVE SETTINGS button on the Amazon S3 settings page but this doesn’t fix the issue. Please fix this ASAP.

Also, I see a few new options in the settings for the WPDM Amazon S3 plugin settings (as seen in the screenshot). Do these need to be set and if so, how should they be correctly set?? https://snipboard.io/uKnwmq.jpg

In addition, I have discovered another new issue where, after updating to the most recent version of Download Manager, the Page Templates and Link Templates have become UNSET in each EXISTING package. Since I have 130 packages, it will take a long time to manually go back and reset the templates in every package. (https://snipboard.io/ANIEG7.jpg) Please provide a way for me to relink all of my templates globally (probably via a function of some kind). I was previously provided this function by WPDM Support (see this post: https://www.wpdownloadmanager.com/support/topic/reposted-custom-link-and-page-templates-missing-again/#post-112519) however there appears to be syntax errors in this code (on lines 3 through 5) which crashes my site (and I did replace the page_template_id and link_template_id with my own template IDs):

function wpdm_bulk_update_templates(){
    $params = array(
        'post_type' ► 'wpdmpro',
        'posts_per_page' ► -1,
    );
    $packs = new WP_Query( $params );
    while( $packs->have_posts() ) {
        $packs->the_post();
        global $post;
        update_post_meta(get_the_ID(),'_wpdm_page_template','page_template_id');
        update_post_meta(get_the_ID(),'_wpdm_template','link_template_id');
    }
}
add_action('init', 'wpdm_bulk_update_templates');

Do you have an update on this issue? It’s been 5 days since your last reply. Version 5.2.2 didn’t fix the issue.

Thank you for the CSS code. I added the [title] with inline styling to my custom page template to make it look like it did before so everything looks like it should now. You may close this ticket.

Also, could you please provide the proper code to bulk update the link templates as well?

I went ahead and created the custom templates in the directories as suggested, naming the files using the original template IDs to keep the IDs the same as what is stored in the database. I then deleted my old custom templates through the Templates dashboard. After doing this, my new custom templates (in the directories) are working properly on the front end however I saw an issue where there appeared to be no template selected in each package.

Since I didn’t see any other place to set this in the database other than the _wpdm_template and _wpdm_page_template meta values (which were already set properly), I still had to go into each package and manually reset the templates there. If I saved a package without doing so, it would revert to several of the other default templates (if any were active). Would there have been another place to reset the templates for each package in the database or was manually resetting in each package the only way in this case?