lochmueller / autoloader Goto Github PK

Hey,

I'm getting exceptions for the page module previews, since the ext:autoloader generates automatically the layout files.

#1288092555: Could not load layout file. Tried following paths: "typo3conf/ext/provider/Resources/Private/Layouts/ContentBackend.html", "typo3conf/ext/provider/Resources/Private/Layouts/ContentBackend". (http://typo3.org/go/exception/CMS/debug/1288092555)

TYPO3\CMS\Fluid\View\Exception\InvalidTemplateResourceException thrown in file
/docker/code/typo3_src-6.2.15/typo3/sysext/fluid/Classes/View/StandaloneView.php in line 410.

My actual workaround
Don't using a layout for backend previews. 😢

Do not enter labels in assueLabel mode, if there is no default

Everytime I recreate the file, the exception occurs after actuating "Flush system caches"

#1278155988: The path provided does not point to existing and accessible well-formed XML file. More information
TYPO3\CMS\Core\Localization\Exception\InvalidXmlFileException thrown in file
/docker/code/typo3_src/typo3/sysext/core/Classes/Localization/Parser/AbstractXmlParser.php in line 99.

TYPO3 version: 6.2.15
Autoloader version: 1.9.1

It seems like the problem don't occur when I clear the autoloader cache via TYPO3 backend and all strings for tt_content.content_element_nameand tt_content.content_element_name.description are present.
But I'm surprised that it is now necessary to add this in addition to the newly introduced strings wizard.content_element_name.description, wizard.content_element_name.

What is the purpose of these lines here?
https://github.com/lochmueller/autoloader/blob/master/Classes/Hooks/ClearCache.php#L65-L70

Removing these files can have weird side effects and should be avoided at all costs.

Instead the class loading information should be re-generated if required.
The API for that is pretty simple: https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/extensionmanager/Classes/Command/ExtensionCommandController.php#L95

The extension currently doesn't have a composer.json which makes it impossible to pull e.g. the latest master via Composer, please add one. I'd suggest lochmueller/autoloader as package name. ;-)

[FEATURE] SoapServer classes and WSDL Handling

Use CDATA only in case of same special chars
In the XML and XLF Writer

Error in the BE view

Under TYPO3 Version 8.7.0, start and end time of events become 4 hours less after saving.

If I e.g. enter 00:00 into field "start time", it becomes 20:00 after pressing save.
If I press the save button again, it become 18:00 (2 hours less), next time 16:00 and so on.

The problem also exists at the datetime field "start" under tab "access" of calendar records,
but neither in records of other extensions e.g. news nor in content elements.

I thing the problem stock somewhere inside the IndexPreperationService method prepareRecordForDatabase.
If I e.g. enter 00:00 into start time field and press save, this value becomes 1491422400 inside $record['start_time'], which correspond to 05.04.2017 22:00:00 in local time and 05.04.2017 20:00:00 in utc. Apart of the date this ist exactly the value I see after page reloads.

I thing in general, the value of "start_time" and "end_time" should not be greater than 86400 (because time) at this place. But if I look in the database table "tx_calendarize_domain_model_index", all values are greater, beside some "end_date" values, which I leave empty.
If I look into the database of an other TYPO3 installation, but Version 7.6, all values are smaller than 86400.

After some debugging I found a solution:
Change this in /Classes/Loader/ContentObjects.php line 263:

SpriteManager::addTcaTypeIcon('tt_content', $typeKey, str_replace('../', '', $icon));

to this:

SpriteManager::addTcaTypeIcon('tt_content', $typeKey, str_replace('../typo3/', '', $icon));

May be this path must be different under 7.x. In this case a condition will help.

It would be nice to have a autoloader for locallang/language overrides.

Normally one must add something like this in the ext_localconf.php:

$TYPO3_CONF_VARS['SYS']['locallangXMLOverride']['default']['EXT:foo/Resources/Private/Language/locallang.xlf'][] = 'EXT:bar/Resources/Private/Language/Path/To/Foo/locallang.xlf';

$TYPO3_CONF_VARS['SYS']['locallangXMLOverride']['de']['EXT:foo/Resources/Private/Language/locallang.xlf'][] = 'EXT:bar/Resources/Private/Language/Path/To/Foo/de.locallang.xlf';

I'd suggest that language overrides must be placed in Resources/Private/Language/Overrides/ExtensionName/original/path/to/locallang.xlf.

With this, the loader could deduce the extension name via GeneralUtility::camelCaseToLowerCaseUnderscored() and use the path after Resources/Private/Language/Overrides/ExtensionName/ for the original file path. The language key could be taken from the file prefix of XLIFF files. Examples:

• Resources/Private/Language/Overrides/FooBar/mod1/locallang_mod.xlf yields
  $TYPO3_CONF_VARS['SYS']['locallangXMLOverride']['default']['EXT:foo_bar/mod1/locallang_mod.xlf'][] = 'EXT:my_extension/Resources/Private/Language/Overrides/FooBar/mod1/locallang_mod.xlf';
