Geändert
* Query für die Tskliste im CC auf gestartete Workflows beschränkt
* Automatisches Starten eines Workflows beim Resetten verhindert, würde es eh' für den Publisher starten, nicht für die Autoren
* Link zum Starten des Workflows wird nun auch im Zustand INIT angezeigt
Wenn das Löschen des Workflows beim Publizieren per Config-Parameter com.arsdigita.cms.delete_workflow_after_publication abgeschalted wurde, sollte das Verhalten nun dem erwarteten entsprechen.
Fehlt
* Publizieren ist noch nicht vom WF abhängig
git-svn-id: https://svn.libreccm.org/ccm/trunk@2296 8810af33-2d31-482b-a856-94f89814c4df
- removed dependencies from ~/sitenode/SiteNodeRequestContext
- refactored ContentCenterServlet to use clean new style application code
- removed dispatcher base code from ContentCenter main page
- refactored root index.jsp to check for logged in user and redirect tu user page
- added permission check to ContentCenterServlet and removed content-center redirect.jsp
- removed old package dependen admin / sitemap application
- added various documentation and improved formatting
git-svn-id: https://svn.libreccm.org/ccm/trunk@2047 8810af33-2d31-482b-a856-94f89814c4df
- Automatische Benachrichtung des Admins, wenn das publizieren eines Content-Items fehlschlägt (Ticket #1192)
git-svn-id: https://svn.libreccm.org/ccm/trunk@1592 8810af33-2d31-482b-a856-94f89814c4df
- nicht mehr benötigte Klassen (nicht erfolgreicher Ansatz für Publizieren von Assoziationen) enfernt
git-svn-id: https://svn.libreccm.org/ccm/trunk@1577 8810af33-2d31-482b-a856-94f89814c4df
- Der eigentliche Vorgang wird jetzt nebenläufig durchgeführt
- Solange der Vorgang noch läuft wird eine entsprechende Meldung angezeigt
git-svn-id: https://svn.libreccm.org/ccm/trunk@1352 8810af33-2d31-482b-a856-94f89814c4df
r1795: First part of the conversion of CCM to be deployed in a standard way
r1796: Multilanguage categorization (already local, but upgrade script
added, comments and translation added)
First part of the conversion of CCM / APLAWS to be deployed in a standard way
by a *.war file.
Backwards compatible to the procedures so far. The ccm scripts can be used
as used to. Only difference is the location of some files (see below).
As an alternative the webapps directory created by the ccm scripts can be
moved into a standard tomcat container or can be added as a virtual host.
APLAWS no longer depends on all the environment variables. For detailed
instructions see documentation on the WIKI. This is a temporary solution,
further enhancements are on the way!
No update script required for this part.
Modifications:
- Creation of a c.ad.runtime.CCMResourceManager class, which currently
handles just the file locations. It replaces the dependency from the
CCM_HOME environment variable. It is initialized during startup of the
servlet container or by the entry point of the installation tools (i.e.
c.ad.packaging.mastertool). It replaces the c.ad.packaging.CCM class
as well. Currently contains backwards compatibility code to check the
runtime environment just in case the initialization is missing (will be
removed later).
- Creation of c.ad.web.CCMApplicationContextListener class which is
notified by the servlet container at the beginning of the startup procedure.
Initialises CCMResourceManager. Must be configured by web.xml (if a contributed
package overwrites the trunk values)!
- File location changes:
- Configuration registry moved to [appbase]/WEB-INF/conf/registry
- ps2fs files moved to [appbase]/ps2fs
(can be modified by configuration parameter)
- lucene index files moved to [appbase]/WEB-INF/work/lucene
(can be modified by configuration parameter)
Developers watch out! ant clean now removes these files, too (esp. registry)!
- XML factory classes are now determined by configuration parameters
- waf.xml.xsl_transformer=[saxon (default)|jd.xslt|resin|xalan|xsltc]
- waf.xml.dom_builder=[xerces (default) | resin]
- waf.xml.sax_parser=[xerces (default) | resin]
- Package c.ad.packaging reorganized so it contains just installation
related code. Runtime configuration related code moved to c.ad.runtime.
Code is not part of the API.
- log4j configuration file is still at the old location, but is not used
anymore! It will be moved to [appbase]/WEB-INF/conf/ in the future.
Developers, modify the file ~/webapps/WEB-INF//classes/log4j.properties
in the meantime.
- While working on the code some deprecated classes and method invocations
replaced by supported API. If a class is no longer used by any module in
trunk, the class has been removed by appending "nolongerInUse" to the file
name. If any of the contributed modules is still depending on deprecated code
it is easy to find and to follow the recommended replacement instructions. Do
not re-incorporate deprecated code! We have to clean up the code base!
Second part: Multilanguage categories
Added update script
Translation of some comments, added comments
version number bumped to reflect the major changes
git-svn-id: https://svn.libreccm.org/ccm/trunk@73 8810af33-2d31-482b-a856-94f89814c4df
r1637 | chrisg23 | 2007-09-17 12:14:27 +0200 (Mo, 17 Sep 2007)
Sourceforge patch 1796099 - allow URL Generators to be registered for specific content types.
Requires upgrade script to be run: ccm-run ccm-cms --from-version 6.5.2 --to-version 6.5.3!
------------------------------------------------------------------------
r1638 | chrisg23 | 2007-09-17 13:48:34 +0200 (Mo, 17 Sep 2007)
Sourceforge patch 1796156 - allow notes to be shown on basic properties authoring step
------------------------------------------------------------------------
r1639 | chrisg23 | 2007-09-17 15:20:13 +0200 (Mo, 17 Sep 2007)
Sourceforge patch 1781131 - workaround to bypass query filtering bug if permission filtering folder contents
------------------------------------------------------------------------
r1641 | chrisg23 | 2007-09-17 15:46:27 +0200 (Mo, 17 Sep 2007) | 1 line
Geänderte Pfade:
M /trunk/ccm-core/src/com/arsdigita/notification/Notification.java
Sourceforge patch 1714842 - if message delete has been specified for a notification, only delete it when the last
referring notification is deleted (several notification records may refer to the same message)
------------------------------------------------------------------------
r1642 | chrisg23 | 2007-09-17 16:05:26 +0200 (Mo, 17 Sep 2007) | 1 line
Sourceforge patch 1727634 - retain specified ordering when paging through folder contents (previously every time you changed to a new page it reverted to default name ordering)
------------------------------------------------------------------------
r1643 | chrisg23 | 2007-09-17 16:19:06 +0200 (Mo, 17 Sep 2007) | 1 line
Sourceforge patch 1783195 - IMPORTANT BUGFIX - if you use fixed length lifecycles with expiry notifications then you are probably affected by this - notifications are not created and sent if you have relied on the default end date set by the lifecycle, only if you explicitly entered a date on the publish form. To fix the timebomb of items that are due to expire without notification, there is a command line program in package uk.gov.westsussex.wsgfl.jobs called CreateMissingNotificationPhases. Package is in ccm-wsx-wsgfl-custom module in contrib area of the repository. To use this, it is best to copy the job class and the accompanying pdl file query-missing-notification-phases to your own custom application, or else install ccm-wsx-wsgfl-custom but strip away everything except those 2 files and the initialiser - removing all bits of the initialiser except the data init. Do not add ccm-wsx-wsgfl-custom to your instance as it is, at it overrides some files in the default Aplaws installation
git-svn-id: https://svn.libreccm.org/ccm/trunk@13 8810af33-2d31-482b-a856-94f89814c4df
SVN-Version 1.0.5 Rev 1603 + alle meine Änderungen
- Navigation (Adaptive Mode)
- Paginator angeglichen
- Paginator <NoContent> -Tag eingeführt
- manipulate-input.js erweitert für deutsche Umlaute (erste Version)
und vielleicht noch ein paar andere Dinge...
git-svn-id: https://svn.libreccm.org/ccm/trunk@1 8810af33-2d31-482b-a856-94f89814c4df
quasi
pb
jensp