misanthrop

Actually, the general challenges to write and support this plugin are:

1. I have to do this in my spare time, and currently, I am alone. Had some support in the past to make an upgrade to version 2, but not at the moment.
2. The setup dependencies between different browsers and operation systems and also servers (and other installed WP plugins) seems to be terribly complicated. I cannot reproduce any of the recent errors mentioned in this form. Unfortunately, because I would like to fix them. But I simply can’t, because I cannot change any code blindly.

Anyone here who can support doing local code changes in such failure scenarios and provide me with the potential fix so that I can incorporate the same in a new version?

What server and client setups are you using? And specifically on which operating system and browser does it fail?

This is really difficult to say. It should work in most of the Environments since the latest changes. Can you check your WordPress option “dc_header_content_type”?

Thank you for the hint! Actually, I don’t know why I missed the ob_end_flush() during the implementation, there must be a reason why I have not added the function. Anyway, once I will be back from current travel, i.e. in September, I will try and update the plugin accordingly.

Unfortunately, I am not familiar with the WP core, and due to some urgencies I currently don’t have the capacity to look deeper into that. Could you try to point out what the changes could be? Actually, my plugin works simple as hell, it just streams the bytes for download to the client, there is nearly no more magic behind it, and I don’t know why the WP core should stop that byte stream at 12,xxx,xxx bytes.

There is a rar scenario that MYSQL settings would not allow for more than a certain amount of download releases. We have tried to fix this with a patch with is not contained in the main release (version 2.1.1). Can you try this and see if it works?

Thank you for the hint and sorry for that, I cannot guarantee that there is no interference with other plugins especially when these manipulate the HTTP headers in a way that breaks the WP download plugin. If I had more capacity I would be able to test this is maybe find a solution so that both plugins can coexist, but currently my development is short if non-existent.

Thank you very much, this will really help.

As the initiating developer for this plugin it am not able to spend as much time as I want on this (not even 10 minutes in the last 10 months), so valuable help like yours is always appreciated.

As you have announced problems with the encryption, I did not want to include your changes at once, and also I had to update the plugin with a minor patch for version 2.1.1.

But it would be great if you could sent me another update or I could enable you for direct communit if you would be interested to support development on the plugin.

Even with the many hints you have provided, it is not possible for me to provide a diagnose for this kind of problem. First of all, I would go to your phpMyAdmin area and backup all wp_dc_* tables, because these tables would contain your codes. Just to make sure not to lose your codes.

The other thing might be related to a plug-in you have installed (some caching plug-in maybe?) or something your host has changed on the server.

Thank you for the suggestion. It might have to do something with your linux/PHP versions. Anyway, it would strongly recommend not to use blanks in filenames on a web server.

Oh dear, it’s already 8 months since this request came in. I will see what I can do, but currently time is very very short.

Thank you for the suggestion. I have taken this as another feature suggestion into our backlog. We are short on development resources but hopefully this feature will come soon.

Thank you very much for the advice, I think this could help others solving their issues in this area!

Can you check at database level if the codes are created? I also don’t know about the WPMU environment, the plugin is only developed for a standard WP installation.

The plugin sends standard headers to the browser to download the respective files. The W3 Cache plugin somehow seems to ammend or overwrite these headers. Maybe it helps to exclude the wp-download-code plugin folder from the caching?