Ticket #21 (closed task: fixed)

Opened 10 months ago

Last modified 4 months ago

Decide if "activeignore" is really needed (and remove it if not)

Reported by: JensLautenbacher Assigned to: martin.leidig@1und1.de
Priority: minor Milestone: 0.13.1
Component: Core (general) Version:
Keywords: Cc:

Description

See config example from #12 and the explanation: For this new configuration suggestion (but also for the current one) we should try to clear the use cases for having the "activeignore" attribute. Is there anything that can't achieved with the help of the policy attribute to the pagerequest (which allows you to select ALL, NONE, or ANY) wrappers as the way to decide if a page is active???

If not, we could a) remove it completely or b) only remove it for the new configuration

Change History

09/01/08 14:58:04 changed by MartinLeidig

  • milestone changed from 0.13.0 to 0.13.1.

09/08/08 15:56:04 changed by MartinLeidig

  • status changed from new to closed.
  • resolution set to fixed.

we still need this feature for Pagers (which should be always active without influencing the page accessibility, otherwise you have to implement the right behaviour within the Pager and you can't share a single Pager class). Nethertheless the naming isn't felicitous. Renamed it to the more concise "checkactive".