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!

Relationship Graph

[ View Issue ] [ Dependency Graph ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0000579	[In-Portal CMS] Other	task	always	2010-02-15 16:22	2010-07-22 15:06

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

Summary	0000579: Ability to use PerPage, SortBy and Page params from URL Query
Description	We are looking for a way to extend functionality for using PerPage, SortBy and Page params from URL Query. Here is a quick outline of things to do: New Query Params Usage: 1. Tag PageLink will include parameters "page,per_page,sort_by" from request, when available (only pass them, when differ, from default values from unit config of that prefix) 2. Pass main_list="1" to InitList/PrintList of main list on the page (one list per page) 3. When main_list parameter is given, then during list initialization use page,per_page,sort_by from url to initialize list 4. Remove "action" attribute from <form> tags on front-end 5. Events OnSetPage, OnSetPerPage, OnSetSorting* should not add associated with them url parameter (page,per_page,sort_by), when it's value is equals to default value from unit config of main list being used. New Query Params Storage: 1. don't store page,page,sorting in session on Front-End (setting in debug.php) 2. store page,page,sorting in cookie (expiration until browser is closed) in format "<prefix>_var", e.g. "product_page".
Additional Information