The PHP Gift Registry is a web-enabled gift registry intended for use among a circle of family members or friends. It is intended to fill the following purposes:
Its features include:
You will require the following software:
I have personally tested this application on Windows 2000, Windows XP, Slackware Linux, Fedora Core 1 and FreeBSD with varying versions of Apache, PHP and MySQL. I have encountered no issues.
Here are some basic instructions to get you going.
A phpgiftreg installation consists of a set of users. Each user is a family member who maintains their own gift list. One or more users are designated as administrators; these users handle approvals of new users and can maintain categories and rankings (described below). When you run the setup script for the phpgiftreg, you will create the first administrator.
Users belong to zero or more families. (A user should always belong to one or more families.) A family is simply a group of users who would be interested in exchanging gifts for each other. For example, if Adam Smith marries Jane Doe, you'd likely have two families defined: the Smiths and the Does. Adam and Jane would probably belong to both families, while Adam's parents and siblings would only belong to the Smith family, and Jane's parents and siblings would only belong to the Doe family. This prevents Adam's second-cousin-twice-removed from seeing Jane's orthodontist, for example. Users can easily be added and removed from families.
Each user maintains a list of users that he/she shops for. All this means is that he can see that user's gift list. Your phpgiftreg installation can be set up to auto-allow shopping requests; otherwise, a user who requests to shop for another user must wait for the recipient to approve the request.
A gift list consists of a set of zero or more items. Each item has a description, an estimated price, a category, a store/retailer where it can be purchased, a ranking, a quantity, a URL where potential buyers can find more information, a comment, and an image. Only the description, price, category, store/retailer, ranking and quantity are mandatory.
Rankings and categories are maintained by the administrator. For the most part, the rankings should be adequate for most users, but the categories can be easily extended.
When a user shops for another user, he/she can reserve or purchase an item. A reservation simply marks the the intention of the buyer to purchase the item. A purchase marks the user as having purchased the item.
When quantities are involved, multiple users can allocate different amounts of reservations and purchases for the same item. For example, Jane Doe can ask for 10 steak knives. Adam's mom can reserve 4 and Jane's friend can purchase 2, leaving 4 available. Once Adam's mom buys the 4 knives, she can convert them to a purchase. If she changes her mind, she can release the reservation, leaving 8 available. Purchases can always be returned, which converts them back to a reservation.
If anonymous purchasing is turned on in the config.php, anybody shopping for another user can see how many of an item are reserved/purchased, but not who did so.
A user who has made multiple reservations/purchases for another user can use the shopping list feature to quickly print off a list of items they have reserved or purchased. This is handy to take to the store, rather than printing off each user's full list.
Once a user receives an item, he/she can mark the item as received, which is different from a deletion in that only the received quantity is debited from their item. If a reserved/purchased item is deleted without being received, a message is privately sent to the reserver/purchaser to inform them that the item is no longer required.
The system also allows the definition of events, which are gift-bearing opportunities, like Christmas and birthdays. Events can be personal or system events. Personal events are events specific to that user, like a birthday or anniversary. System events are events that apply to the entire family, like Christmas or Hanukkah. All events can be marked as recurring, meaning they repeat year after year. Only the administrator can modify system events.
The system also supports messages, which is a basic send/receive system for notifications. Most users should have the option set to automatically e-mail any messages received, provided they have specified a valid e-mail address.