• Hello,

    I found an issue while using your Download Plugin plugin.Environment

    • Local Environment: Windows (WordPress local installation)
    • Live Environment: HTTPS server (Linux)

    Issue Description

    I installed the Download Plugin plugin on my local WordPress setup and used it to download plugins. I tested this with multiple plugins, including your own plugin.

    After downloading the plugin ZIP from my local environment, I uploaded it directly to my live HTTPS server and tried to activate it. During activation, WordPress threw a fatal error.

    I also noticed that the plugin directory structure was changed after uploading. Please refer to the attached screenshot showing the directory that was created after activation.

    To verify the issue, I manually created a ZIP of the same plugin from my local environment (without using the Download Plugin plugin) and uploaded it to the same live server. In that case, the plugin activated and worked correctly.Possible Cause

    It appears the ZIP generated by the Download Plugin plugin may be preserving Windows-style directory separators (\) instead of converting them to Unix/Linux directory separators (/).

    Since my local environment uses backslashes (\) and the live Linux server expects forward slashes (/), I suspect this is causing the incorrect directory structure and resulting in the fatal error.

    Could you please investigate this issue? I have attached a screenshot of the directory structure created after uploading the ZIP generated by your plugin.

    Reference Image: https://ibb.co/vCHFZXC8

    Thank you.

    • This topic was modified 4 days, 22 hours ago by Jan Dembowski. Reason: Removing incorrect NSFW tag. That's for a ADULT site and not for support
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support vincentpg

    (@vincentpg)

    Hi,

    Thank you for reporting this issue and for providing the detailed information about your test environment and findings.

    Based on your description, we understand that the ZIP file generated by the Download Plugin plugin works correctly on your local Windows installation but results in an incorrect directory structure and a fatal error when uploaded to a Linux-based production server.

    We have tested the same workflow on our end by downloading plugins using the Download Plugin plugin and then uploading them to another WordPress installation, and the process worked correctly without any directory structure issues or activation errors.

    To help us investigate further, could you please share the following information?

    • The name and version of the affected plugin.
    • The exact fatal error message from the live server.
    • The ZIP file generated by the Download Plugin plugin.
    • The local server environment you are using (for example: XAMPP, WAMP, LocalWP, Laragon, etc.).
    • The PHP version used on your local environment.
    • The PHP version used on the live server.
    • If possible, a manually created ZIP of the same plugin for comparison.

    This information will help us reproduce the issue more accurately and determine whether there is an environment-specific issue related to ZIP generation or path handling.

    Thank you for bringing this to our attention. We look forward to your response.

    Thread Starter Parth Dangar

    (@pdangar)

    Thank you for your response.

    Please find the requested information below:

    • Local Environment: LocalWP
    • ZIP File: Attached is the ZIP file generated using the Download Plugin plugin from my local environment. This ZIP is of your own plugin.
    • Plugin Tested: Download Plugin (your plugin)
    • Plugin Versions Tested: I tested with multiple versions of the plugin, including the latest available version, and experienced the same issue.

    Plugin file link: https://we.tl/t-Vizx6WchQmRURovx

    Plugin Support vincentpg

    (@vincentpg)

    Hi,

    Thank you for sharing the additional information and the generated ZIP file.

    We have received the details and are currently investigating the issue on our end. Our team will review the archive structure and attempt to reproduce the behavior using a similar environment.

    We appreciate your detailed report and the effort you put into helping us diagnose the issue. We’ll keep you updated as soon as we have more information or findings to share.

    Thank you for your patience.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.