The autoloader takes care of finding classes in TYPO3. It is closely related to \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance() which takes care of singleton and XCLASS handling.

As a developer you should always instantiate classes either through \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance() or with the Extbase \TYPO3\CMS\Extbase\Object\ObjectManager> (which internally uses makeInstance() again).

TYPO3 6.2 was still delivered with a couple of different autoloaders, that all had different approaches and rules to find a class. This led to the naming conventions in and outside Extbase and the optional ext_autoload.php file to load classes that didn’t follow the conventions. Since TYPO3 7.0 all this is gone and there is only a single autoloader left, the one of composer. No matter if you run TYPO3 in composer mode or not, TYPO3 uses the composer autoloader to resolve all class file locations. However, the autoloader is a little bit more sophisticated in composer mode as it then supports PSR-4 autoloading.

This means, you did not install TYPO3 via a require-statement inside your composer.json. It’s a regular old-school install where the TYPO3 source and the symlinks (typo3/index.php) are setup manually. In this case, every time you install an extension, the autoloader scans the whole extension directory for classes. No matter if they follow any convention at all. There is just one rule. Put each class into its own file. The generated classmap is a huge array with a mapping of classnames to their location on the disk.

Example:

<?php

$typo3InstallDir = \TYPO3\CMS\Core\Core\Environment::getPublicPath(); return array( 'Schnitzler\\Templavoila\\Clipboard\\Clipboard' =>$typo3InstallDir . 'typo3conf/ext/templavoila/Classes/Clipboard/Clipboard.php',
'tx_templavoila_pi1' => $typo3InstallDir . 'typo3conf/ext/templavoila/Compatibility/class.tx_templavoila_pi1.php', ... );  This method is failsafe unless the autoload information cannot be written. In this case, check the Install Tool for warnings and make sure that typo3temp is writable. Troubleshooting: If your classes cannot be found, try the following approaches. • Dump the class loading information manually with the following command: php typo3/cli_dispatch.phpsh extbase extension:dumpclassloadinginformation • If that command itself fails, please (manually) uninstall the extension and simply try reinstalling it (via the Extension Manager). • If you are still not lucky, the issue is definitely on your side and you should double check the write permissions on typo3temp. Loading Classes With Composer Mode¶ In composer mode, the autoloader checks for (classmap and PSR-4) autoloading information inside your extensions’ composer.json. If you do not provide any information, the autoloader falls back to the classmap autoloading like in non composer mode. Troubleshooting: • Dump the class loading information manually via composer dumpautoload and check that the autoload information is updated. Typically you would check vendor/composer to hold files like autoload_classmap.php and autoload_psr4.php etc. Example: $ tree vendor/composer
.

• If you didn’t do so before, have a look at the PSR-4 standard. It defines very good rules for naming classes and the files they reside in. Really, read the specs and start using PSR-4 in your projects. It’s unlikely that there will be any other more advanced standard in the near future in the PHP world. PSR-4 is the way to go and you should embrace it.
• Even if you do not use composer mode and the class mapping of the autoloader allows you to use whatever you want, stick to PSR-4. It’s not only a very good standard to find classes, but it will also help organizing your code.
• PSR-4 is all about namespaces. No matter if you like namespaces or not, use them. Namespaces exist since PHP 5.3, so you will be able to use them in any modern TYPO3 project due to the minimum PHP requirements of TYPO3 itself.