Search results

Products.CMFPhotoAlbum-0.5.0-2.lbn19.noarch

A Plone-based photograph album

Products.CMFPhotoAlbum-0.5.0-2.lbn25.noarch

A Plone-based photograph album

Products.CMFPlacefulWorkflow-1.5.10-1.lbn13.noarch

Overview ======== Placeful Workflow is a Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site: 1. When you access the root of your site, you will see a new action in the workflow state drop-down menu called "policy". Click on the "policy" link. 2. The next page will let you add a policy to your folder by clicking on the "Add Workflow policy" link. Click on "Add Workflow policy". 3. Now you have a workflow policy in your site, and you can set the workflow policies for this folder and below. We didn't add any workflow policies, so you don't have a choice of different workflow policies yet, so the default workflow policy will be taken both for the folder and below. Usage ===== Now, let's define a new workflow policy: 1. Access "Site Setup" and click on "Placeful Workflow" in the "Add-on Product Configuration" section. 2. Enter the name "my_policy" in the "New policy" field, and click on "add". 3. Now you have a new policy. Enter the title "Example policy" and the description "This is an example policy". 4. Change the workflow for the content type "Folder" from "folder_workflow" to plone_workflow", and click on "Save". Now all your content types should use the "plone_workflow". Let's test the new workflow policy for "Folders" at the root of our site: 1. At the root of the site, select the "Policy" link in the workflow state drop-down menu. 2. Select "Example policy" for "In this Folder" and "Below this Folder" and click "Save". 3. Then, let's add a Folder to see whether the new workflow policy is active. Go to the root of your site and select "Folder" from the "Add new item" drop-down list. Enter the id "myfolder", the title "My folder" and the description "This is my folder", and click on "Save". 4. Now, when you access the "State" drop-down list, you will see that you have the possibility to "submit" the folder. The submit transition only exists in the "plone_workflow", and is absent from the "folder_workflow", which demonstrates that the workflow policy we have chosen is used for the "Folder" content type. Let's go one step further and add a new folder inside of "My folder". After having added the new folder, you should also find the "Submit" transition available. Now it would be interesting to change the workflow policy setting in the Plone site. Let's first change the workflow policy for "Below this Folder" to "Default Policy". You will find that the second folder does not more have the "submit" transition. You can add an additional workflow policy in the first folder, which assigns the "My policy" for "In this Folder", so the second folder will once again have the "submit" transition. Additional tools ================ The Placeful Workflow tool (portal_placeful_workflow) is installed by the installer. It provides a few configuration options so that you use to create you workflow policies through the ZMI.

Products.CMFPlacefulWorkflow-1.7.3-1.lbn25.noarch

Overview ======== Placeful Workflow is a Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site: 1. When you access the root of your site, you will see a new action in the workflow state drop-down menu called "policy". Click on the "policy" link. 2. The next page will let you add a policy to your folder by clicking on the "Add Workflow policy" link. Click on "Add Workflow policy". 3. Now you have a workflow policy in your site, and you can set the workflow policies for this folder and below. We didn't add any workflow policies, so you don't have a choice of different workflow policies yet, so the default workflow policy will be taken both for the folder and below. Usage ===== Now, let's define a new workflow policy: 1. Access "Site Setup" and click on "Placeful Workflow" in the "Add-on Product Configuration" section. 2. Enter the name "my_policy" in the "New policy" field, and click on "add". 3. Now you have a new policy. Enter the title "Example policy" and the description "This is an example policy". 4. Change the workflow for the content type "Folder" from "folder_workflow" to plone_workflow", and click on "Save". Now all your content types should use the "plone_workflow". Let's test the new workflow policy for "Folders" at the root of our site: 1. At the root of the site, select the "Policy" link in the workflow state drop-down menu. 2. Select "Example policy" for "In this Folder" and "Below this Folder" and click "Save". 3. Then, let's add a Folder to see whether the new workflow policy is active. Go to the root of your site and select "Folder" from the "Add new item" drop-down list. Enter the id "myfolder", the title "My folder" and the description "This is my folder", and click on "Save". 4. Now, when you access the "State" drop-down list, you will see that you have the possibility to "submit" the folder. The submit transition only exists in the "plone_workflow", and is absent from the "folder_workflow", which demonstrates that the workflow policy we have chosen is used for the "Folder" content type. Let's go one step further and add a new folder inside of "My folder". After having added the new folder, you should also find the "Submit" transition available. Now it would be interesting to change the workflow policy setting in the Plone site. Let's first change the workflow policy for "Below this Folder" to "Default Policy". You will find that the second folder does not more have the "submit" transition. You can add an additional workflow policy in the first folder, which assigns the "My policy" for "In this Folder", so the second folder will once again have the "submit" transition. Additional tools ================ The Placeful Workflow tool (portal_placeful_workflow) is installed by the installer. It provides a few configuration options so that you use to create you workflow policies through the ZMI.

