A portlet that allows users to create a list of links on
their homepage.
If link url is for a content item, then the link is based on
id of draft item and so is content managed.
Application includes a load parameter
uk.gov.westsussex.portlet.bookmarks.name which
allows you to specify the name of the portlet type (ie the
name that will appear in the drop down list of types).
The default is 'My Links' because that is what our users
wanted. If the application is loaded with a name you
don't like it can be hacked by changing the value in the
title column of application_types
This package is dependent on patch 1178475 because
the portlet XML is cached until the user edits it and
patch 1181342 because the xsl import is loaded
dynamically.
The caching policy means that if an item is
unpublished, the link remains until the portlet is edited
or the server restarted. However when the portlet is in
edit mode, the broken link is highlighted, as the editor
form is not cached. The alternative would be to not
cache the portlet xml, as checking the status of all
items to see if the portlet is dirty would probably take
about the same time as regenerating the XML. A
possible improvement would be to allow the caching
policy to be configurable.
On the subject of XSL, you will probably want to amend
the stylesheet as it is not great (neither xslt or html are
my strong points)
There is scope for improvement if anyone has the time
and inclination
a facility to re-order the links would be useful, and not
too much work to add some up & down arrows next to
each link on the editor.
the option to include access checks on rendered links
would mean the homepage administrator could put links
on the page confident that only permitted users see the
links. However, this would alter the caching policy xml
would need to be cached by portlet id and current user,
and all cached versions would need to be invalidated on
editing
Chris.........
Logged In: YES
user_id=1069385
Don't use this yet - I discovered a problem when regression
testing. The pdl in this version prevents articles with related
links from being published/unpublished.
I have a new version which uses the sort key in the
related_links table rather than having a separate sort key.
The new version includes an upgrade script to move any
existing portlets to the new data model.
I haven't submitted the new version yet, as I may have
time/funding to include the facility to order and edit
bookmarks (basically ripping off the cms related link ui). I will
submit the fixed version after that change as it will be much
more useful then
Logged In: YES
user_id=1069385
Okay - this is the final version, which includes the 2
improvements suggested above. If permission checking is
switched on, no portlet xml is cached.
Reordering is based on the related links ui in the content
centre, but with a bug fixed
Chris....
Final version