typo3

Does anyone have a working example how to extend femanager 3.3.0 on TYPO3 8.7? I created a new Extension which does all the stuff (new database fields for fe_user, TCA, Partials,....). I have the new fields in the femanager plugin and can select them for the frontend. Registering IS WORKING: the new fields are saved in the database. There is a Warning in the Log: Core: Error handler (FE): PHP Warning: Declaration of TOCO3\TocoLedes\Controller\NewController::createAction(TOCO3\TocoLedes\Domain\Model\User $user) should be compatible with In2code\Femanager\Controller\NewController::createAction

Is it possible to insert a frontend plugin to a page without having a template (and markers) included? Normally I use: 10.marks { CONTENT_LEFT < plugin.tx_xy_p1 } But in a new project I dont want to have a template file where the markers ( ###CONTENT_LEFT### ) are included. The plugin should appear as the only thing on that page. If all you want is the plugin, simply create a sparkingly fresh root template with the standard page object of type PAGE, and insert plugin content there. Create a new page with rootflag etc, and maybe the static files for your plugin, if needed. In the setup field

i'll try to upload a file (or later multiple files) in FE. This works, like my current code. But how can i get a file reference of this file now? /** * * @var array $fileData * @var integer $feUserId * @return \TYPO3\CMS\Extbase\Domain\Model\FileReference */ private function uploadFile($fileData, $feUserId) { $storageRepository = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Resource\\StorageRepository'); $storage = $storageRepository->findByUid(1); # Fileadmin = 1 $saveFolder = $storage->getFolder($this->settings['uploadFolder']); // Datei speichern $fileObject =

what is the correct way to dynamically create new Child Elements in a Fluid Form using JavaScript? Problem: 1:n Relation (Parent/Child) using Extbase ObjectStorages: When the Parent Fluid Form is called it should be possible to add several childs (incl. properties of course!) Dirty, partly working, Solution: I added some JS Code and added the required input elements dynamically. The "xxx" will be interated for each Child. The data will be correctly stored in the DB. <input type="text" placeholder="First Name" name="tx_booking[newBooking][accompanyingperson][xxx][firstname]"> However, if an

I am running realURL 1.12.6 on TYPO3 4.5.26 I am used to realURL creating paths that contain the preVar also for the default language, like www.example.com/de/seite/ and www.example.com/en/page/ In one case, this is just not happening - or I think, only sometimes. In most of the cases, I get www.example.com/seite/ and www.example.com/en/page/ Where can this be changed? PS: Here's the beginning of my realurlconf: $TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT'] = array( 'init' => array( 'enableCHashCache' => 1, 'appendMissingSlash' => 'ifNotFile', 'enableUrlDecodeCache' => 1,

I'm experiencing a strange problem with extbase/fluid extension creation. I use TYPO3 6.1 I've made an extension with a backend module on my dev server (same configuration/hardware then the prod). The module works perfectly with the path to the template : myext/Resources/Private/Backend/Templates myext/Resources/Private/Backend/Layouts myext/Resources/Private/Backend/Partials After this, I downloaded my extension's zip in the ext manager and then installer on the prod server. Now I can't use my extension because the module don't find the templates. I've configured the extension by the same way

Problem: I wrote a conditional VH (extending AbstractConditionViewHelper ) and it works as usually, anyway I realized that in non-cached version it is evaluated only once. Initialy I thought that's my bug, but checked common <f:if> and the problem is identical :S In general when I visit my page for the first time, condition is evaluated and valid result is given, but when I'll refresh the page VH isn't called anymore (checked by setting breakpoint inside the VH) and VH is always treated as FALSE. Only any change in view's code will cause that VH will be evaluated once, and again next refresh