Regular Baptist Press

Thank you for the quick response!

Thank you for the help. It now seems to be working properly.

• This reply was modified 2 years, 6 months ago by Regular Baptist Press.

I also tested it with All Visitors and saw that it worked.

I’m struggling with how I can configure things differently though, as when I’m logged in as an administrator I still get the same error. If the Administrator can’t view the file through doc_preview, then there is no permission I can add to other users that would allow it.

Could you possibly look into it further? How can it be blocked for an administrator? Also, any user who is logged in can download the file just fine and see all other details. It’s only the doc_preview that is having an issue. It seems like maybe there is something in the doc_preview that is causing an issue since everything else on the page is working as it should.

I have checked, and the proper permissions are there.

This stopped working correctly after version 5.4.1 – I have two other sites which still run that version and it works correctly. I have not been able to upgrade them since due to this issue.

I hope you all can find what it is and get it fixed so I can keep my sites updated.

This seems to possibly be a bigger issue. I just looked at some of my older downloads, which were uploaded back in September 2019 (before I began having the import issue), and they are now listing the “root://” as the directory in the “Attach Dir” field, which is not correct. However, if I go to the database and check the postmeta table, the directory is set correctly.

If I look at packages which I have created more recently (from the site, not via bulk import), I see that the “Attach Dir” field in the postmeta table is encoded. These are packages that are working fine, and pointing to the correct directory.

So, it seems as if maybe there is an issue somewhere with data that’s not encoded? Or their not being encoded when imported?

Again, checking back to see if there are any updates. This is still an issue, even though I’ve updated to 5.3.3. Thanks

Hi – sorry for not getting back to this sooner.

I have tried with several different types of paths/links and none of them work. They all set it to root://, then when I update, it changes to root://wp-admin. I have to go in manually choose the directory on each download to correct the issue.

That’s because that one was created before I did the last update. It seems to only be an issue with new imports.

Please run the import file, and check the file it imports. I again today imported files, then updated, and had the same issue.

I’m not importing files, I’m setting the directory (package_dir) – again, I’ve done these for over a year, with no issues until this latest update. I have my file setup using the sample.csv structure.

And also – yes – when I first import, everything is fine. HOWEVER, if I update a download package that I imported that set the package_dir, it resets the attached directory to “root://wp-admin”. Did you test this on the site? Add a character to the description, then click “Update”.

If you run an import with the file I provided, you should see them created. Then, go in and update one, and you will see that they “Attach Dir” is reset, and when downloading from the package, you do not get the correct files.