Products.CMFPlacefulWorkflow-1.7.3-1.lbn25.noarch

Overview ======== Placeful Workflow is a Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site: 1. When you access the root of your site, you will see a new action in the workflow state drop-down menu called "policy". Click on the "policy" link. 2. The next page will let you add a policy to your folder by clicking on the "Add Workflow policy" link. Click on "Add Workflow policy". 3. Now you have a workflow policy in your site, and you can set the workflow policies for this folder and below. We didn't add any workflow policies, so you don't have a choice of different workflow policies yet, so the default workflow policy will be taken both for the folder and below. Usage ===== Now, let's define a new workflow policy: 1. Access "Site Setup" and click on "Placeful Workflow" in the "Add-on Product Configuration" section. 2. Enter the name "my_policy" in the "New policy" field, and click on "add". 3. Now you have a new policy. Enter the title "Example policy" and the description "This is an example policy". 4. Change the workflow for the content type "Folder" from "folder_workflow" to plone_workflow", and click on "Save". Now all your content types should use the "plone_workflow". Let's test the new workflow policy for "Folders" at the root of our site: 1. At the root of the site, select the "Policy" link in the workflow state drop-down menu. 2. Select "Example policy" for "In this Folder" and "Below this Folder" and click "Save". 3. Then, let's add a Folder to see whether the new workflow policy is active. Go to the root of your site and select "Folder" from the "Add new item" drop-down list. Enter the id "myfolder", the title "My folder" and the description "This is my folder", and click on "Save". 4. Now, when you access the "State" drop-down list, you will see that you have the possibility to "submit" the folder. The submit transition only exists in the "plone_workflow", and is absent from the "folder_workflow", which demonstrates that the workflow policy we have chosen is used for the "Folder" content type. Let's go one step further and add a new folder inside of "My folder". After having added the new folder, you should also find the "Submit" transition available. Now it would be interesting to change the workflow policy setting in the Plone site. Let's first change the workflow policy for "Below this Folder" to "Default Policy". You will find that the second folder does not more have the "submit" transition. You can add an additional workflow policy in the first folder, which assigns the "My policy" for "In this Folder", so the second folder will once again have the "submit" transition. Additional tools ================ The Placeful Workflow tool (portal_placeful_workflow) is installed by the installer. It provides a few configuration options so that you use to create you workflow policies through the ZMI.

Products.CMFPlone-4.3.3-1.lbn13.noarch

