In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph

[ View Issue ] [ Relation Graph ] [ Vertical ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0001050	[In-Portal CMS] Data Management	feature request	always	2011-05-04 21:23	2012-07-25 05:33

Reporter	Dmitry	View Status	public
Assigned To	!COMMUNITY
Priority	normal	Resolution	fixed
Status	closed

Summary	0001050: Ability to access Disabled Section with Direct Link
Description	Often these days we need to have an ability to access a disabled Section or Category Item on the Front-end without having it shown in the list among other Enabled Sections or Category Items. There is a beautiful solution that Google Picasa has for this - Direct URL which contains some "key" for authenticating the user and showing him hidden by default content. Example: https://picasaweb.google.com/dandrejev/MaksikGitara?authkey=Gv1sRgCJeZqfiPxL271 I propose we implement the same for Section (later for Category Items). Interface: 1. If Status is Pending or Disabled we show a new "Access with Link" field right after (below) that Status field 2. New "Access with Link" field will have a Check-box (enabled by default) and a Label field (which can be copied) with full URL to that Section. Functionality: 1. We would need to have 2 new DB fields ( in Categories table (and later for Category Items) to store the Status and the Authentication Key. I suggest calling them as AllowAccessWithLink and AuthKey, but I am insisting on these names. 2. Let's use some random Alpha-numeric (case sensitive) algorithms (nothing fancy) to generate (automatically) and save this keys. Keys will NOT change! Suggested length 15-20 chars. 3. One of hard questions is - which of the URLs to show: a. with ModRewrite or without - I believe it should be based on current website settings b. which language - default one for Front-end 4. Need to make sure if In-Portal performs a URL redirect due to forcing the HTML URL when user visits without one we need to keep AuthKey in URL as well.
Additional Information	From technical viewpoint it will be pretty easy to implement: 1. create 2 fields in a Category table: DirectLinkEnabled (Yes/No) and DirectLinkAuthKey 2. when someone enables direct link functionality (on category/section editing page), then: - random alpha-numeric string will be generated and stored in category/section record - link to that page with freshly generated authentication key will be displayed 3. in checkItemStatus method (where check is made to prevent viewing Pending/Disabled categories/sections) also check is authentication key is present in url and it matches one from current category/section record 4. if all matches, then show category/section and don't redirect to "no permission" page as usual in this case

Web Development by Intechnic

In-Portal Open Source CMS