How To

Audiences
Integrators and site admins
Developers

GetPaid for Plone how-to documentation collection.

Integrators and site admins

How do I enable "buyable" options for Folderish content types?: By default, Folderish content types cannot be made buyable (or donateable, shippable) because it caused some confusion when the default view for a container was another content object. However it is easy to enable using some zcml.
How do I set up buildout for an existing Plone site?: Buildout is a very easy way to set up GetPaid and all its dependencies, and it makes it easy for you to maintain your site with the latest code. Buildout sets up all of the things you need, including an instance.
How do I translate GetPaid into another language?: This Howto provides information on how to make (or update) a translation of the GetPaid interface in a given language using i18n tools.
How to set up SSL for GetPaid: You should use Secure Socket Layer (SSL) for any site with GetPaid installed to provide added security for the site. This document explains how you can set up SSL by adding configurations to Apache and Virtual Host Monster.

How do I enable "buyable" options for Folderish content types?: By default, Folderish content types cannot be made buyable (or donateable, shippable) because it caused some confusion when the default view for a container was another content object. However it is easy to enable using some zcml.
How do I set up buildout for an existing Plone site?: Buildout is a very easy way to set up GetPaid and all its dependencies, and it makes it easy for you to maintain your site with the latest code. Buildout sets up all of the things you need, including an instance.

Best practices for customizing GetPaid: We often get asked: "Is there any preferred approach to allow integrators to implement customizations? For instance, if I want to default the billing/shipping addr country, or reorder the form so that country precedes state, etc." GetPaid leverages the Zope 3 best practices for customization. This document explains more about those.
How do I enable "buyable" options for Folderish content types?: By default, Folderish content types cannot be made buyable (or donateable, shippable) because it caused some confusion when the default view for a container was another content object. However it is easy to enable using some zcml.
How do I set up buildout for an existing Plone site?: Buildout is a very easy way to set up GetPaid and all its dependencies, and it makes it easy for you to maintain your site with the latest code. Buildout sets up all of the things you need, including an instance.
How do I translate GetPaid into another language?: This Howto provides information on how to make (or update) a translation of the GetPaid interface in a given language using i18n tools.

Best practices for customizing GetPaid: We often get asked: "Is there any preferred approach to allow integrators to implement customizations? For instance, if I want to default the billing/shipping addr country, or reorder the form so that country precedes state, etc." GetPaid leverages the Zope 3 best practices for customization. This document explains more about those.
How do I enable "buyable" options for Folderish content types?: By default, Folderish content types cannot be made buyable (or donateable, shippable) because it caused some confusion when the default view for a container was another content object. However it is easy to enable using some zcml.
How do I run tests for GetPaid?: GetPaid contains several tests within its components. This document explains the commands to run those tests. Note: this is required before you check anything in to the svn repository.
How do I set up buildout for an existing Plone site?: Buildout is a very easy way to set up GetPaid and all its dependencies, and it makes it easy for you to maintain your site with the latest code. Buildout sets up all of the things you need, including an instance.