WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36339


Ignore:
Timestamp:
03/25/2016 11:13:13 PM (5 years ago)
Author:
DrewAPicture
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36339

    • Property Summary changed from Possible issue with wp_export() and undefined custom post types to Possible issue with export_wp() and undefined custom post types
  • Ticket #36339 – Description

    initial v1  
    1 While writing the improved docblock for wp_export, I noticed something that may be an issue if an invalid custom post type is supplied. Here is the code:
     1While writing the improved docblock for `export_wp()`, I noticed something that may be an issue if an invalid custom post type is supplied. Here is the code:
    22
    33{{{#!php
     
    1818 
    1919
    20 The two things that occured me are
     20The two things that occurred me are
    21211. If a valid custom post type is supplied but its `can_export` property is `false`, `posts` will be used instead. This is unexpected behaviour. I think it should stop and not export anything.
    22221. if an invalid custom post type is supplied, every post type that has `can_export` set to `true` is used. This is also unexpected behaviour. I think it should stop and not export anything.