Currently article titles ( stubs ) are not links, they are headings that have click handlers bound to them. In order to provide bookmarking capability to articles, a system of query strings must be implemented, such that when a title is bookmarked, upon following the link, the forum should note the query string, redirect to login if necessary, and process the query string once the user is on the forum. Should be possible to handle this by utilizing the session variable.
When clicking the stub normally, the link should not redirect as this would destroy the user cache ( and perhaps break normal function of the site ). Therefore article stubs should provide a bookmarkable link but also prevent default and channel the action through the socket as is done now.
Links should follow these specifications:
text should be the full title with html ( as is displayed in the stub )
href should be the forum url followed by "?" and the query string
query string should consist of category=<id> and optionally topic=<id> joined with &, OR chat=<id>
chat id should be validated by participation with an error message if the user is not permitted to view the chat
category id's and topic id's should be validated
optional topic id defaults to null
query string should be validated in entirely based on 3
Currently article titles ( stubs ) are not links, they are headings that have click handlers bound to them. In order to provide bookmarking capability to articles, a system of query strings must be implemented, such that when a title is bookmarked, upon following the link, the forum should note the query string, redirect to login if necessary, and process the query string once the user is on the forum. Should be possible to handle this by utilizing the session variable.
When clicking the stub normally, the link should not redirect as this would destroy the user cache ( and perhaps break normal function of the site ). Therefore article stubs should provide a bookmarkable link but also prevent default and channel the action through the socket as is done now.
Links should follow these specifications:
category=<id>and optionallytopic=<id>joined with&, ORchat=<id>null