I have followed this up with more research. The table is in the server database, but the ###. above is incorrect from what the table prefix actually is. Would anyone be able to tell me where that is set or I can adjust it to match what the database is named?
I downloaded the version on your site (found here: https://www.wpdownloadmanager.com/download/wpdm-extended-short-codes/) and it also reports to be 3.0.4 when uploaded to the site even though the page I download it from did say 3.0.5. I’m pretty confident your zipped file has the wrong version details in the plugin file.
I also am interested in a fix for this soon.
In my frustration I forgot to mention I am using the category tag.
[wpdm_category id="category," operator="IN" orderby="post_title" order="asc" item_per_page="20" template="55ad4baa968fd" cols=1 colspad=1 colsphone=1 toolbar=0]
For example. The above is neither in title order and stops at 12 items when it used to work fine several versions of Download Manager Pro ago. I have these types of shortcodes throughout my website and none of them work correctly anymore. I have changed them out for order_by and items_per_page as well. It is stupid to have to change shortcodes throughout my website in order to continue to use your plugin after it is updated (with NO documentation of the change before hand at a minimum).
I would like to be able to control this better as well.
I have this same issue. What version of the plugin is the fixed code in? My plugin (v 6.0.2) doesn’t appear to show me when updates are available anymore.
Thanks.
Jonathon
I did use categories=”slug” and the shortcode seemed to ignored it completely. I will have a look at the asset manager, but this is for a category view and the asset manager sounded more like individual packages, but I haven’t looked at it yet. Thank you.
Pat,
You’re the best. I’m so glad you not only said you fixed it, but took the couple more seconds to tell us how. This has saved me.
J
I disagree. The whole point of a changelog page is to report changes. That is no matter how big or how small. You should include all versions of your product. Please make this best practice change moving forward.
Jonathon
That did work, but what about the two different versions of the plugin?
I also had this problem and the plugin above appears to have fixed it. Might I suggest rolling this plugin into the Core package? it seems like something that should just be done as part of the upgrade process.
I am having this same issue. I was even able to update an addon from within Download Manager, but the main plugin I keep having to update manually over SFTP.
I have created a custom role called that I would like to give the ability to add their own downloads, but I do not want them to be able to post to the blog or use anything except for the Download Manager main functions of adding packages. I used to be able to do this, but for some reason now the users cannot see the Downloads and if they can see it they have no privledges to add or edit downloads they already created (back when it worked).
Thoughts?
I have done this for my main client. I added the full url and reworded the link label to make it clear it wasn’t a download. I had no trouble as long as I included the http(s):// at the beginning. I haven’t done it lately though so maybe something has changed.
Hope that helps.
The solution to this issue is posted here: https://www.wpdownloadmanager.com/support/topic/download-button-is-disappear/
The solution to this issue is posted here: https://www.wpdownloadmanager.com/support/topic/download-button-is-disappear/
Thank you. That was fast and just what I needed.
I had the same issue. Actually I have never been able to use the built in update mechanic. Are you saying the updater will work in 4.6.5? I don’t know why you all don’t just support WordPress built in update mechanic.
This issue appears to have been resolved. It turned out to be caused by the theme (Jupiter) which was not handling php7 properly in certain cases.
Well I haven’t heard anything from the developers. My more immediate problem is that anyone who searches our website using a keyword that is also in a downloadable package the website crashes with a 500 gateway error. I have resolved most of the speed issues by changing our host and disabling redundant calls to javascripts between plugins.
Anyone know how to remove Download Manager Packages from WP Search?
Jonathon
The problem could be related to a memory leak? The error message I get is that the site could not allocate enough memory.
Replacing that file does appear to have resolved the problem. Is there any additional testing I should do? Will this file be included in a future version of the manager?