Skip to content

Blog isPrivate sometimes incorrectly returns NO #3207

Open
@aerych

Description

@aerych

See #3206 for background. Determine the cause for the isPrivate prop returning the NO when it should be YES and patch this behavior. Once that's done let's switch back to checking isPrivate vs isWpcom.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions