I’d run in the same issue some days ago. This is how it works for me:
First of all add your configuration file to the Configuration directory of your package. Then create some dummy content in it, just for testing.
If you hadn’t done yet, add Package.php file to “Classes/Vendor/Package/”. This is how mine looks like:
<?php
namespace EntwicklerButze\Ansetzungen;
use \TYPO3\Flow\Package\Package as BasePackage;
use \TYPO3\Flow\Configuration\ConfigurationManager;
use \TYPO3\Flow\Core\Bootstrap;
/**
* The Basepackage
*/
class Package extends BasePackage {
/**
* Invokes custom PHP code directly after the package manager has been initialized.
*
* @param \TYPO3\Flow\Core\Bootstrap $bootstrap The current bootstrap
* @return void
*/
public function boot(Bootstrap $bootstrap) {
// Multi-Client configuration file
///////////////////////////////////////////////////////////////////////////////////////////
$dispatcher = $bootstrap->getSignalSlotDispatcher();
$dispatcher->connect('TYPO3\Flow\Configuration\ConfigurationManager', 'configurationManagerReady',
function (ConfigurationManager $configurationManager) {
$configurationManager->registerConfigurationType(
'Client', // <= name of your configuration file without .yaml
ConfigurationManager::CONFIGURATION_PROCESSING_TYPE_DEFAULT,
TRUE // <= allow suffixes like "Client.Bigcustomer.yaml"
);
}
);
}
}
Within your controller just add a variable with the following annotation: