There’s not a lot to go on here, bit this warning usually indicates there is another plugin writing a header early so other plugins can’t do things like write a cookie. This wouldn’t normally interfere with a CSV import, as it’s not really an error, just a warning.
Can you provide a more detailed descrotion of what you did, and any feedback messages you saw during the import process?
Hi thanks for your reply.
How it can be a warning if it terminated the import process? and shows incomplete import count?
What the solution at your end? If i deactivate all other plugins before import?
Technically, a warning doesn’t stop execution whereas an error would. It may be a precondition to the failure (or not related at all), but the actual failure will be for a different reason because the import doesn’t have anything to do with setting headers.
I would suggest you try changing the “CSV Imports in the Background” setting (plugin settings under the Advanced tab) to see if that helps. Also setting the plugin debugger on will give you a more complete record of what happened during the import.
I am getting this error now:
atabase Error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘WHERE id = 228980’ at line 1
Can you check!
