• Resolved tweakben

    (@tweakben)


    Howdy! Plugin looks fantastic, super easy to use, thanks for all your hard work on this!

    I’m having two problems with the plugin, under WP 3.9.1 and BuddyPress 2.0.x and a WooThemes Superstore theme.

    1.) Nobody can actually download a file. It starts to transfer the file, and the file ends up being 1Kb in size. So if the file was a 200Mb movie in mp4, the filename.mp4 contains text that says:

    [code]

    <b>Fatal error</b>: Allowed memory size of 188743680 bytes exhausted (tried to allocate 156381184 bytes) in <b>/home/XXXXXXXXXXXX/public_html/wp-includes/functions.php</b> on line <b>2935</b>
    [/code]

    2.) If you “drop files” to the upload box, it uploads them twice. Similarly, if you select the file to upload, it opens the file open dialog box twice.

    Any advice?

    Thanks so much!

    https://wordpress.org/plugins/buddydrive/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter tweakben

    (@tweakben)

    And then these are in the error_log for apache:

    [16-May-2014 15:36:05 UTC] PHP Fatal error: Allowed memory size of 188743680 bytes exhausted (tried to allocate 481038336 bytes) in /home/XXXXXX/public_html/wp-content/plugins/buddydrive/includes/buddydrive-item-actions.php on line 193
    [16-May-2014 15:39:19 UTC] PHP Fatal error: Allowed memory size of 188743680 bytes exhausted (tried to allocate 481038336 bytes) in /home/XXXXXX/public_html/wp-content/plugins/buddydrive/includes/buddydrive-item-actions.php on line 193Howdy! Plugin looks fantastic, super easy to use, thanks for all your hard work on this!

    This is usually a site/server issue – not a plugin specific one. Try increasing the memory available to PHP.

    Thread Starter tweakben

    (@tweakben)

    The memory limit is 256Mb, max post & file size is 2GB. It’s a dedicated server of which the limits are all set properly.

    Why would WordPress’s memory limit matter when trying to send a file to a person? It shouldnt need 481Mb memory allocated to download a 481Mb file. It should just serve the file.

    The memory limit is 256Mb

    Actually it’s only 180M according to the error message. Perhaps you need to speak to your hosts about this?

    Thread Starter tweakben

    (@tweakben)

    Your right, it’s 180Mb. If you read the post, you’d see that I host my own site on my own dedicated server. So I dont need to speak to my host.

    But in all due respect, esmi, my question is for the plugin author, not for the theme diva and forum moderator. The question is regarding the function of his plugin, not in the function of my memory limits, which, at 180Mb are five times what most wordpress hosts memory limits are. I respectfully request that you allow the plugin author to help resolve this issue rather than clouding up a thread that is not about WordPress memory limits, but in fact, two completely unrelated issues.

    It is not plugin specific – it’s site specific. You have a PHP memory issue.

    Thread Starter tweakben

    (@tweakben)

    esmi: Respectfully, I disagree. If it was a memory issue, then the plugin could not be used by 99% of hosts out there. The support forums would be filled up with memory issues for this plugin. But there isnt a single mention of it here at all.

    If this plugin required a higher memory limit than 180Mb, it would clearly say so, too.

    Finally, if you read the error logs, it’s trying to use 481038336 bytes of memory for a 481038336 file to download. That’s ~481Mb. What if there’s a 1GB file on the site? Does it need 1GB of memory to allow someone to download? Obviously, this line of thinking is highly incorrect.

    Have you tried deactivating all other plugins on your site and switching to the default theme before activating this plugin?

    Thread Starter tweakben

    (@tweakben)

    It’s nothing conflicting with a plugin or a theme, as the download begins to serve but serves an error message encoded within the actual file being downloaded. It has to do with the way php’s readfile is being used on line 193 of the code.

    readfile() will not present any memory issues, even when sending large files, on its own. It might be a problem with the ob_get_level().

    I know your trying to help, but back to what I asked you originally, not to clutter the thread with misguided general checklists, and to allow the plugin author who has devoted many hours to writing and using this plugin to reply to the errors generated by the plugins syntax. 😉

    Thread Starter tweakben

    (@tweakben)

    No love no support from the plugin author. Deleted and removed.

    Plugin Contributor Mathieu Viet

    (@imath)

    Sorry to read that & that you add trouble with the plugin. I couldn’t find time to look at this support lately. I’m sure you’ll find the plugin that will suit your needs.
    Bye

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Fatal error: Allowed memory size exhausted’ is closed to new replies.