--Changes--

1.31 to 1.32
(Oct 23, 2001 - changes by Danny Adair: danny@adair.net)

-- the following fixes have been applied in order to make EventFolder Zope 2.4.x compatible

-- fixed several issues concerning cataloging.
   CatalogAware is no longer a base class of EventDocument, EventDocDates and EventDocumentAddendum.
   Instead, cataloging and uncataloging is done "manually" by the product itself.

-- Added a new Management screen for "Updates, Reviews, Dates" and put the old manage_main on a new tab "Manage"
   (Since managing the dates and addenda of an event had been done through the ZMI and CatalogAware was dropped, the cataloging/uncataloging wouldn't be executed automatically.)

1.2a to 1.3
 
-- fixed some bugs

-- removed Renderable Product from installation requirements
   implies need to do <dtml-with efname><dtml-var index_html></dtml-with>
   
-- Fixed bug where EF folder as object manager had no allowable subobject types:
   it used to be correct? Now allows Event Docs and DTML methods.
   
-- Added Upcoming Events DTML method forwarded by John Puster. Thanx

1.2 to 1.2a (14 June 2001)

-- add 'moderated' tag line under calendar display

-- fixed bug that prevented 'Year' display from working properly.-- add 'moderated' tag line under calendar display


1.1 to 1.2 (13 June 2001)

--  minor fix to fix problem where Title bar of calendar display won't change

   Changed the title of /Control_Panel/Products/EventFolder/EventFolder/propertysheets/methods/index_html 
   to a blank string and use the instance property 'prefix' to set the title. 


--  Added 'outerTable' property.  If this exists (i.e., is not an empty string) then
    certain outer table elements will be left out. Works better with CMF and also
	a way to deal with $#^%# buggy  NS 4.x - some versions hang with nested tables.




1.01 to 1.1 (6 June 2001)

-- In Control_Panel/Products/EventFolder: to fix import/export problems

   In 'EventFolder_factory' in the Add list name field: removed the space between Event and Folder
   so it shows EventFolder rather than Event Folder
   
   In 'EventDocument_factory' in the Add list name field: changed it to EventDoc.


-- Changes to rendercal.py to clean up generated HTML.

-- Changes to various ZClass methods to clean up HTML and adjust proxy roles, etc. to 
   work correctly inside the CMF.
   
-- General minor cleanups.




1.0 to 1.01

-- Compatible with 2.2.1 beta 1 and up

-- added Ownership tab to EventFolder instances

-- added highlight to current date in the calendar display

-- fixed some inconsistencies in the architecture that made search
   give wrong answers from time-to-time. Specifically, changed name
   of the body text attribute of an EvDocAdder (an update/review item)
   to a different name than that of the body text attr of an event.

-- added facility to choose to search updates and reviews as well
   as just events.  
   
-- minor cleanups to look & feel.

-- added a ZClass-dtml method in EventFolder/EventFolder called 
   thismonth_titlesonly.  This will build a list of events in the
   current month, which can be neat to display next to the
   calendar or on a home page.  See that method for an example
   of how to use this ability or check it out on www.ptang.com.


0.9 to 1.0

EventFolder 1.0 is compatible with Zope 2.2 beta 1 and higher. If you
are using an Zope 2.1.6 you need to use EventFolder 0.9. It won't
work correctly with Zope 2.2.0

-- Search will now look in both the title and text_content (the body
of the posting) fields for a match.  It should correctly throw out
duplicates (the same word appears in both title and body).  A maximum
# of search results property has been added.  Since the search is
done across two indices (title & text_content), it's held in memory
so it was felt that a limit would be prudent.  Actually, all that's
held in memory is a list of object refs rather than the so-called
'pluggable brains' so not all that much memory is used anyway.  But
I digress...

-- Added a 'now' link to return you to the current month.

--added an optional (defaults on) feature that checks the text of a posting
for illegal HTML.  This is handy for 2 reasons:

1. We check for the <dtml>, which certainly should not be in a posting. Naughty, naughty....
2. Things such as <head> will confuse the client browser and potentially disrupt the
    looknfeel of a site.

These are the disallowed tags (can be changed in validateform.py)

head, html, meta, base, dtml, applet, area, bgsound,body,form,
button, embed, frame, frameset, iframe, input, layer, link,
script, select, style, textarea, title


