WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #34560, comment 17


Ignore:
Timestamp:
11/04/2015 09:34:30 PM (4 years ago)
Author:
pdfernhout
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34560, comment 17

    initial v1  
    11As a caveat for any fix for this issue, issue #25233 from two years ago says: "Currently WordPress loads all the revisions in order to possibly upgrade them to the 3.6 versioning of revisions. It does so on every post loaded in wp-admin. It might make sense to move this to an upgrade routine or somewhere else as it adds to the performance degradation." That issue mentions other things to consider as well.
    22
    3 I am not sure if that specific concern on upgrading revisions applies here or if data corruption/confusion could be a possibility somehow if that was not done and a very old post was editied. But it seemed worth mentioning in case upgrading all the post revisions was a crucial (but undocumented in the code) side-effect of counting revisions inefficiently in the original editor code?
     3I am not sure if that specific concern on upgrading revisions applies here or if data corruption/confusion could be a possibility somehow if that was not done and a very old post was edited. But it seemed worth mentioning in case upgrading all the post revisions was a crucial (but undocumented in the code) side-effect of counting revisions inefficiently in the original editor code?