WordPress.org

Make WordPress Core

Opened 16 months ago

Last modified 16 months ago

#20114 new defect (bug)

Posts and Pages w. private visibility don't show up in existing content

Reported by: heinrichgeps Owned by:
Priority: normal Milestone: Awaiting Review
Component: Editor Version: 3.3.1
Severity: major Keywords: has-patch
Cc: ng@…

Description

when inserting or editing a link in the editor (post or page) pages & posts with private visibility don't show up in the "existing content" section of the "insert/edit link" popup. All pages/posts with public visibility are shown. This doesn't make sense as I have all necessary privileges to see and edit these private pages/post. Even the admin doesn't see the private pages. Very annoying.

Attachments (1)

20114.diff (1.3 KB) - added by soulseekah 16 months ago.

Download all attachments as: .zip

Change History (5)

comment:1 heinrichgeps16 months ago

  • Severity changed from normal to major

soulseekah16 months ago

comment:2 soulseekah16 months ago

Remember that links to private content that a visitor has no access to will result in a 404. http://codex.wordpress.org/Content_Visibility#Private_Content
This is especially true for crawlers, you will get 404 even though your content exists for you.

For possible non-core-based solutions to this refer to:

The attached diff shows private posts in the lists. Patch will not work on 3.3.1, since many things have been moved around in that area.

JS would require proper localization for the word "Private" if this enhancement/defect is considered. If not, use HTML links.

comment:3 soulseekah16 months ago

  • Keywords has-patch added; needs-patch removed

comment:4 heinrichgeps16 months ago

The patch works flawless on 3.3.1.

Remember: there are situations where you have only a few pages / posts that are visible to the public and the main content is visible only to subscribers (we love privacy in germany!). It is very annoying not to be able to use the internal link tool. The 404 problem is very well documented with many possible solutions (you pointed to the most important ones).

Ergo: I'd highly propose the implementation of this patch.

Note: See TracTickets for help on using tickets.