Plone is a user friendly Content Management System running on top of Python, Zope and the CMF. It benefits from all features of Zope/CMF such as: RDBMS integration, Python extensions, Object Oriented Database, Web configurable workflow, pluggable membership and authentication, Undos, Form validation, amongst many many other features. Available protocols: FTP, XMLRPC, HTTP and WEBDAV Turn it into a distributed application system by installing ZEO. Plone shares some of the qualities of Livelink, Interwoven and Documentum. It aims to be the open source out-of-the-box publishing system. What is Plone? Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. * Plone is easy to install. You can install Plone with a a click and run installer, and have a content management system running on your computer in just a few minutes. * Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content. * Plone is international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content. * Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C's AAA rating for accessibility. * Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product. * Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support. * Plone is extensible. There is a multitude of add-on products for Plone to add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages. * Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD. Technical overview Plone is a content management framework that works hand-in-hand and sits on top of Zope, a widely-used Open Source web application server and development system. To use Plone, you don't need to learn anything about Zope; to develop new Plone content types, a small amount of Zope knowledge is helpful, and it is covered in the documentation. Zope itself is written in Python, an easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Zope and Plone work. By default, Plone stores its contents in Zope's built in transactional object database, the ZODB. There are products and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.

Products.CMFPlone-4.3.20-1.lbn19.noarch

Plone is a user friendly Content Management System running on top of Python, Zope and the CMF. It benefits from all features of Zope/CMF such as: RDBMS integration, Python extensions, Object Oriented Database, Web configurable workflow, pluggable membership and authentication, Undos, Form validation, amongst many many other features. Available protocols: FTP, XMLRPC, HTTP and WEBDAV Turn it into a distributed application system by installing ZEO. Plone shares some of the qualities of Livelink, Interwoven and Documentum. It aims to be the open source out-of-the-box publishing system. What is Plone? Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. * Plone is easy to install. You can install Plone with a a click and run installer, and have a content management system running on your computer in just a few minutes. * Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content. * Plone is international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content. * Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C's AAA rating for accessibility. * Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product. * Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support. * Plone is extensible. There is a multitude of add-on products for Plone to add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages. * Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD. Technical overview Plone is a content management framework that works hand-in-hand and sits on top of Zope, a widely-used Open Source web application server and development system. To use Plone, you don't need to learn anything about Zope; to develop new Plone content types, a small amount of Zope knowledge is helpful, and it is covered in the documentation. Zope itself is written in Python, an easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Zope and Plone work. By default, Plone stores its contents in Zope's built in transactional object database, the ZODB. There are products and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.

Products.CMFPlone-4.3.20-1.lbn25.noarch

Plone is a user friendly Content Management System running on top of Python, Zope and the CMF. It benefits from all features of Zope/CMF such as: RDBMS integration, Python extensions, Object Oriented Database, Web configurable workflow, pluggable membership and authentication, Undos, Form validation, amongst many many other features. Available protocols: FTP, XMLRPC, HTTP and WEBDAV Turn it into a distributed application system by installing ZEO. Plone shares some of the qualities of Livelink, Interwoven and Documentum. It aims to be the open source out-of-the-box publishing system. What is Plone? Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. * Plone is easy to install. You can install Plone with a a click and run installer, and have a content management system running on your computer in just a few minutes. * Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content. * Plone is international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content. * Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C's AAA rating for accessibility. * Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product. * Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support. * Plone is extensible. There is a multitude of add-on products for Plone to add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages. * Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD. Technical overview Plone is a content management framework that works hand-in-hand and sits on top of Zope, a widely-used Open Source web application server and development system. To use Plone, you don't need to learn anything about Zope; to develop new Plone content types, a small amount of Zope knowledge is helpful, and it is covered in the documentation. Zope itself is written in Python, an easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Zope and Plone work. By default, Plone stores its contents in Zope's built in transactional object database, the ZODB. There are products and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.

Products.CMFQuestions-0.5.2-8.lbn13.noarch

CMFQuestions is a simple product written to collect data from people - feedback on a course, simple data collection etc. Has support for multiple choice and free answer questions.

Products.CMFQuestions-0.5.2-9.lbn19.noarch

CMFQuestions is a simple product written to collect data from people - feedback on a course, simple data collection etc. Has support for multiple choice and free answer questions.