SooBahkDo on "[Plugin: Newsletter] Import Process Fails When Import Files Contain Accented Characters And Fails Dif"

Hello,

Just changed over to Newsletter from MailPoet and it looks promising; however, the issue I am reporting was identified after multiple import files failed in different manners.

When troubleshooting this issue I tried creating the CSV import files using Excel on Windows 10 and Excel on Windows XP and a text editor Notepad++ and all import files exhibited the same results.

I also tried changing the delimiter used in the export files and encountered the same results.

I followed the tip on the import page about breaking up import files into smaller files in case server resources were being exceeded even though we run a private server with 64 gigs of ram and it is highly customized to handle very resource intensive tasks.

Eventually, through a very tedious process of splitting up import files containing thousands of records into many different smaller files I was able to identify the individual records causing the import process to fail.

Depending on the accented characters in the import files, the import process fails differently as indicated below:

1) The import procedure fails when the accented character é is present in a file and this failure generates ERR_CONTENT_DECODING_FAILED

2) The import procedure also fails (but differently) when the accented character ë OR ` is present in an import file and this failure results in a BLANK ADMIN PAGE (the navy blue background color) after the import procedure completes rather than the results page which normally appears upon completion of the import process.

I recreated each failure indicated above repeatedly by trying to import a files containing the accented characters and the results were the same each time.

The import procedure works very nicely as long as no accented characters are present in the import files.

I request that you consider improving the import process to accommodate accented characters without failing.

Perhaps at minimum and to prevent the entire import from failing, the process can skip records containing accented characters and mark those records as FAILED OR it can be coded to properly handle imports containing accented characters.

As a user I was chasing all kind of possible causes for the import failures and wasted an entire day due to this issue.

Now I am taking even more time to report it hoping for an update with a fix.

This seems a strange issue to be happening with a Newsletter plugin that is supposed to accommodate translations.

We are running a WP 4.5.2 Multisite Network with Newsletter and most Newsletter extensions active on 5 sites.

We are using SendGrid.

The site where this issue occurs is also running WPML Multilingual plugin.

I look forward to a fix.

Please advise if you require any additional information.

Thanks
Phil D

https://wordpress.org/plugins/newsletter/