TYPO3 SQL Bug for MySQL 4.1: if you're using MySQL 4.1+ you'll encounter SQL problems (Install tool/Extension Manager). Edit the files “ext_tables.sql” and “ext_tables_static+adt.sql” in your extension directory (ext/pt_conference) and remove the string “DEFAULT '0' NOT NULL “ from all lines containing a field description with “auto_increment”. It's recommended to edit the SQL files before installing the extension! This is not done by default since it may lead to problems using TYPO3 in combination with former versions of MySQL.

Incomplete integration in TYPO3 APIs, e.g. integration of multilingual capabilities, integration of editable style sheets

Text messages/labels are English language only and hardcoded in the source code at this state (see To-Do list)

Product prices are fixed to the product records in the current version. Don't change the price of an already ordered product, or you'll encounter accounting and statistic errors.

Shortcomings in underlying database design and coding (e.g. bindings to fixed UIDs) - we learned from our first implementation and are going to change some things in one of the next versions (see ToDo list)

There's no system check of double booking of tutorials (assuming all tutorials take place on the same day usually). This common sense decision is left to the ordering user. If more than one tutorial is booked, only the first one found is displayed at “Attendee status”.

The VAT ID check [tx_ptconference_pi1::checkVatId()] uses the online XML-RPC interface of the German 'Bundeszentralamt für Steuern (BZSt)' (Federal Tax Office, see http://evatr.bff-online.de/eVatR/xmlrpc/ for more information) via the extension pt_euvatcheck. This means the check can only be used from German companies with a valid own VAT ID (which has to be set in Constant Editor of pt_euvatcheck).