Products.FacultyStaffDirectory 3.1.1

Provides content types for creating and organizing personnel directories within educational institutions
Products.FacultyStaffDirectory is a personnel directory, a provider of shared workspaces for committees, a way of keeping track of people's areas of expertise, a floor wax, and a dessert topping. It integrates with Plone's users and groups infrastructure and supports an extensibility framework for custom requirements.

Installation:

FacultyStaffDirectory 3 requires Plone 3.3 or greater.

 1. Add the following to buildout.cfg

[buildout]
eggs =
. . .(other eggs). . .
 Products.FacultyStaffDirectory


 2. Re-run buildout (typically 'bin/buildout').
 3. Restart Zope (typically 'bin/instance restart').
 4. Install the FacultyStaffDirectory product using portal_quickinstaller or the Plone Add/Remove Products tool under Site Setup. The necessary dependencies will install themselves automatically. (Membrane remains in the 'available' column, but is in fact installed.)

last updated on:
March 29th, 2012, 20:29 GMT
price:
FREE!
developed by:
WebLion Group, Penn State University
homepage:
weblion.psu.edu
license type:
GPL (GNU General Public License) 
category:
ROOT \ Internet \ Plone Extensions

FREE!

In a hurry? Add it to your Download Basket!

user rating

UNRATED
0.0/5
 

0/5

Rate it!
What's New in This Release:
  • Added a sample-content profile. [pumazi]
  • fsd_atoz_view and department_textual_view should now work on Department objects living outside the FacultyStaffDirectory root on a site. Warning: external Departments will only work reliably for situations where there is a single FacultyStaffDirectory object in a site. If there are multiple FacultyStaffDirectory objects, then use of external Departments will have undefined behavior. [cah190]
  • Fixes to author.cpt to support Plone 4.x. Thanks to Paul Roeland for reporting this problem and supplying a patch. [cah190]
  • Fixed fsd_atoz_view to work with last names having first characters outside the A to Z range. We now allow for any valid unicode character. Thanks to Toni Haka-Risku for reporting this problem and supplying a patch which served as a starting point for this fix. [cah190]
read full changelog

Add your review!

SUBMIT