Project

General

Profile

Actions
Copy link

Feature #52114

open

Expand "do not search" to subpages

Added by d.ros no-lastname-given over 10 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Should have
Assignee:
Mathias Schreiber
Category:
Backend User Interface
Target version:
-
Start date:
2013-09-18
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The do not search function in page settings is a quite useful thing. Especially if you want to hide pages from search and googlesitemap xml rendering.

But there´s one thing that makes it quite unhandy on large pagetrees. You cannot expand it to child pages. You can go with the list module, but even this is much efford if you want to hide 200 pages.

An equivalent usage to the access function would be a great benefit from an editors POV.

Cheers

David

Files

12.png (2.71 KB) 12.png d.ros no-lastname-given, 2013-09-20 14:17
Actions
Copy link
 #1

Updated by Georg Ringer over 10 years ago

  • Status changed from New to Needs Feedback

using addRootLineFields for the field is no option?

Actions
Copy link
 #2

Updated by d.ros no-lastname-given over 10 years ago

It´s more a question of what an editor can expect. To me it would feel a kind of natural that this behaviour works there out of the box.

Cheers

Actions
Copy link
 #3

Updated by Georg Ringer over 10 years ago

IMO this really depends on the usecase. there can be also pages at an entry level which should not be searchable but the pages within should...

as an integrator you can quite easily change that to be passed to the children

Actions
Copy link
 #4

Updated by d.ros no-lastname-given over 10 years ago

Of course you are right.

It was only an idea how to integrate something useful into the GUI.

See attached image.

Feel free to close or wait for other opinions.

Cheers

David

Actions
Copy link
 #5

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to New
Actions
Copy link
 #6

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber
I can imagine such a field.
But I think it should work a bit differently - more like login-mode.
Here's my proposal:
  • Add a dropdown "search-mode"
    • Include in Search (default), value 0
    • Include in Search including Subpages, value 2
    • Exclude in Search, value 1
    • Exclude including Subpages, value 3

Feedback highly welcome :)

Actions
Copy link
 #7

Updated by d.ros no-lastname-given over 9 years ago

Check. +1
BTW: "Include in Search including Subpages, value 2" seems to me obsolete.

Actions
Copy link
 #8

Updated by Mathias Schreiber over 9 years ago

d.ros no-lastname-given wrote:

Check. +1
BTW: "Include in Search including Subpages, value 2" seems to me obsolete.

Imagine this:

Page 1
  - Page 2 (disabled incl. subpages)
    - Page 3
      - Page 4 (enabled incl. subpages)
        - Page 5

I think you might need a way to enable including subpages "again" in case a tree above it disabled that.
Or am I thinking in circles here?

Actions
Copy link
 #9

Updated by d.ros no-lastname-given over 9 years ago

You are right.

BTW: Shouldn't be default "inherit" instead of "include in search" from treelevel1 ?

Just for UX consistence? So there's no question about it.

Actions
Copy link
 #10

Updated by Mathias Schreiber over 9 years ago

d.ros no-lastname-given wrote:

BTW: Shouldn't be default "inherit" instead of "include in search" from treelevel1 ?

jup, that makes sense.

Actions
Copy link
 #11

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to New
Actions
Copy link

Also available in: Atom PDF