• Resources/Private/Language/Overrides/FooBar/mod1/de.locallang_mod.xlf yields
  $TYPO3_CONF_VARS['SYS']['locallangXMLOverride']['de']['EXT:foo_bar/mod1/locallang_mod.xlf'][] = 'EXT:my_extension/Resources/Private/Language/Overrides/FooBar/mod1/de.locallang_mod.xlf';
• Resources/Private/Language/Overrides/Qux/Resources/Private/Language/locallang.xlf yields
  $TYPO3_CONF_VARS['SYS']['locallangXMLOverride']['de']['EXT:qux/Resources/Private/Language/locallang.xlf'][] = 'EXT:my_extension/Resources/Private/Language/Overrides/Qux/Resources/Private/Language/locallang.xlf';

It could be argued that the last example is unnecessarily verbose but it should be this way for consistency. If at one point in the future every extension sticks to Resources/Private/Language, this could be simplified a lot.

I don't know why, but if I use the content object functionality of autoloader with the 6.2.14 version of TYPO3, I got this SQL-Error in Front- and Backend.

After some debugging, I notice that inside the dynamic generated typoscript from autoloader the last "t" of "tt_content" is missing.

If I look in Classes/Loader/ContentObjects.php at line 345, everything looks good for me.

config.tx_extbase.persistence.classes.' . $config['modelClass'] . '.mapping.tableName = tt_content');

But if I look at the generated typoscript, it looks like this:

config.tx_extbase.persistence.classes.VENDOR\ExtKey\Domain\Model\Content\MyContent.mapping.tableName = tt_conten

Adding a linebreak at the end of Classes/Loader/ContentObjects.php line 345 solve this problem:

config.tx_extbase.persistence.classes.' . $config['modelClass'] . '.mapping.tableName = tt_content
');

is there an option/configuration to adapt the path(S) for partials and/or templates for Content Objects?

Hi Tim

Thank you for your work and this very useful extension!

I stumbled yesterday upon a problem with the translation of FAL records. I've created the content object with the following annotation:

@var \TYPO3\CMS\Extbase\Domain\Model\FileReference

The TCA part:

'tx_xyz_image' => array( 'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig('image', array( 'appearance' => array( 'createNewRelationLinkTitle' => 'LLL:EXT:cms/locallang_ttc.xlf:images.addFileReference' ), 'foreign_types' => array( 2 => array( 'showitem' => '--palette--;LLL:EXT:lang/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette, --palette--;;filePalette' ) ), 'minitems' => 0, 'maxitems' => 1, ), $GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']), ),

Maybe i miss something, but i get always the image object from the record from default language.

Thank you.

Best,
René

<a:be.editLink /> didn't work in 6-2.

Actually the provider extension icon is taken as icon for the list within the CType selectbox when editing tt_content record.

In the NCEW the own icon is used (which is present under ext:providerextension/Resources/Public/Icons/Content/FooBar.svg)

These two options are no longer present in TYPO3 >= 7.6

• noIconsBelowSelect
• foreign_table_loadIcons

They are replaced by showIconTable

To fix this properly we need to check whether we use 6.2 or not.

Links:

• https://docs.typo3.org/typo3cms/TCAReference/7.6/Reference/Columns/Select/#showicontable
• https://docs.typo3.org/typo3cms/TCAReference/6.2/Reference/Columns/Select/#noiconsbelowselect

Is it possible to wrap the whole PluginNameBackend.html with an anchor to edit the element?

We often have troubles with the autoloader cache after deploying new features or after updating the TYPO3 core. The TCA modifications by autoloader aren't loaded and we have to manually clear the autoloader cache.

Is it possible - from your view - to only check if you are an TYPO3 backend admin. Or maybe something advanced like: If main context is production, and actual user is admin and has set an option to enable the clear cache button.

What do you think Tim? Actually I often has these scenarios. How do you prevent such stuff?

Add language hanlding.

• Create language file
• Add missing labels as dummy

Migrate all classes/loader to "singular" folder names

Instead of manipulating the configuration array here: https://github.com/lochmueller/autoloader/blob/master/ext_localconf.php#L28

The API method should be used
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::registerAjaxHandler

This avoids potential CSRF issues with the Ajax calls

Hey Tim,

I wrote you already directly in slack. I couldn't figure out why there is the check if css_styled_content is loaded in ext:autoloader/Classes/Hooks/ElementBackendPreview.php in line 46 -> https://github.com/lochmueller/autoloader/blob/master/Classes/Hooks/ElementBackendPreview.php#L46

With TYPO3 7 css_styled_content isn't a requirement anymore. Therefore this if statement must be removed or extended to check if fluid_styled_content is installed.

2.0.1 does not contain the latest fixes here in master, at least this one is missing: 50b4a0d

Besides that, I am missing the tags for these versions in this repo

Actually there is tt_content.providerextension.header automatically generated but isn't used.

I would suggest to use this for the <optgroup /> as label within the CType selectbox.
So, all content elements of one contentObject provider extensions are grouped together.

Hi,
I'm trying to write a JSON-RPC Server Loader, but I have trouble integrating the Zend/Json/Server Library in your Project under the Contrib directory. I changed the composer.json in Contrib and the did a composer update and a composer dumpautoload -o to have a autoload_classmap.php. But know even the SoapServer is not working anymore. Should I do a Pull-Request? I forked the project under fduarte42/autoloader. Do you have any advice?

Kind regards,

Tito

Hello,
I tried to install autoloader via composer on V 7.6.1 and received the following exception:

[InvalidArgumentException]
Could not find package typo3-ter/autoloader at any version for your minimum-stability (stable). Check the package spelling or your minimum-stability.

Could you give me a feedback, please. Thanks!

Hi,

the icon of content objects is not displayed in the Content/Page overview. Here is an image of the case.

The icon is correctly named and placed - and shown, when I add the content element. In the overview of the content elements, there is added an extra subfolder to the icon link. Here is an example: My Typo3 installation is at http://some.toplevel.domain/some-site/
The generated icon link then is /some-site/some-site/typo3conf/ext/some-extension/Resources/Public/Icons/Content/ContentElement.svg
That is wrong and one subfolder too much.

After an upgrade of typo3_console and focuspoint we are facing a Runtime Notice that's turned into an Exception.

changing this line:

$return = ArrayUtility::mergeRecursiveDistinct($return, $object->getTca($table));

into this:

$tableTca = $object->getTca($table);
$return = ArrayUtility::mergeRecursiveDistinct($return, $tableTca);

does fix it.

• add info about adding icons Resources/Public/Icons/Content/ModelName
• add custom icons to contentObject example extension

I tried to use the autoloader_plugin as an example, but as soon es ein changed the namespaces, it seems that typo3 cannot find the controller anymore. What am I doing wrong?

My extension can be downloaded here: https://dl.dropboxusercontent.com/u/24707107/ohmex.zip

Refix the sorting of the slot registration
Introduced in this pull request: #56

At the moment slots are registered in a more or less random order (order of class files in the Slots folder) and there is no way to explicitly control the order of execution if there are more than one slot for the same signal. It would be nice to have some kind of priorization (e.g. @priority annotation or something like this).

Actually ;;;richtext:rte_transform[flag=rte_enabled|mode=ts_css] isn't added to TCA for fields where I annotate it through PHPDoc Block

<?php

namespace Foo\Ccontent\Domain\Model\Content;

use TYPO3\CMS\Extbase\DomainObject\AbstractEntity;

/**
 * Class TextTeaser
 * @package Foo\Ccontent\Domain\Model\Content
 * @db tt_content
 * @wizardTab common
 */
class TextTeaser extends AbstractEntity
{
    /**
     * @var string
     * @enableRichText
     */
    protected $bodytext;

    /**
     * @return string
     */
    public function getBodytext()
    {
        return $this->bodytext;
    }

    /**
     * @param string $bodytext
     */
    public function setBodytext($bodytext)
    {
        $this->bodytext = $bodytext;
    }
}

It would be nice for new users of the ext to get an overview which prefixes (tt_content, content.element, ...) are for which area in the backend.

When you drop me a short info to every possible, I could write the documentation part with some nice backend screenshots.

I've tried to add a custom palette or an additional field with e.g. \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes('tt_content', 'assets', 'ccontent_homepage_slide', ''); without success.

When checking the TCA with the configuration backend module, no additional field is added.

GridElement Loader

With #19 the LanguageOverride loader was added and should be documented in Documentation/Loader.

What about generating a sample PluginNameBackend.html with all properties (at least for properties with getters) with key and value style?

I tried to install the extension in a TYPO3 6.2 installation. The extension could not be activated since it requires typo3/cms in the composer.json (BTW the same problem with the faqextension).

Sometimes PLUGINNAME and PLUGINNAME.DESCRIPTION is added twice to xlf file when adding new content object.

Hi,

we are currently seeing a problem with classes not being available to the autoloader.

• TYPO3 7.6.5
• composer based install (web-dir is used, see below)
• autoloader is required in composer.json
• custom extension is NOT required in composer.json (we follow monolitic repository approach and
  it is part of our source repo)

  "cms-package-dir": "{$vendor-dir}/typo3/cms",
  "web-dir": "Web/"

So probably the class loaderis somehow "messed up".

Can someone confirm EXT:autoloader is compatible with composer based installs?

I'll dig now to see where it breaks for us and report back here.

Extendable Mapper for different variable types

The documentation currently says the following about the Slots loader:

... So it is possible to connect one slot class with many signals.

However, the code leads to believe that only the first annotation pair is used, thus the following won't work:

class MySlot {
  /**
   * @signalClass \Foo\Bar
   * @signalName mySignal
   * @signalClass \Foo\Qux
   * @signalName mySimilarSignal
   */
  public function doSomething() {}
}

Is this actually supported or could this be supported? In any case a code snippet in Documentation/Loader/Slots would be useful.

E.g.: When your provider extension has been named to ccontent @wizardTab works only with value ccontent.
Possible problem: header = ... isn't generated.

After updating to 1.8.0 my ContentElements show no Label and/or description, when I try to add a ContentElement to a Page. Only the Icon is shown. When I downgrade to 1.7.0 everthing is working again. I tried the example autoloader_contentobject extension, and it also happens there.