Is it possible to place a warning regarding this issue on the project page?
This was first reported in June 16, 2016, and a working patch since late July, 2016
Something like:
Warning: There are known issues handling UTF-8 data in 8.x-4.0-alpha1 release where the database export is irreversibly corrupted. Please refer to /sq bracket 2749885 /close sq bracket.
I'd considered this issue as major / critical as many users will use this for their only backup source, and the issue affects any site that potentially contains extended characters.
Even on an English site where the module appeared to work fine, we found over 20% of pages post export were affected in some way with this issue, where special quotes characters were exported as invalid / unknown character, leaving a ? character throughout the content instead of the correct character.
Thanks
Comments
Comment #2
avpadernoI am moving the issue to the appropriate queue.
Comment #3
Anonymous (not verified) commented@kiamlaluno, are you sure this is the right place? We have problem with maintenance project. And goal of the issue is find help outside the project.
Comment #4
avpadernoEditing the project page, which the only way to put a warning on a project page is a task for the maintainers.
Webmasters only edit them in specific cases, such as abandoned projects, or projects that don't follow drupal.org rules; we don't edit project pages to add warnings about bugs.
Comment #5
alan d. commentedIf that is the case / protocol, this is a "Close (Won't fix)", there is already a 6 month old issue within the project.
Since this is potentially being used as the sole backup mechanism for some sites, I'd suggest this is a special use-case worth discussing with other web masters.
If an issue with Drupal 7, this is 1 in 3 sites at risk of data loss; thankfully uptake in 8.x is low, at ~4.5%, or 1 in 20 sites at risk of data loss.
Comment #6
avpaderno