How To
| Audiences |
|---|
| End users and general |
| Integrators and site admins |
| Developers |
GetPaid for Plone how-to documentation collection.
End users and general
General Questions
- How to install GetPaid .7.0 (with functional Google Checkout) with Plone 3.1.7
- (standalone rootless install in unprivileged user home directory)
- How to upgrade from GetPaid .3/Plone 3.0.x to GetPaid .6.1/Plone 3.1.2
- (standalone rootless install in unprivileged user home directory)
- How to manage inventory and warehouse information for a product
- GetPaid allows you to manage information about inventory and warehouse location on an object through the extension getpaid.warehouse. This document explains how you can update the information on a particular product.
Integration and Configuration
- How to install GetPaid .7.0 (with functional Google Checkout) with Plone 3.1.7
- (standalone rootless install in unprivileged user home directory)
Integrators and site admins
General Questions
- How to install GetPaid .7.0 (with functional Google Checkout) with Plone 3.1.7
- (standalone rootless install in unprivileged user home directory)
- How to upgrade from GetPaid .3/Plone 3.0.x to GetPaid .6.1/Plone 3.1.2
- (standalone rootless install in unprivileged user home directory)
Integration and Configuration
- How to install GetPaid .7.0 (with functional Google Checkout) with Plone 3.1.7
- (standalone rootless install in unprivileged user home directory)
- 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.
- Creating Content Types That Are Buyable, Shippable or Donations
- In addition to making existing content types buyable, donatable or shippable via the GetPaid setup screens and manually setting that on your content objects, content types can be programmatically set to be buyable. This HowTo provides information for developers to make their content type buyable by default.
Developer Questions
- 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.
- Creating Content Types That Are Buyable, Shippable or Donations
- In addition to making existing content types buyable, donatable or shippable via the GetPaid setup screens and manually setting that on your content objects, content types can be programmatically set to be buyable. This HowTo provides information for developers to make their content type buyable by default.
Developers
General Questions
- How do I install GetPaid in my Plone site?
- Instructions on how to add GetPaid to your existing Plone site.
Integration and Configuration
- How do I install GetPaid in my Plone site?
- Instructions on how to add GetPaid to your existing Plone site.
- 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 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 to tie actions to payments
- A brief explanation on how to tie workflow transitions, mailing, etcetera to a payment happening in getpaid.
- Creating Content Types That Are Buyable, Shippable or Donations
- In addition to making existing content types buyable, donatable or shippable via the GetPaid setup screens and manually setting that on your content objects, content types can be programmatically set to be buyable. This HowTo provides information for developers to make their content type buyable by default.
Developer Questions
- How do I install GetPaid in my Plone site?
- Instructions on how to add GetPaid to your existing Plone site.
- 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 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.
- 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.
- Accessing GetPaid Attributes on Objects
- A quick howto on how to access the GetPaid attributes of an object such as "price" or "product id" programmatically .
- How to tie actions to payments
- A brief explanation on how to tie workflow transitions, mailing, etcetera to a payment happening in getpaid.
- Creating Content Types That Are Buyable, Shippable or Donations
- In addition to making existing content types buyable, donatable or shippable via the GetPaid setup screens and manually setting that on your content objects, content types can be programmatically set to be buyable. This HowTo provides information for developers to make their content type buyable by default.