UPDATE: So I was able to restore everything myself through the database in phpMyAdmin without having to relink the templates in every package manually (thankfully).
To restore the missing custom templates themselves: in the options
table, I found the option_name fields _fm_link_templates
and _fm_page_templates
in the database, edited each of them and pasted in the original option_value for each (from my old database backup that still contained this data) and saved it. This restored my missing templates.
To relink the templates for all packages: I found that the package Link Template and package Page Template are set in the postmeta
table under _wpdm_template
for the link template and _wpdm_page_template
for the page template. I ran the following SQL queries to bulk update the old meta_value for each template (using my own template IDs):
Doing this set all of my packages to use the desired custom templates I designed without editing each package manually in WordPress.
Even though I have fixed this on my own, I would still like your thoughts on why the data in _fm_link_templates
and _fm_page_templates
was reset when I updated to version 5.0.1 and what can be done to avoid this from happening in the future. I have made careful notes to be able to fix this again in the future if it happens but it would obviously be ideal if this didn’t keep breaking when updating.
My issues appear to have went away after you accessed my admin. I assumed that you fixed something while you were in there. My downloads are working but I don’t know why because you didn’t say if you fixed anything. Did you fix or do anything? If so, what?
I had made a staging copy of my site last week and it was still having the issues as of this morning. I went into the Cloud Storage settings where my Amazon S3 account credentials are set and I just re-saved the settings by clicking the Save Settings button. Right after doing that, the downloads started working again on my staging site too. Ron, I’d recommend that you try re-saving your settings to see if it gets your S3 downloads working again. Perhaps support re-saved my settings while they were in there.
Shahriar, you couldn’t access my own package downloads because I have my downloads protected by another membership plugin so that only certain membership roles can access the downloads. For future reference, I’ve found that you can still access one of my protected package downloads by going to the edit screen for one of my packages and then clicking Preview Changes. This will open up the page for the package and allow testing of the Download buttons even though the package is protected.
I see that you logged in about 2 hours ago and it appears you have fixed the issue but you haven’t replied yet. I’d like to know what the issue was, what you did to fix it and if this is patched for future versions. Thank you.
Where is support? It’s been over 48 hours and no response. I also see tickets by others building up with no response in days. My issues need to be resolved quickly otherwise we will seriously consider taking our business elsewhere. We have paid for support and we expect it in a reasonably timely manner. Thank you.
Also, trying to use the Amazon S3 Manager in the backend doesn’t work either. The buckets won’t load under the “Explore Buckets” section on the left.
I think I just got it working again. I was looking at the settings for Advanced Custom fields and I saw that the Who Can Manage section permission settings had no option selected at all. I then checked the Administrator box, saved the settings and now the entry fields and field data appear to be working again. The Who Can Manage and Who Can View permissions settings were apparently added in the 1.8.0 update as they were not present in the previous version (1.7.4) that is still running on my staging site. I would think that the Who Can Manage settings should have defaulted to the Administrator setting but this wasn’t the case after I updated.
In addition to the entry fields missing on the Edit Package page, the field data is also not displaying anywhere on the frontend. See the attached images.
Clearing the Chrome browser cache fixed it. I was able to update by clicking Update Now on the Plugins page. Thanks for your help. You may close this ticket now.
As I showed in my post from July 4, we can’t click the Update Now option on the plugins page because it says “Automatic update is unavailable for this plugin.” See my most recent screenshot.
It is still not working.
This is not fixed. The ‘update not available message is still there. See attached.
Can I please get an update on the auto update in WordPress not working? I know that I can manually update but auto update is supposed to be working. Thank you.
I did not manually delete the templates in Downloads > Templates. I did nothing to cause them to be removed from the database options table either. Because I needed this fixed quickly, I had to rebuild new custom templates and then reassign them one at a time to all 91 of our packages. I don’t know when this issue occurred and since my site backup with the custom templates intact is several months old, I can’t easily restore directly from that backup since we have a WooCommerce store with many orders that have come in since then. We had 3 custom templates that disappeared.
Also, I see that WPDM 4.7.7 is now available but the automatic update within WordPress is again not working. I thought that this issue had been resolved since the last update came out but apparently not. My WPDM Pro license is current and active. See attached screenshot.
I am having the same problem. My Pro license is current and active.
Since clicking the ‘Check for Updates’ button and waiting 24 hours, it is now showing the latest version as 2.7.2. Thanks for your help. You may close this ticket now.
Could I please get an answer to my last post? Thank you.
Version 4.7.6 appears to have corrected the Updates tab login issue however I do see another minor issue. I was notified yesterday that the version 2.7.2 update was available for Advanced TinyMCE Button. I clicked the Check for Updates button however this does not refresh the version number that is currently the latest version. I had to manually update the plugin via FTP which is now reflected in the dashboard but the latest version still shows as version 2.7.1. I already tried logging out and back in again and clicking the Check for Updates button after that but it still doesn’t show the correct latest version. See attached screenshot. Thanks.
I see that someone logged in to my site to check the issue about 11 hours ago. Do you have an update on the Updates tab login issue?
I have tested with all other plugins disabled and with a default WordPress theme active yet the issue is still there. I have also tried deactivating, deleting the plugin and reinstalling (both through the WordPress dashboard and manually) with no change.
Thanks.
By the way, I’m running Download Manager Pro 4.7.4 and WordPress 4.9.6.