Support

Search results for ""

Sorry, no results found. Perhaps you would like to search the documentation?
All Topics
Soapbox

Error when trying to ‘Export as CSV’

I keep receiving the message “Failed – Request failed with status code 500” when trying to export any content as a CSV. Please could you assist?

Thanks!

1 month, 1 week ago
Stefan van den Dungen Gronovius
Developer

Hello,

Thanks for your feedback.
Can you have a look at your error.log file and find the error related to our plugin when using Export?
You can share the log with us by sending it to support@admincolumns.com.

1 month, 1 week ago
Soapbox

Hi Stefan,

Sure I’ve just sent over the log to that email address.

Thanks!

1 month, 1 week ago
Eds Keizer

We have the same issue. It is related to the naming of the CSV.php file. It does not follow guidelines as it should be named Csv.php so it follows Composer/PSR-4 naming.

This is the log at our server (redacted):

PHP message: PHP Warning: include(/www/*****/public/web/app/plugins/admin-columns-pro/vendor/composer/../../classes/Export/Exporter/Csv.php): Failed to open stream: No such file or directory in /www/*****/public/vendor/composer/ClassLoader.php on line 576; PHP message: PHP Warning: include(): Failed opening ‘/www/*****/public/web/app/plugins/admin-columns-pro/vendor/composer/../../classes/Export/Exporter/Csv.php’ for inclusion (include_path=’.:/usr/share/php’) in /www/*****/public/vendor/composer/ClassLoader.php on line 576; PHP message: PHP Fatal error: Uncaught Error: Class “ACP\Export\Exporter\Csv” not found in /www/*****/public/web/app/plugins/admin-columns-pro/classes/Export/Exporter/CsvFactory.php:12

1 week, 6 days ago
Stefan van den Dungen Gronovius
Developer

Thanks for reaching out.

This issue was already fixed on our side some time ago. What you’re experiencing is likely caused by Git not properly registering the filename casing change (from CSV.php to Csv.php), which can happen on case-insensitive filesystems.

To resolve this, please either:
– Remove the file from your repository and re-add it so Git correctly registers the casing change, or
– Re-upload the plugin/package (ZIP) to ensure all files are replaced with the correct casing

This should resolve the autoloading issue with Composer/PSR-4.

Let us know if the issue persists after that.

1 week, 6 days ago
Eds Keizer

Thanks that was indeed the case

1 week, 5 days ago