TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-04T11:36:29ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103264 (Resolved): Add Google conversion param ?gad_sourcehttp://forge.typo3.org/issues/1032642024-03-04T11:36:29ZJonas Eberlejonas.eberle@aero.de
<p>Google now calls ?gad ?gad_source:</p>
<p><a class="external" href="https://support.google.com/google-ads/answer/13327296">https://support.google.com/google-ads/answer/13327296</a></p>
<p>It would be cool to ship it with TYPO3 in the $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['excludedParameters'] array.</p>
<p>(typo3/sysext/core/Configuration/DefaultConfiguration.php)</p> TYPO3 Core - Bug #102315 (Resolved): FLUIDTEMPLATE: extbase.controllerExtensionName does not allo...http://forge.typo3.org/issues/1023152023-11-03T16:49:13ZJonas Eberlejonas.eberle@aero.de
<p>As mentioned in the docs, configuring <code>extbase.controllerExtensionName</code> should allow to skip the <code>extensionName</code> argument of <code>f:translate()</code>:</p>
<pre>
page = PAGE
page.1 = FLUIDTEMPLATE
page.1 {
extbase.controllerExtensionName = felogin
template = TEXT
template.value (
<dl>
<dt>f:translate key="username":</dt>
<dd><f:translate key="username" /></dd>
</dl>
)
}
</pre>
<p>But in v12.4.8-dev, this is thrown:</p>
<pre>
#1639828178 RuntimeException
ViewHelper f:translate in non-extbase context needs attribute "extensionName" to resolve key="username" without path. Either set attribute "extensionName" together with the short key "yourKey" to result in a lookup "LLL:EXT:your_extension/Resources/Private/Language/locallang.xlf:yourKey", or (better) use a full LLL reference like key="LLL:EXT:your_extension/Resources/Private/Language/yourFile.xlf:yourKey". Alternatively, you can also define a default value.
</pre>
<p>In 11.5.33-dev this works.</p>
<p>Ref: FLUIDTEMPLATE docs <a class="external" href="https://docs.typo3.org/m/typo3/reference-typoscript/12.4/en-us/ContentObjects/Fluidtemplate/Index.html#extbase-controllerextensionname">https://docs.typo3.org/m/typo3/reference-typoscript/12.4/en-us/ContentObjects/Fluidtemplate/Index.html#extbase-controllerextensionname</a></p> TYPO3 Core - Bug #99503 (Resolved): Inline script concatenation requires scripts to have trailing...http://forge.typo3.org/issues/995032023-01-10T10:50:11ZJonas Eberlejonas.eberle@aero.de
<p>concatenateJs produces invalid JavaScript if scripts do not end with ';'.</p>
<p>In JavaScript ';' line endings are optional, but when concatenating scripts a ';' (or a line feed) needs to be added.</p>
<p>Minimum reproducible example:</p>
<p>(TypoScript settings)<br /><pre>
config.concatenateJs = 1
page.jsInline {
script1 = TEXT
script1.value = alert(1)
script2 = TEXT
script2.value = alert(2)
}
</pre></p>
<p>This results in<br /><pre>
alert(1)alert(2)
</pre></p>
<p>(This applies to concatenated files in any of the PAGE.includeJS functions and friends, too)</p> TYPO3 Core - Task #98326 (Closed): Core Development: Improve "watch" Grunt workflowhttp://forge.typo3.org/issues/983262022-09-10T13:01:42ZJonas Eberlejonas.eberle@aero.de
<p>The "watch" task could notify the developer when changes have been compiled. <br />As long as we do not have live/hot reload of the backend, this would help to indicate that changes can now be tested.</p> TYPO3 Core - Feature #97563 (New): Add rendering option to `select` fields to hide them if only 1...http://forge.typo3.org/issues/975632022-05-06T08:00:27ZJonas Eberlejonas.eberle@aero.de
<p>This is about adding a TCA rendering option to <code>select</code> fields that would hide the field from the editor if there is only 1 value available.</p>
<p>This allows decluttering the backend form by removing fields where the editor does not actually have a choice. This leads to better UX.</p>
<p>The immediate use case is if the Core wants to provide fields but not provide any options (except default) for it because it only becomes useful if an integrator adds functionality there.</p>
<p>There might also be other use cases for integrators to use this option. For example, when dynamically adding items through a <code>userFunc</code> which could result in only 1 item.</p> TYPO3 Core - Task #97562 (New): Remove the example "Layout 1/2/3" entries from tt_content.layout ...http://forge.typo3.org/issues/975622022-05-06T07:48:42ZJonas Eberlejonas.eberle@aero.de
<p>They do not provide any functionality and are merely an example.<br />They might just confuse editors if the integrator has not cleaned up that field or used them in the frontend.</p>
<p>Keep the fields, though since they serve a role (providing "variants" of a page/content element) and we would like integrators to use them if they implement a "variant" for commonality.</p>
<p>That's breaking, thus provide a .rst how to get the example values back (Configuration/TCA/Overrides/tt_content.php).</p>
<p>It has to be discussed if the .xlf-entries should stay although unused.</p> TYPO3 Core - Bug #95656 (Closed): Backend: scrollbar in .scaffold-modulemenu on Firefox cuts int...http://forge.typo3.org/issues/956562021-10-14T17:52:41ZJonas Eberlejonas.eberle@aero.de
<p>The problem from <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Backend: scrollbar in .scaffold-modulemenu on Firefox cuts into icons (Closed)" href="http://forge.typo3.org/issues/94633">#94633</a> resurfaced.</p> TYPO3 Core - Bug #95648 (Closed): Undefined array key 0 in /var/www/html/typo3/sysext/indexed_sea...http://forge.typo3.org/issues/956482021-10-14T13:12:20ZJonas Eberlejonas.eberle@aero.de
<p>After searching, if there should be results.</p>
<p>backtrace:</p>
<pre>
in /var/www/html/typo3/sysext/core/Classes/Error/ErrorHandler.php line 145
at TYPO3\CMS\Core\Error\ErrorHandler->handleError(2, 'Undefined array key 0', '/var/www/html/typo3/sysext/indexed_search/Classes/Domain/Repository/IndexSearchRepository.php', 1226)
in /var/www/html/typo3/sysext/indexed_search/Classes/Domain/Repository/IndexSearchRepository.php line 1226
at TYPO3\CMS\IndexedSearch\Domain\Repository\IndexSearchRepository->multiplePagesType('0')
in /var/www/html/typo3/sysext/indexed_search/Classes/Domain/Repository/IndexSearchRepository.php line 262
at TYPO3\CMS\IndexedSearch\Domain\Repository\IndexSearchRepository->doSearch(array(array('sword' => 'lo', 'oper' => 'AND')), -1)
in /var/www/html/typo3/sysext/indexed_search/Classes/Controller/SearchController.php line 289
...
</pre> TYPO3 Core - Feature #95629 (Rejected): Provide ViewHelper for PageTitleAPIhttp://forge.typo3.org/issues/956292021-10-13T14:19:08ZJonas Eberlejonas.eberle@aero.de
<p>The PageTitleAPI works great for any kind of pages or records and is used by many extensions.</p>
<p>For SEO and accessiblity reasons it makes sense to output an <h1> in the main page layout, but to my knowledge we don't have an out-of-the-box way to use the PageTitle value in a Fluid template.</p>
<p>A ViewHelper could look like this:</p>
<pre>
use TYPO3\CMS\Core\PageTitle\PageTitleProviderManager;
use TYPO3\CMS\Core\Utility\GeneralUtility;
use TYPO3Fluid\Fluid\Core\Rendering\RenderingContextInterface;
use TYPO3Fluid\Fluid\Core\ViewHelper\AbstractViewHelper;
class PageTitleViewHelper extends AbstractViewHelper
{
public static function renderStatic(
array $arguments,
\Closure $renderChildrenClosure,
RenderingContextInterface $renderingContext
) {
return GeneralUtility::makeInstance(PageTitleProviderManager::class)->getTitle();
}
}
</pre> TYPO3 Core - Bug #95539 (New): Installation should show error if AJAX failshttp://forge.typo3.org/issues/955392021-10-08T09:36:11ZJonas Eberlejonas.eberle@aero.de
<p>On step 4 (when the actual installation happens):</p>
<p><img src="http://forge.typo3.org/attachments/download/36458/clipboard-202110081126-3jafz.png" alt="" loading="lazy" /></p>
<p>Even if there has been an error, the progress bar conveys that it is still doing something.</p>
<p>In the case I have at hand here, the AJAX request returned with 500 and this HTML response:</p>
<pre>
Symfony\Component\DependencyInjection\Exception\RuntimeException
Cannot autowire service "TYPO3\CMS\Core\DataHandling\SoftReference\SoftReferenceParserFactory":
argument "$runtimeCache" of method "__construct()" references interface "TYPO3\CMS\Core\Cache\Frontend\FrontendInterface"
but no such service exists. You should maybe alias this interface to one of these existing services:
...
</pre>
<p>Whatever the error is, we should make the user aware of that occurrence and where to find the log.</p>
<p>In my opinion it would help the user to directly show him/her the returned error message but I am not sure how others think about it.</p> TYPO3 Core - Bug #95519 (Closed): Undefined array key "file" in typo3/sysext/frontend/Classes/Typ...http://forge.typo3.org/issues/955192021-10-07T12:00:16ZJonas Eberlejonas.eberle@aero.de
<pre>
PHP Warning: Undefined array key "file" in /var/www/html/typo3/sysext/frontend/Classes/Typolink/FileOrFolderLinkBuilder.php line 34, in file /var/www/html/typo3/sysext/core/Classes/Error/ErrorHandler.php:145 -
Stack trace:
#0 /var/www/html/typo3/sysext/frontend/Classes/Typolink/FileOrFolderLinkBuilder.php(34): TYPO3\\CMS\\Core\\Error\\ErrorHandler->handleError(2, 'Undefined array...', '/var/www/html/t...', 34)
#1 /var/www/html/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(4745): TYPO3\\CMS\\Frontend\\Typolink\\FileOrFolderLinkBuilder->build(Array, 'wefwefewfewf', '', Array)
#2 /var/www/html/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(2310): TYPO3\\CMS\\Frontend\\ContentObject\\ContentObjectRenderer->typoLink('wefwefewfewf', Array)
#3 /var/www/html/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(1339): TYPO3\\CMS\\Frontend\\ContentObject\\ContentObjectRenderer->stdWrap_typolink('wefwefewfewf', Array)
#4 /var/www/html/typo3/sysext/frontend/Classes/ContentObject/TextContentObject.php(44): TYPO3\\CMS\\Frontend\\ContentObject\\ContentObjectRenderer->stdWrap('wefwefewfewf', Array)
#5 /var/www/html/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php(798): TYPO3\\CMS\\Frontend\\ContentObject\\TextContentObject->render(Array)
...
</pre> TYPO3 Core - Task #95338 (Closed): Cleanup template modulehttp://forge.typo3.org/issues/953382021-09-23T20:14:30ZJonas Eberlejonas.eberle@aero.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Streamline Web->Template module UI (Closed)" href="http://forge.typo3.org/issues/93523">#93523</a> parts of the template module have been refactored.</p>
<p>We propose to restore the old order partly.</p>
<p>Left before / Right after change<br /><img src="http://forge.typo3.org/attachments/download/36388/clipboard-202109232213-w1tmm.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/36389/clipboard-202109232214-tarqx.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #95336 (Closed): Logging in a newly created user errors with "No such workspace ...http://forge.typo3.org/issues/953362021-09-23T17:39:01ZJonas Eberlejonas.eberle@aero.de
<p>The instance did have EXT:workspaces installed but no workspace created yet.</p>
<p>After adding a new user (just username + password filled out) the error occured when that user tried to log in.</p>
<p>Backtrace<br /><pre>
InvalidArgumentException in /var/www/html/typo3/sysext/workspaces/Classes/Service/WorkspaceService.php line 137
at TYPO3\CMS\Workspaces\Service\WorkspaceService::getWorkspaceTitle(-99)
in /var/www/html/typo3/sysext/workspaces/Classes/Backend/ToolbarItems/WorkspaceSelectorToolbarItem.php line 46
at TYPO3\CMS\Workspaces\Backend\ToolbarItems\WorkspaceSelectorToolbarItem->__construct()
in /var/www/html/typo3/sysext/core/Classes/Utility/GeneralUtility.php line 3271
at TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Workspaces\\Backend\\ToolbarItems\\WorkspaceSelectorToolbarItem')
in /var/www/html/typo3/sysext/backend/Classes/Controller/BackendController.php line 157
</pre></p> TYPO3 Core - Bug #95334 (Closed): FlashMessages not showing in BeLog and BeUser moduleshttp://forge.typo3.org/issues/953342021-09-23T16:35:17ZJonas Eberlejonas.eberle@aero.de
<p>We had these FlashMessages when deleting log entries:<br /><img src="http://forge.typo3.org/attachments/download/36387/clipboard-202109231833-jr0f6.png" alt="" loading="lazy" /></p>
<p>They disappeared with<br /><a class="external" href="https://forge.typo3.org/issues/94209">https://forge.typo3.org/issues/94209</a> / <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/69269">https://review.typo3.org/c/Packages/TYPO3.CMS/+/69269</a></p> TYPO3 Core - Task #95221 (Closed): Remove unused LLL: xlf keys in indexed_searchhttp://forge.typo3.org/issues/952212021-09-15T11:20:06ZJonas Eberlejonas.eberle@aero.de
<p>It seems that from locallang_pi.xlf only 2 strings are used for newContentElement wizard.</p>