Red Hat Bugzilla – Bug 794359
Add a function to completely hide a page using check-box and date-control
Last modified: 2018-01-29 20:42:03 EST
++ This bug is a clone of bug 794358 ++ Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007pmle&sfdc.override=1 project_key: JBEPP A platform JIRA for GTNPORTAL-2295 [Add a function to completely hide a page using check-box and date-control] As mentioned in GTNPORTAL-2033/JBEPP-1096, "Visible" and "Publication date" are effective only for Navigation. Pages are still accessible via direct URL access, such as http://localhost:8080/portal/private/classic/pagename GTNPORTAL-2033/JBEPP-1096 is for a documentation fix because it is an expected behaviour and the document should mention the limitation. This JIRA is raised for a feature request to implement the function to completely hide a page from users. It may be going to add some capability to "Visible" and "Publication date" feature.
Link: Added: This issue relates to JBEPP-1096
Link: Added: This issue incorporates GTNPORTAL-2295
Labels: Added: EPP_6_0_0_Candidate
*** Bug 794358 has been marked as a duplicate of this bug. ***
Ok, so, there's a proposed implementation on https://github.com/jpkrohling/gatein-portal/compare/BZ794359-HidePageIfPublicationDateInFuture-Take2 This proposal adds a new checkbox to the set of fields related to the publishing date, named "". When this checkbox is marked and the current time is outside of the window of the publication date (ie: before the start publication date, or after the end publication date), an user that knows the URL of this page will be redirected to the parent node. Additionally, a message will be shown to the user, saying that the page is not available yet (or has expired). There's no change in the current behavior, as in, nodes marked as "not visible" will still be available for users knowing the URL, as well as nodes which are not published. This is to prevent problems with backwards compatibility, ie, administrators today might be taking advantage of this "bug" (for instance, when they don't want a page to show up in a navigation, but the page is linked from inside a document). I'm attaching a few screenshots, to demonstrate the change. If this is an acceptable solution, the code will be merged once it gets reviewed.
Created attachment 853092 [details] Form - New field - Access restricted before publishing date
Created attachment 853094 [details] Page - Access restricted before publishing date
Created attachment 853095 [details] Form - New field - Access allowed before publishing date
Created attachment 853098 [details] Page - Access allowed before publishing date
Created attachment 853099 [details] Form - New field - Access restricted after publishing date
Created attachment 853101 [details] Page - Access restricted after publishing date
Created attachment 853102 [details] Form - New field - Access allowed after publishing date
Created attachment 853103 [details] Page - Access allowed after publishing date
Status: the feature is being discussed on gatein-dev . Next steps: get a code review done, send pull-request, get it merged into master.
Pull Request sent: https://github.com/gatein/gatein-portal/pull/788
The above PR was merged in upstream.
(In reply to Juraci Paixao Krohling from comment #8) > Ok, so, there's a proposed implementation on > https://github.com/jpkrohling/gatein-portal/compare/BZ794359- > HidePageIfPublicationDateInFuture-Take2 > > This proposal adds a new checkbox to the set of fields related to the > publishing date, named "". > > When this checkbox is marked and the current time is outside of the window > of the publication date (ie: before the start publication date, or after the > end publication date), an user that knows the URL of this page will be > redirected to the parent node. Additionally, a message will be shown to the > user, saying that the page is not available yet (or has expired). > > There's no change in the current behavior, as in, nodes marked as "not > visible" will still be available for users knowing the URL, as well as nodes > which are not published. This is to prevent problems with backwards > compatibility, ie, administrators today might be taking advantage of this > "bug" (for instance, when they don't want a page to show up in a navigation, > but the page is linked from inside a document). > > I'm attaching a few screenshots, to demonstrate the change. If this is an > acceptable solution, the code will be merged once it gets reviewed. Thanks for the description there, Juca. I've made the changes in the User Guide here: http://docbuilder.usersys.redhat.com/22545/remarks/#Adding_a_new_Page_using_Page_Creation_Wizard Search for "BZ#794359" to find the changes relating to this ticket. I need to get a new, blank screenshot for the procedure. Asking for test portals in sme-portal for this, or I'll just spin up an ER build of 6.2 to get the screen.