justinianch

I was able to fix this on my AWS Lightsail/bitnami instance.

1. Bitnami uses a symlink (/opt/bitnami/wordpress → /bitnami/wordpress)
2. The Events Calendar 6.16.4 added a path traversal security check that uses realpath() to resolve symlinks
3. WordPress’s wp_upload_dir() returns the symlinked path
4. The two paths never matched so every CSV was rejected with the misleading invalid-csv-file error

The fix — setting WP_CONTENT_DIR and WP_CONTENT_URL in wp-config.php — forces WordPress to use the real path, so they match.

This is what I added to wp-config.php:
define( ‘WP_CONTENT_DIR’, ‘/bitnami/wordpress/wp-content’ );
define( ‘WP_CONTENT_URL’, ‘https://www.SITENAME.com/wp-content’ );