So i started thinking of a database structure that will enable me to accomplish this. As i started to research i also posted a question on stackoverflow to see what others had in mind.

The design

After a bit of thought i came up with this design.

Design Details

Products have an id_configuration
A configurable products actually is a collection of products witch have the same id_configuration (witch is auto-generated).

Features linked to products
Rather then categories, which seems more naturally to me. This enables me to easily move products between categories.

Product features values is stored in the link table
I decided to store the feature value for a product in the link table. This helps with more simple queries and also it means that you don’t have to insert all the options in the feature options table (think of features that have different values for all products)

Name and Label for features
The name is used internally in the admin section and Label is used in the site front-end. This is useful for features with same name. Ex: Size for clothes, size for hardisks etc.

Filterable flag on features
A Yes/No flag that shows witch filters are filtrable.

Examples of use

Selecting products
The most important thing is how do we select products, and how do we only show one product for the configurable ones. For this we use GROUP BY.

SELECT * FROM `products`
GROUP BY CASE `products`.`configurable` WHEN 'yes' THEN `products`.`id_configuration` ELSE `products`.`id` END


Filtering products
The bellow example shows the query for a single filter/feature (with id 38) and 2 values selected:

SELECT * FROM `products`
WHERE `id` IN (SELECT id_product FROM `product-features` WHERE `id_feature` = 38 AND `value` IN ('Test value', 'New Value') GROUP BY id_product HAVING COUNT(*) >= 1)
GROUP BY CASE `products`.`configurable` WHEN 'yes' THEN `products`.`id_configuration` ELSE `products`.`id` END


Get active filters
After you have a list of filter products you will want to print out a list of filters that are applicable to this list, since not all are available to the current selected products.

SELECT `id_feature` FROM `product-features`
WHERE `id_product` IN (SELECT `id` FROM `products` WHERE ___YOUR_CONDITIONS____) GROUP BY `id_feature`

Notice that i left out the GROUP BY from the product subselect.

Associate count of products for a filter
Its very useful to show the count of products for a certain value of a filter. The bellow query is how you can select that count for one filter.

SELECT *, COUNT(*) AS `count` FROM (
SELECT *
FROM `product-features`
WHERE
`id_product` IN (SELECT `id` FROM `products` WHERE ___YOUR_CONDITIONS____) AND
`id_feature` = 36
) AS `tbl` GROUP BY `value`

Notice that i left out the GROUP BY from the product subselect.

Conclusions

I think this database model works best for what i wanted and it has all the flexibility i needed:
- it allows for any 2 products to group as configurable
- you can add promotions and separate images for each variation
- have separate stocks on each variation (witch make more sense to me)
- get sales report cumulate or separate on each variation.

Hope you like this approach and i await you comments on it.

svn attempt to write a readonly database
commit failed

Although if i looked at the repo the commited files were there.

After hunting Google a bit, I found the problem to be with the “/svn/repopath/db/rep-cache.db” file that did not have write permissions for the user subversion uses.
After fixing permissions, committing went perfectly with no errors.

Hope it helps.

So add this to your hosts:
174.36.30.71 www.dropbox.com

Hope it works for you.

The project can be found here:
http://code.google.com/p/php-adwords-api/

It is still a work in progress and does not yet support all the services and functions of the API, but we hope to add more services as soon as possible. And if you need a certain service or function please dont hesitate to add a ticket on google code and request it.

You will find examples of usage in the folder examples of the library.

Generating print-ready well-formatted PDF documents with PHP is not an easy task. Traditionally, there are two main approaches to PDF generation with PHP. Given sufficient time and patience, both partially get the job done, but still leave a lot to be desired:

HTML-to-PDF: This approach is widely used in mainstream applications. Here an HTML document is programmatically created and converted to a PDF, using one of the many open source libraries ¹. Since HTML, however, is not a page-oriented format (as is PDF), it is impossible to perform a 1-to-1 mapping between HTML and PDF. Typical word processing file format features, such as header and footers, orphans and widows or even page numbers can simply not be represented in HTML.

Table of contents

