Colin Hart

Hello

In the list of plugins on my site it was still saying Downloader Pro support expired, when I clicked the upgrade link it took me to your site, where I copied the license key and then pasted it into the plugin on my site, then it said it was registered and active again. I think the license key was the same it seemed to need me to update it anyway before it activated again properly.

So it looks like as you said the order was active but for some reason my installation did not pick it up until I forced it to update by refreshing the license key.

Hello

I have replaced my existing plugin with the new one and it seems to be working fine now, I am getting the affiliates page as expected now, thank you for the very quick response and fix.

Regards

Colin

Thank you for your reply. Thats ok I have found the issue and sorted it now.

Hello
I fixed it myself, at the bottom of the file

wp-content/plugins/download-manager/assets/bootstrap/js/popper.min.js

there is a line

//# sourceMappingURL=popper.min.js.map

The “//#” syntax is called a pragma comment, which is a compiler directive. In this case it is giving browsers directions on how to find the js map file

As I don’t really care about having a map for the minified .js file, I simply deleted this line its probably useful for developers.
I did a file find from the top of the WordPress installation and the .map file is not present.

An alternative would probably be to actually get the popper.min.js.map file and put it in the .js directory.

It seems to come down to Browsers are now starting to support this browser directive and there is something not quite right in your config.js file used to build the Bootstrap for release so it is putting this pragma in the .js file but not including the .map file in the build.

The custom templates were not converted they have gone, I think this was due to file permissions in my WordPress installation, the update process was unable to create the XML files but carried on and removed the old templates anyway, that is why I am asking where they were stored in the older version of Download Manager so that I can retrieve them from a backup and recreate them in the updated version.

I know the XML files were not created because I saw error messages in the web server logs indicating it could not create an XML file in a particular folder when I tried to create a custom format in the updated Download Manager, when I looked that folder did not exist, I created the folder gave it appropriate permissions and the new custom format file was created successfully.

ALl I want to know is where the custom formats where stored in previous versions of the Download Manager so I can retrieve them from a backup and recreate them, I do not need anyone logging in and looking around, the custom formats I had are gone in the updated Download Manager, I have now fixed my installation so I can create custom formats.

Thats not the question I asked. What I asked was where the custom formats used to be stored in previous versions of Download Manager so that I can retrieve the custom format I used to have from a backup and put it into the latest version of Download Manager I now have installed.

A different topic now that you have brought up the new features for custom formats/templates, are you saying that custom formats/templates are now stored in temporary storage which you can set to be auto cleaned every day, that seems counter intuitive if I have gone to the trouble of creating custom formats and templates I am hardly likely to want them to be cleaned out every day.

I have investigated further and found that the custom formats are now being stored as xml files in a folder in the site, the location required did not exist on my installation, when I created the folder structure with the appropriate access rights then the custom formats could be created and saved and used.

Now all I have to do is work out what css I had before and put that into this new custom link format and set my packages to use that.

My guess is that the upgrade attempted to create this new folder location to put the existing custom formats into, failed, and carried on removing them from wherever they where stored before anyway. So they where not available for the upgraded download manager to use and all trace of them where they where before seems to have vanished to. In my case it is one custom format and a few packages, in some other customers installations this could be a lot of custom formats discarded and lot of packages reverted to using the default formats, that is a lot of work thrown away.

• This reply was modified 4 years, 11 months ago by Colin Hart.

My apologies, the PayPal payment is working it just takes a while for PayPal to update the account and send out the payment received notifications.

Thank you for this fix to the PayPal notification email it is just what I wanted.

Regards
Colin Hart

I have managed to sort this out now. This still leaves the question of why the original update failed leading to this mess. The earliest error I can see in the web server error log file is this

[Sat Dec 07 21:21:03.478410 2019] [php7:notice] [pid 20223] [client 185.157.233.52:59283] WordPress database error Duplicate column name ‘request_status’ for query ALTER TABLE wp_ahm_emails ADD request_status INT(1) NOT NULL made by activate_plugin, do_action(‘activate_download-manager.old/download-manager.php’), WP_Hook->do_action, WP_Hook->apply_filters, WPDM\\WordPressDownloadManager->install, referer: https://www.oldblogger.com/wp-admin/plugins.php

That is what I have done, finding the latest versions was the problem before but know I know where they are its fine thank you.