[lqfb-main] LiquidFeedback Frontend 2.0.3 released
Philipp von Klitzing
philipp at vklitzing.com
Mon Aug 13 10:15:51 UTC 2012
> Today the Public Software Group  released LiquidFeedback
> Frontend 2.0.3, the third service release for the frontend of
> LiquidFeedback 2.0.
> - Italian translation
> - Traditional chinese translation
> - Dutch translation
> - Update of Greek translation
1. As I assume that not in every LQFB installation nicknames will be
permitted I would like to suggest to add the following to the help
"member.settings.name-no-nick.[de].txt[.html]" texts, so that they can
receive translation in the future. Combine this with a corresponding
configuration switch in example.lua.
Enter your real name. <b>Nick names are not permitted</b>, and result in
either correction by the administrator or blocking/deletion of this
Wähle einen Namen, d.h. Deinen Realnamen. <b>Spitznamen sind nicht
erlaubt</b> und fuehren entweder zur Korrektur durch den Admin, oder zur
Sperrung/Loeschung dieses Kontos. [...]
2. Likewise I would like to suggest to include the option for an external
link in the initial help text (the one seen after the signup/first logon,
"index.index.[en].txt[.html]") to be able to point to a tutorial, a dummy
guide or the like.
> - Improved example config
3. Suggestion: Include an "email signature" configuration setting in
example.lua (named "config.mail_signature") and attach that at the bottom
of each notification message (see member.lua):
4. By the way, the first "Hello" in model/member.lua is missing a "!"
behind it, and after the second "Hello" followed by "<user>," the next
line starting with "Please" needs to have a lower case "please" instead.
> - Improved unit editing in admin backend
5. With a larger list of units (I have around 250-300 sub-units) the
"member" part of the admin web UI is messy to use: The units (that the
member can be member of) are shown in arbitrary order and not sorted at
all (neither by unit hirarchy, nor by alphabet).
6. The "vote now" link has a too low visbility in the UI, and it needs to
be clicked several times to finally arrive at the voting screen.
Moreover, the resulting page that is reached after the first click on
"vote now" is overwhelming and confusing. Need to fast-track this part.
More information about the Main