• A completely new approach
• Introducing LiveDocx
• Templates and documents
• Using LiveDocx
  • Creating a template in Microsoft® Word 2007
  • Assigning scalar data types in LiveDocx
  • Assigning compound data types in LiveDocx
  • Generating image files with LiveDocx
• Deploying LiveDocx in your own applications
• Learn more
  • LiveDocx in PHP 5
  • LiveDocx SOAP service
• Footnotes

Programmatic: This approach offers total control of the resulting PDF. However, it requires that the x and y coordinates of every line of text, every geometrical shape and graphic be set from program code ². Not only is this an extremely time-consuming solution, but is also very brittle: Every time a graphical designer changes the layout of a document, a programmer must re-work his or her program code.

A completely new approach

In this article, the author presents an entirely new, third approach. It relies on templates being created in a WYSIWYG environment, such as Microsoft® Word or Open Office, and then being populated with data in PHP. The resulting document can be saved not only to PDF, but also DOCX, DOC and RTF.

Before we delve into a technical discussion on the inner workings of this new approach, let us first take a look at a practical example. The following PHP 5 code illustrates PDF generation, in which the merge fields software, licensee and company in the template template.docx [46.7 KB] are populated with scalar data in PHP. The resulting document document.pdf [104.7 KB] is created and written to disk.

The code demonstrated in this article will be shipped with the Zend Framework 1.10 when it becomes available. Although at the time of writing, there is no official release date, 1.10 is expected to release in Q4 2009. In the meantime, you can check the components out of the Standard Incubator SVN repository.

Introducing LiveDocx

LiveDocx is a SOAP-based document generation service, based on the market-leading, word processing component TX Text Control .NET. LiveDocx allows word processing templates to be populated in any programming language that supports SOAP. The resulting document can be saved to any supported format. This article, however, concentrates on using LiveDocx in PHP 5.

The components of the Zend Framework implementation of LiveDocx are located at /Zend/Service/LiveDocx/ in the standard Zend Framework distribution file. It is possible to use LiveDocx directly with the PHP 5 SoapClient, without the Zend Framework, and with the third party library NuSOAP. The NuSOAP approach even allows LiveDocx to be used in PHP 4. This article, however, concentrates on the official Zend Framework components in PHP 5.

Templates and documents

Throughout this article, we refer to the terms templates and documents. It is important to understand the difference between the two.

Templates: The term template is used to refer to the input file, containing formatting and text fields. Templates can be in any one of the following file formats:

• DOCX - Office Open XML Format
• DOC - Microsoft® Word DOC Format
• RTF - Rich Text Format
• TXD - TX Text Control® Format

Templates can be stored either locally on the client machine (the one from which the SOAP request is initiated) or remotely on the backend server. The decision on which one you should use depends upon the kind of application you are developing.

If you store the templates locally, you have to transfer the template together with the data that should be populated on every request. In the case that the template remains the same on every request, this approach is very inefficient. It would be better to upload the template to the backend server once and then reference it on all subsequent requests. This way, only the data that should be populated is transfered from the client to the backend server. Most applications, using LiveDocx fall into this category.

On the other hand, if you have a template that is constantly changing, or an application in which you enable end-users to upload templates, you may consider storing templates locally and transfer them every request. This approach, is obviously slower, as every request contains the template itself, in addition to the data to populate it.

Documents: The term document is used to refer to the generated output file that contains the template file, populated with data - i.e. the finished document. Documents can be saved in any one of the following file formats:

• DOCX - Office Open XML Format
• DOC - Microsoft® Word DOC Format
• HTML - XHTML 1.0 Transitional Format
• RTF - Rich Text Format
• PDF - Acrobat® Portable Document Format
• TXD - TX Text Control Format
• TXT - ANSI Plain Text

In addition to the above word processing file formats, documents can also be saved to the following image file formats:

• BMP - Bitmap Image Format
• GIF - Graphics Interchange Format
• JPG - Joint Photographic Experts Group Format
• PNG - Portable Network Graphics Format
• TIFF - Tagged Image File Format
• WMF - Windows Meta File Format

