Project

General

Profile

Actions
Copy link

Idea #2503

closed

Make it possible to disable/enable "sections"

Added by Phil Hodgson about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Phil Hodgson
Category:
Tapestry structural improv.
Target version:
Testing and Upgrading + PGP.ca features
Start date:
04/07/2014
Due date:
Story points:
-

Description

That is, make it so that Tapestry features can be configured to appear or disappear in the UI. This should include authorization, so that disabled features cannot be accessed even if the URL is known/guessed.

Subtasks 4 (0 open — 4 closed)

Task #2851: Review 2503ResolvedPhil Hodgson04/07/2014Actions
Task #2542: Reference configuration when rendering partials and cellsResolvedPhil Hodgson04/07/2014Actions
Task #2541: Identify "modules" and assign config.yml keysResolvedPhil Hodgson04/07/2014Actions
Task #2543: Reference configuration when authorizing controllersResolvedPhil Hodgson04/07/2014Actions
Actions
Copy link
 #1

Updated by Ward Vandewege about 10 years ago

  • Parent task deleted (#2501)
Actions
Copy link
 #2

Updated by Ward Vandewege about 10 years ago

  • Tracker changed from Task to Idea
Actions
Copy link
 #3

Updated by Phil Hodgson about 10 years ago

  • Subject changed from Make it possible to disable/enable "modules" to Make it possible to disable/enable "sections"

Changing title of issue: Let's call the components of Tapestry we would like to separate "sections": the word "module" is too overloaded for us.

Actions
Copy link
 #4

Updated by Phil Hodgson almost 10 years ago

  • Status changed from New to Resolved

It is now "possible" and a kind of framework for doing it has been developed and merged into master. The story will continue, so to speak, in #2850.

Actions
Copy link

Also available in: Atom PDF