[TYPO3-english] Re: FE Plugin rendered empty - SOLUTION

[Jennifer Koenig]

With a second pair of eyes lent by a colleage :) I was able to figure out what the problem was and solve it.

1. When you make a FE Plugin according to the steps outlined in "Reliable Extensions with Extbase and Fluid" (Joachim Rau, Sebastian Kurfurst, 2. Edition) - you don't need the Typoscript configuration that I had in fileadmin/templates/ts/setup.ts. So I erased the code I had written under the comment #plugin.

2. The plugin was still rendering empty, so I decided to go back to the Extension Builder where I had created it initially, re-generate it, and then compare any differences in relevant files, to see where the problem had been. After re-generating the extension, the only difference I could find was in ext_tables.php, namely:

OLD:
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
    $_EXTKEY, 'PackageList', 'Travel Packages List'
);

NEW:
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
    $_EXTKEY, 'Packagelist', 'Travel Packages List'
);

In the old file, the plugin name was in UpperCamelCase. In the new file, it isn't.  So, it should be "Packagelist" and not "PackageList".

After deinstalling the original extension and reinstalling it with the changes, and embedding the plugin as a content element in the page, everything worked.

So - watch your cases when naming things in TYPO3. Apparently it's case(over)sensitive.