Make WordPress Core

Opened 4 weeks ago

Last modified 3 weeks ago

#44236 new defect (bug)

Maintain consistency between privacy export report and archive filenames

Reported by: iandunn Owned by:
Milestone: Awaiting Review Priority: low
Severity: minor Version: 4.9.6
Component: Privacy Keywords: good-first-bug
Focuses: Cc:


Prior to r43180, the export .zip filename changed every time it was regenerated; after that commit, it was reused to ensure links aren't broken (see #43905).

That commit didn't do anything to the .html filename, though, so after the initial regeneration, the value of $obscura will not match between the two filenames. I don't think this presents any issues for Core, and might not for plugins either, but it seems like they should be consistent, just to be safe.

If a plugin hooks into wp_privacy_personal_data_export_file_created, it may reasonably assume that the filenames to match, and do something like str_replace( '.html', '.zip', $foo ). That seems unlikely, since both filenames are passed to the callback, but it's better to be safe than sorry.

Change History (1)

This ticket was mentioned in Slack in #gdpr-compliance by iandunn. View the logs.

3 weeks ago

Note: See TracTickets for help on using tickets.