vincentpg

Hi,

Thank you for reporting this issue and for providing the detailed explanation.

You’re absolutely right. Since dpwap_plugin_download_link() is hooked to a filter, it should always return the expected data type. Returning null on the permission check can indeed cause the plugin list table to fail when WordPress expects an array.

We’ll update the function to return the original $links array (instead of null) when the current user does not have the required capability. This will preserve the expected return type and prevent the fatal error.

Thank you for identifying this. We’ll include the fix in our next plugin update.

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.

Hi,

Thank you for bringing this to our attention.

We appreciate you taking the time to report this issue. We will review the findings internally to verify the reported behavior and assess the impact.

If the issue is confirmed, we will include the necessary fix in an upcoming ProfileGrid release.

Thank you again for helping us improve the security of ProfileGrid.