Shaon, Any thoughts regarding the screenshot I’ve attached. Wrong line numbers?
Shaon,
Please look at the screenshot I’ve attached. 2468 and 2470?
Hi Shaon,
I’ve just installed the latest WPDM upgrade version Version 4.1.8. If you’ve included the [file_list] button customization option in that release, how do I make it happen? Or, will this custom button option be in the next upgrade? Thanks!
Shaon, The problem has been resolved. There was a corrupt package that caused this 502 error. Ad soon as I deleted that package, everything worked great. This is one to remember! Thanks for all your support. You’ve been great. Close this ticket.
Shaon, I hear you. Before I push back on the host provider, would there be any “path” issue for subsites when calling the all files list?
Even if I check all categories (not leaving blank) I get the 502 on the subsite.
[wpdm_packages link_template="link-template-search-result" order_by="post_title" order="asc" paging="asc" items_per_page="10" title="" desc="" cols=1 colsphone=1 colspad=1]
See here:
http://cef.wrc.wpengine.com/archived-resources/
Thanks for the quick response Shaon.
Shaon, What do you think? Here’s what my host provider found…
—- Host Provider Message Begins —–
We’ve dug into this further for you and upon extensive investigation I’ve discovered the cause of the issue.
Within the Staging site I tried creating a secondary sub-site for testing by cloning the main site over to a new sub-site. When loading the URL being requested however, everything worked as expected.
The cause of the issue is due to the ‘Link Template’ package being an option within All Packages > Link Template. By moving this item to the Trash, the remaining downloads display without any issues.
I’ve left this as-is on the Live site as I’m unsure of its exact utility in the Production environment, but you can see the effects of this on the Staging environment here: http://cef-wrc-wpengine-com.wrc.staging.wpengine.com/?wpdmtask=get_downloads&category=0
I would recommend reviewing the settings on the ‘Link Template’ page and perhaps adjusting them to different settings to prevent the issue in the future. Upon review, it looks like the package ID may be incorrect, per the contents of the package:
[wpdm_package id=3096 template="link-template-default-icon"]
[wpdm_package id=3059 template="link-template-default.php"]
Right now the two package Ids seem inconsistent. I’m unsure if this is intentional, However you may reach out to the Plugin developer directly to see if they’ve accounted for ‘Link Template’ being utilized within the Packages section.
—— Host Provider message ends ——-
Not sure what the package id has to do with archive shortcode when trying to display all in a file list…. Shaon, can you shed some light on this? What’s your take? I still get the “loading” icon on the live site.
Hey there Shaon,
So I did contact our host provider. Here’s what they are saying back after trying to recreate the issue:
——-begin——-
Thank you for your assistance and authorization while we work on this. Checking into the issue further after pushing to staging, the problem appears to stem from this call in the code:
http://cef-wrc-wpengine-com.wrc.staging.wpengine.com/?wpdmtask=get_downloads&pg=3109&category=0
This specific URL is being called, but is causing a segmentation fault in Apache, which in turn causes a 502 in nginx, which then results in the “Loading” box being stuck on screen. This is not due to the memory limit, but is instead due to the code. Changing the category in the above URL to anything other than 0 will load correctly without an nginx 502 error. This leads me to believe the code isn’t designed to properly handle the category being 0, or the categories may be misconfigured. In either case, this is a problem with that specific plugin and is not related to the memory limit. While we’re unable to assist further with this, due to it being a coding issue, presenting the information I’ve just given you to the plugin author should help them diagnose the problem. Essentially, the above URL is the cause of the issue.
The site itself is actually functioning perfectly, outside of the initial loading box. Clicking any button for the downloads works fine to expand the boxes and removes the Loading box, as well. So, the problem is only present on the initial load of the page. It is still a problem, but if it were a memory limit issue, the functionality of the site altogether probably would not work correctly.
If the developer of that plugin gives you any other information about server settings we can help with, please let us know and we can assist if we’re able.
——end——–
In turn, I responded….
Thanks for your answer David. The only trouble I have with your response is that that same code loads successfully on the parent site of the multisite install. See page: http://wrc.wpengine.com/jd-test-wpdm-archive/
So how does one page work, and not the other?
Idea on what to try next? The categories look fine. There are only 6. There are only about 10 packages. This shouldn’t be happening.
Still an issue after making a memory limit change. We will be using this plugin on about 20 subsites for all our downloads. We need this to work like it does for other companies.
The log refers to:
“[WPE Monitoring] Stopwatch php.pod-3147.function.session_start.duration exceeded 200ms.”
Here’s the code added to our wp-config.php file on wrc install to increase PHP memory limit:
define( ‘WP_MEMORY_LIMIT’, ‘512M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );
I’m checking with our provider to be sure that on a multisite install that the memory increase affects subsites as well.
Thanks again Shaon. Worked very well!
Line 5 appears as: <li><a href="#browse"><?php echo __('Browse','wpdmpro'); ?></a></li>
Line 149 appears as: <?php if(current_user_can('access_server_browser')) wpdm_file_browser(); ?>
Shaon, Ok! But, it might be wise to tell me what the line of code says to be sure my editor WRAP isn’t pointing to a different line of code. Just to be safe!
Hi Shaon, I’ve just upgraded now to version 4.1.7 and was going to reapply these customizations. I removed the browse tab and that worked as noted above. I don’t see the 2nd line of code anymore to remove as you stated above re: wpdm_file_browser. What do I need to do to remove the directory tree folder beneath the DROP FILES HERE box after 4.1.7 upgrade?
Thanks,
j
success
Worked great! Thanks Shaon. I will take care in future upgrades to remove the same lines until the multisite fix is available as part of an upgrade. Many thanks – close ticket.
Hi Shaon,
Ok – done, I’ve removed the Browse tab line of code. But after testing that I can see it still leaves the directory tree beneath the tabbed box (see attached) where a user could drag and drop file(s) into the upload box. We need to remove that as well since it too is pointing at root. How can I remove that?
Note: I don’t have a Dir Addon installed either.
Hey Shaon. I think you’ve earned a SUPER HERO badge. I’ve just upgraded to the v4.1.4 WPDM pro. And…(drum roll please) – You fixed the multisite duplication issue as promised. I’m very happy to report my tests proves how brilliant you are! Kudos to you! How did you do it?
Anything I should know regarding settings for each subsite?
Many thanks from one happy customer 🙂
j
Ok – looking forward to it. I’ll proceed with development on this end in another direction until its ready.
Hi Shaon, It has been a month since my last request. I am checking in to see how you are doing on the Download Manager Pro v4.1.4 upgrade and if you could provide a date when this might be available. I appreciate that you are busy – but I also am being held accountable to get this multisite development completed. Please provide. Thank you!
Nice! Thank you Shaon. Well done!
Understood. But until the multisite blog.dir fix is included, the upgrade and the product is unusable for our purpose. We can’t have duplicate IDs messing up which file is getting downloaded. Sorry to press you, but when would you say the next version with this fix would be ready? I do appreciate all you’ve provided thus far.
Hi Shaon, I see that there is an update from 4.1.0 to 4.1.2. It didn’t appear that this included the Multisite seperate blog.dir updoad directories was included. I also didn’t see a way to upgrade in the WP backend plugin dashboard – just the notice. What is the proper method to upgrade your plugin? Thanks for your assistance.