Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#51361 closed defect (bug) (fixed)

Provide documentation to indicate changes to wp_privacy_exports_url require moving files to avoid breaking existing exports

Reported by: garrett-eclipse's profile garrett-eclipse Owned by: garrett-eclipse's profile garrett-eclipse
Milestone: 5.6 Priority: normal
Severity: normal Version: 5.5
Component: Privacy Keywords: has-patch
Focuses: docs, administration Cc:

Description

This is a follow-up of #44038 which was committed in 5.5 as [48127] and [48330]. That ticket updated the handling of privacy export paths making them relative and using the wp_privacy_exports_url(). This function provides the wp_privacy_exports_url which allows admins to customize the location of their exports. As of the commits changing this location via the filter will break any existing exports unless they're migrated to the new directory location. As such this ticket strives to educate this via the filters through a new since phpdoc (patch coming).

Note: This is a potential candidate for 5.5.2 but for now I'll milestone for the next major.

Attachments (1)

51361.diff (844 bytes) - added by garrett-eclipse 4 years ago.
Added @since docs to the exports dir/url filters to indicate changes should be reflected on the server to avoid breaking existing requests.

Download all attachments as: .zip

Change History (2)

@garrett-eclipse
4 years ago

Added @since docs to the exports dir/url filters to indicate changes should be reflected on the server to avoid breaking existing requests.

#1 @SergeyBiryukov
4 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 49042:

Docs: Add a @since note to wp_privacy_exports_dir and wp_privacy_exports_url filters about exports using relative paths since WordPress 5.5.

When changing exports location via these filters, make sure to migrate the files to the new directory, to avoid breaking any existing exports.

Follow-up to [48127], [48330].

Props garrett-eclipse.
Fixes #51361.

Note: See TracTickets for help on using tickets.