You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although rare sometimes a post can have a parent that itself doesn't have status publish. This might occur under (at least) the following conditions:
You change the post status of a published post with existing children. The children then for now* still has the post as parent.
If you alter the page attributes/parent dropdown to intentionally include e.g. private or draft posts using the page_attributes_dropdown_pages_args and quick_edit_dropdown_pages_args.
* As the page attributes/parent dropdown doesn't list anything but published posts the next time you save any of those children they loose the connection and become a root post themselves. See core issue #8592 for details.
I guess there would need to be some further check to see if the user can see it, but I didn't have time yet to look into that. So leaving this as a hint for now which I hope to revisit later.
The text was updated successfully, but these errors were encountered:
Although rare sometimes a post can have a parent that itself doesn't have status
publish
. This might occur under (at least) the following conditions:You change the post status of a published post with existing children. The children then for now* still has the post as parent.
If you alter the page attributes/parent dropdown to intentionally include e.g.
private
ordraft
posts using thepage_attributes_dropdown_pages_args
andquick_edit_dropdown_pages_args
.* As the page attributes/parent dropdown doesn't list anything but published posts the next time you save any of those children they loose the connection and become a root post themselves. See core issue #8592 for details.
I think the fix could be this:
here:
breadcrumb-trail/inc/breadcrumbs.php
Lines 941 to 946 in cd728c5
What I am a little bit unsure is how to handle
private
:I guess there would need to be some further check to see if the user can see it, but I didn't have time yet to look into that. So leaving this as a hint for now which I hope to revisit later.
The text was updated successfully, but these errors were encountered: