Plugin Support
Kush
(@kushnamdev)
Hey @jalorod,
Thank you for contacting us.
These warnings indicate that the Visualizer plugin is trying to read a CSV file but failing to open it correctly.
To fix this:
- Check if the CSV source configured in the Visualizer chart actually exists and is reachable (whether local or external).
- Ensure the file permissions allow the web server user (usually www-data or apache) to read it.
- If the CSV URL is remote, confirm that the server allows opening remote files (allow_url_fopen = On in php.ini).
- If you’re using a dynamic import (for example, from a Google Sheet or REST URL), test that URL directly in your browser to confirm it’s valid and publicly accessible.
Once the plugin can successfully open the file, both warnings will stop appearing.
I hope this helps, thank you!
Thank you for your reply.
About your questions, in all my charts I entered data manually with plugin (not referencing external csv’s from Google sheet or similar).
All my charts are showing correctly so it is strange that it can’t read the csv’s (caused by permissions os others) as you suggest.
I have changed the code in the plugin about line 290 of file Module.php to include en if() like this one:
if ($fp) { // To avoid warnings in logs when $fp is boolean
while ( ( $array = fgetcsv( $fp ) ) !== false ) {
......
}
}
fclose( $fp );
So it seems that the problem is fixed.
Would you consider to include this change in next versions for avoid the problem (so I can update and don’t change it every time)? And for other people that has this problem.
Thank you,
Hi @jalorod,
Thank you for the detailed update and for sharing your solution!
We’re glad to hear that your change fixed the issue. However, we haven’t been able to replicate this issue on our end, but we’ll review what could have caused it and explore how to prevent these warnings in future releases. Your input is very helpful for improving the plugin.
Let us know if we can help with anything else.
Ok, thank you…only if you can confirm in the moment in which there is a new release that fix it…is a problem for me when updating the plugin (losing my changes) as i said (perhaps to other users too).
Regards,