Using LiveDocx

In this section, we are going to look at the entire process of creating a document using LiveDocx from scratch.

Creating a template in Microsoft® Word 2007

The first step in any LiveDocx project is the creation of a template. To do this, you can use either Open Office or Microsoft® Word. For the purpose of this article, we are going to use Microsoft® Word 2007. For instructions on using Open Office, please take a look at the LiveDocx Blog.

Start off by creating a new file in Microsoft® Word 2007 and save the template file as template.docx.

You can then start to compose the template, inserting text, graphics and merge fields with the Field dialog box, shown to the right.

After a while, you will have a template, which contains images, text and a number of merge fields. The merge fields are represented by { MERGEFIELD name } and will be populated with scalar data in the next step. The follow screenshot of the template in Microsoft® Word 2007 illustrates how your template may look:

Save the template template.docx [46 KB] when you are done.

Assigning scalar data types in LiveDocx

Now that we have the template file, the next step is to populate it with data. In the following example, we are going to assign scalar data types - in this case strings - to the template.

For many applications, in particular those in which PDF files are used of archiving purposes, you may wish to set the meta data of the PDF file. You can do this, by specifying an associative array with the meta data that should be embedded into the PDF file. The setDocumentProperties() method must be called before createDocument():

The resulting document document.pdf [104 KB] is written to disk and can now be opened in your favorite PDF reader, such as the shipped Document Viewer in Ubuntu:

Assigning compound data types in LiveDocx

In addition to the scalar data types, which were assigned to the template in the previous example, you can also assign compound data types, such as an associative array. Consider the template template.doc [20.5 KB] and the resulting document document.pdf [77.6 KB]. In particular, take a look at the following section of the template (click to enlarge):

The section of the template between the bookmarks

and is repeated in the final document to produce rows of a table. One sub-array of the following associate array is used for each row.

Using the following PHP 5 code, we are going to populate the template with an associative array of telephone connection data. For clarity, this example shows only the part in which an associative array is assigned. The instantiation of LiveDocx and the document creation and retrievable processes are identical to the previous examples and have been omitted:

The resulting document contains the following table with the data from the assigned associate array (click to zoom):

Generating image files with LiveDocx

In addition to the word processing file formats listed above that are supported by LiveDocx, you can also save the resulting documents as one or more image files. For this purpose, Zend_Service_LiveDocx_MailMerge offers the methods getAllBitmaps() and getBitmaps():

Similarly, it is possible to retrieve images for pages in a specific range:

Note that zoomFactor parameter. This is a per cent value, in the range of 10% to 400%. These methods are ideally suited to generating thumbnail images of the created document, for example, to display in the browser as a preview.

The actual image files can be written to disk by iterating through the $bitmaps array. There is one page of binary data per record in the array:

Deploying LiveDocx in your own applications

The code, which constitutes the PHP 5 implementation of LiveDocx, shipped in the Zend Framework, is released under the New BSD license and thus may be deployed, modified and redistributed in most projects, according to that terms of the license. The actual LiveDocx SOAP server, however, is proprietary software. There are three ways in which the SOAP service can be deployed in your own applications.

1. Free public server
   For the vast majority of applications, developers choose this approach. The default LiveDocx server that is referenced in the Zend Framework components is the free public server. It may be used in your own applications completely free of charge. Sign up for a LiveDocx account.
2. Premium hosted server
   In the case that your application generates several thousand documents per hour, you may consider paying a small monthly fee to have access to your own personal LiveDocx server. In association with leading hosting providers, you can rent such a premium hosted server.
3. Local licensed server
   In the case that your application generates more than about ten thousand documents her hour, you may consider installing a LiveDocx server in your local network. Having direct access in a local gigabit network is by far the fastest way of deploying LiveDocx.

Learn more

This article has scratched the surface of what you can do with LiveDocx. If you would like to learn more about this new powerful document generation platform, please take a look at the following resources:

LiveDocx in PHP 5

• phpLiveDocx blog.
• phpLiveDocx technical articles.