misanthrop

You should:
1. Install the plugin on the new server (empty).
2. Export all download code related tables from the old server (depending on your WP database prefix, usually “wp_”, so normally all tables wp_dc_*).
3. Import all the data into the tables on the new server.
4. If you have moved all pages/posts as well, then the [download] shortcodes should work, otherwise you simply have to recreate them.

I currently cannot reproduce the issue. Are you sure that you only have one download item defined on your page?

It most probably to do something with the HTTP headers, I would love to apply a fix if I would just happen to know what goes wrong in Safari/MAC (and I don’t have a MAC to try it out). Could you send me snapshots of your HTTP headers / network trace in Safari?

Good question. As I don’t have a MAC in my test environment, it would be great to hear from others regarding their experiences.

Thank you.

Sorry for the long delay in my replies, I am quite busy and this plug-in development has to be hobby work. Do you still have the issue?

Maybe you hit a threshold defined by your provider. For example the max memory. Can you successively increase the size of a (dummy) file and check when it breaks?

The last plugin update is a long time ago, so it could also be related to browser changes. Which browser types and versions are affected?

At the moment, unfortunately not with programming. You would have to use the logic form shortcode.php in one of your template php files to achieve that with proramming.

But shortcodes are according to my understanding handled in the core of WordPress, not in the theme, so why aren’t they available?

Thank you. Unfortunately no progress so far, because of time limitation ?? I am on a tight schedule and can only spend like 30-60 minutes a month on plugin work – and this goes mostly into support activities. (Support appreciated :-))

I can’t find a hint in the code for version 2.3.0. Do you have someone on your end with some small programming skills to debug/look into this? Because I cannot really reproduce the issue.

The plugin upgrade as such can be as risky as any other software update. You need to take a database upgrade of course and ideally have a test or integration environment where you can play through the whole process. But basically if you have the codes exported from your database, it shoud not be a problem to use this export to fix potential issues which could come after the upgrade.

The last change to the database schema was even before version 2.3.0 by the way.

Sorry, no progress so far due to strict time limitation on my side. Maybe during the X-mas holidays…

Well, thank you, this is already on the feature backlog list. I will try to include it but currently my time is very very limited. (Support from other developers is of course always appreciated :-))

Thank you very much! I will check that and include the fix in the next version if I can do it without any further side effects.

It’s already logged as a possible feature for the future. Let’s hope that I will find some time to implement. But this plugin is just one of my many side activities, time is scarce…