Studied psychology and IT. Worked for 25 years in the German film industry. Since 2005 zazu.berlin FILM+DIGITAL - webpages with TYPO3, platform design and film production.

My name is Edward Lenssen, founder and CEO of Beech. I live and work in Venlo, The Netherlands, at walking distance from the German border near Düsseldorf. I've been using TYPO3 since 2004.

Hello TYPO3 Community, today we've released TYPO3 11.5.25 LTS, which is ready for you to download. This version is a maintenance release and contains bug fixes only. For details about the release, please see: https://get.typo3.

Thema: Extensions fit machen für TYPO3 v12 Gemeinsam mit ein paar Entwicklern, die bereits Erfahrungen mit Extension Upgrades gesammelt haben, schauen wir uns an, was sich alles geändert hat.

With version 11.5, felogin/Resources/Private/Templates/Login templates no longer seems to be used.

Is this true? How can I change the login/logout pages?

br, MV

1 post - 1 participant

Hello to all!

We have a group of editors that has to edit in “live mode” a subtree in our site and has to edit in “draft mode only” another subtree of the same site.

Is it possible? All my tests suggest that rights are additive… Our 2 subtrees have different user groups with appropriate rights and our editor group inherit both groups.

How can we manage that kind of configuration?

A million thanks!

Eric T.

1 post - 1 participant

Hi,
I need to use versioning on pages and tt_content tables. i’m using Typo3 12.2.0 and I activate extension workspaces, create workspace and user. When I add new page on workspace record is created, but after publishing old record is replaced new record. In pages table i can see only last version of record. Records in sys_log table are created, but i can’t restore old version of page.
Can someone help with running versioning.

1 post - 1 participant

The TYPO3 documentation tools are constantly improved by the TYPO3 Documentation Team to support you, the reader, in getting comprehensive information and quickly finding answers to your questions, and to help you, the author, in creating documentati…

Hi,
I have setup a new environment (Ubuntu VM+T3) to start Development.
T3 ist setup as Production Type “Development”.
When using plugin SAV_Charts I get these errors on the frontpage. I am sure it has nothing directly to do with SAV_Charts since the setup is the same as in my Production environment and it works well there.

Can anyone identify where the problem in the setup of the environment could be?
<pre><code class="lang-auto">
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception

PHP Warning: Undefined array key "marker." in /var/www/html/averlon.de/av_t3test/public/typo3conf/ext/sav_charts/Classes/Controller/DefaultController.php line 154
in /var/www/html/averlon.de/av_t3test/public/typo3/sysext/core/Classes/Error/ErrorHandler.php line 137

}

$message = self::ERROR_LEVEL_LABELS[$errorLevel] . ': ' . $errorMessage . ' in ' . $errorFile . ' line ' . $errorLine;
if ($errorLevel & $this->exceptionalErrors) {
throw new Exception($message, 1476107295);
}

$message = $this->getFormattedLogMessage($message);

at TYPO3\CMS\Core\Error\ErrorHandler->handleError()
in /var/www/html/averlon.de/av_t3test/public/typo3conf/ext/sav_charts/Classes/Controller/DefaultController.php line 154


// Sets markers defined by typoscript
$typoScriptService = GeneralUtility::makeInstance(TypoScriptService::class);
$typoScriptConfiguration = $typoScriptService->convertPlainArrayToTypoScriptArray($this->getSettings());
if (is_array($typoScriptConfiguration) && is_array($typoScriptConfiguration['marker.'])) {
$typoScriptMarkers = $typoScriptConfiguration['marker.'];
foreach ($typoScriptMarkers as $typoScriptMarkerKey => $typoScriptMarker) {
if (strpos($typoScriptMarkerKey, '.') === false) {
$typoScriptValue = $this->getContentObjectRenderer()->cObjGetSingle($typoScriptMarker, $typoScriptMarkers[$typoScriptMarkerKey . '.']);

at YolfTypo3\SavCharts\Controller\DefaultController->showAction()
in /var/www/html/averlon.de/av_t3test/public/typo3/sysext/extbase/Classes/Mvc/Controller/ActionController.php line 575

}
$validationResult = $this->arguments->validate();
if (!$validationResult->hasErrors()) {
$this->eventDispatcher->dispatch(new BeforeActionCallEvent(static::class, $this->actionMethodName, $preparedArguments));
$actionResult = $this->{$this->actionMethodName}(...$preparedArguments);
} else {
$actionResult = $this->{$this->errorMethodName}();
}

at TYPO3\CMS\Extbase\Mvc\Controller\ActionController->callActionMethod()
in /var/www/html/averlon.de/av_t3test/public/typo3/sysext/extbase/Classes/Mvc/Controller/ActionController.php line 492

$this->view = $this->resolveView();
if ($this->view !== null && method_exists($this, 'initializeView')) {
$this->initializeView($this->view);
}
$response = $this->callActionMethod($request);
$this->renderAssetsForRequest($request);

return $response;
}

at TYPO3\CMS\Extbase\Mvc\Controller\ActionController->processRequest()
in /var/www/html/averlon.de/av_t3test/public/typo3/sysext/extbase/Classes/Mvc/Dispatcher.php line 96

throw new InfiniteLoopException('Could not ultimately dispatch the request after ' . $dispatchLoopCount . ' iterations. Most probably, a @' . IgnoreValidation::class . ' annotation is missing on re-displaying a form with validation errors.', 1217839467);
}
$controller = $this->resolveController($request);
try {
$response = $controller->processRequest($request);
if ($response instanceof ForwardResponse) {
// The controller action returned an extbase internal Forward response:
// Another action should be dispatched.
$request = static::buildRequestFromCurrentRequestAndForwardResponse($request, $response);

at TYPO3\CMS\Extbase\Mvc\Dispatcher->dispatch()
in /var/www/html/averlon.de/av_t3test/public/typo3/sysext/extbase/Classes/Mvc/Web/FrontendRequestHandler.php line 46

* @throws InfiniteLoopException
*/
public function handleRequest(RequestInterface $request)
{
return $this->dispatcher->dispatch($request);
}

/**
* This request handler can handle any web request.

</code></pre>
There are some more lines but the thread is limited - for good reason!

I am nearly sure there is something on permissions or wrong file content somewhere. But since I am not familiar with PHP I cannot find out.

Help appreciated.
Regards Karl-Heinz

1 post - 1 participant

Dear TYPO3 users, a vulnerability has been found in the following third party TYPO3 extension: "Forms Export" (frp_form_answers) For further information on the issues, please read the related advisory TYPO3-EXT-SA-2023-002 which was published tod…

I’m a newbie to Typo3 (v 12.2.0) and got lost just before configuring the backend. I have a domain example.com and Typo3 should be accessible via (https://)example.com/typo3-test1. The “https://” is automatically inserted by Apache2 (v2.4.54).

Hi,
I have installed an Extension and FE is shown in the correct language.

Since I modified one template and want to add some text, I tried to add the related ID in the de.localllang.xlf - but it is not shown in FE.
<pre><code class="lang-auto"><f:translate id="nextYear" />
</code></pre> <pre><code class="lang-auto"> <trans-unit id="nextYear">
<source>next year</source>
<target state="needs-translation">nächstes Jahr</target>
</trans-unit>

</code></pre>
Can someone help how I can add own IDs to the language file which then show up in its translation in the FE?
Regards Karl-Heinz

1 post - 1 participant

Hello TYPO3 Community, today we've released TYPO3 11.5.24 LTS, which is ready for you to download. This version is a maintenance release and contains bug fixes only. For details about the release, please see: https://get.typo3.

I have updated from 9.5.0 to 10.36. Sofar the website and extensions are working fine.

tt_news is updated to 10.0.1 and extender to 7.1.0

On Typo 3 9 I had already created new fields using the extender.

After updating and installing the extensions, all the fields can be viewed in the backend but the values (of news fields) are not viewable in Frontend.

I get the following error for address.php
<pre><code class="lang-auto">1/1) Symfony\Component\DependencyInjection\Exception\InvalidArgumentException
Expected to find class "Evoweb\Extender\Domain\Model\Address" in file
"/typo3_src-10/typo3conf/ext/extender/Classes/Domain/Model/Address.php"
while importing services from resource "../Classes/*",

but it was not found! Check the namespace prefix used with the resource.
</code></pre>
Could you please help me here.

1 post - 1 participant

Thema: Unterstützung von Redakteuren durch OpenAI (ChatGPT) im TYPO3 Backend (André Lademann) Netresearch hat die API von OpenAI (ChatGPT) ins TYPO3 Backend integriert.

“The documentation was my first home within the TYPO3 ecosystem. The team consisted of Martin Bless back then and he allowed me to contribute back to the project. That was around 2018.

Hi,
I would like to show a category tree with tt_products.

The plugin “category_menu” does only show the root level of the category tree.

I have installed mbi_products_categories. This now allows me to assign the tt_products categories (not the system categories) to products.

But how to show the category tree in FE?

1 post - 1 participant

Hello,

I’ve a problem with typo3 backend, some element used the bparams “|” but this character is forbidden for the standard “RFC 1738”, so our server don’t permit to used this character in url and I’ve an error “You don’t have permission to access this resource.”

Do you have an idea how I can changed the character “|” by the encoding “%7C” ?

Thx for your reply

1 post - 1 participant

Dear TYPO3 Community, today we've released TYPO3 12.2.0, 11.5.23 LTS and 10.4.36 LTS, which are ready for you to download.

Hi,
I have setup a picture as page content in BE.
Now I assumed if I use Image Manipulation “OpenEditor” and do some changes and “accept”, the view on the image should change - but it does not!!! Cache is disabled!

What is Image Manipulation for and how to use it?

Thanks
Karl-Heinz

1 post - 1 participant

Dear TYPO3 Community, the TYPO3 Security Team pre-announces important security releases which are planned to be published on Tuesday, February 7th, 2023 between 9:00-12:00 UTC. All officially supported versions are affected and will be fixed.

I am trying to setup tt_products from scratch on T3 11.5.

• tt_products included in template
• sysfolder with one product and some categries
• page with plugin Products:List - but no product is shown!
• page with plugin Categories:menu - categories are shown!

No typoscript changes, no own typoscript, all settings via BE form of tt_products.

What do I miss to see the dummy product?

Help appreciated!

Regards Karl-Heinz

1 post - 1 participant

Dear TYPO3 users, a vulnerability has been found in the following third party TYPO3 extension: "femanager" (femanager) For further information on the issues, please read the related advisory TYPO3-EXT-SA-2023-001 which was published today: TYPO3…

Hi,
I have upgraded from 10.4 to 11.5. Website works! But I get an error when logging in to the BE.
<pre><code class="lang-auto">The requested URL was not found on this server.
</code></pre>
I have seen in the changelog that some things with login to the BE have changed. When using APACHE (what I do) some rewriting is now used.
Rewriting is activated and the .htaccess is not changed by me.

But it looks like something is going wrong.

Logfile says:
<pre><code class="lang-auto">[Mon Jan 30 08:23:08.000809 2023] [core:info] [pid 18767] [client 127.0.0.1:37536] AH00128: File does not exist: /var/www/averlon.de/av_homep/public/typo3/login, referer: http://www.averlon.de/typo3/
</code></pre>
But I guess this is only a follow-up error of the misconfiguration.

Any help appreciated.
Regards
Karl-Heinz

1 post - 1 participant

Hi,
I get errors when trying to upgrade via composer from 10.4.x to 11.5.0.

Can please someone help me identify the problem and probably have a solution for this:
<pre><code class="lang-auto">composer require typo3/cms-core:11.5.0 --update-with-dependencies
The TYPO3 extension package "sjbr/sr-freecap", does not define an extension key in its composer.json. Please report this to the author of this package. Specifying the extension key will be mandatory in future versions of TYPO3 (see: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ComposerJson.html#extra)
./composer.json has been updated
Running composer update typo3/cms-core --with-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires typo3/cms-core 11.5.0, found typo3/cms-core[v11.5.0] but these were not loaded, likely because it conflicts with another require.
Problem 2
- typo3/cms-about is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-about v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 3
- typo3/cms-adminpanel is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-adminpanel v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 4
- typo3/cms-backend is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-backend v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 5
- typo3/cms-belog is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-belog v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 6
- typo3/cms-beuser is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-beuser v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 7
- typo3/cms-extbase is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-extbase v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 8
- typo3/cms-extensionmanager is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-extensionmanager v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 9
- typo3/cms-filelist is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-filelist v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 10
- typo3/cms-fluid is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-fluid v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 11
- typo3/cms-fluid-styled-content is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-fluid-styled-content v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 12
- typo3/cms-form is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-form v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 13
- typo3/cms-frontend is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-frontend v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 14
- typo3/cms-impexp is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-impexp v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 15
- typo3/cms-info is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-info v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 16
- typo3/cms-install is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-install v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 17
- typo3/cms-lowlevel is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-lowlevel v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 18
- typo3/cms-opendocs is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-opendocs v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 19
- typo3/cms-recordlist is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-recordlist v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 20
- typo3/cms-recycler is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-recycler v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 21
- typo3/cms-redirects is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-redirects v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 22
- typo3/cms-reports is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-reports v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 23
- typo3/cms-rte-ckeditor is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-rte-ckeditor v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 24
- typo3/cms-scheduler is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-scheduler v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 25
- typo3/cms-seo is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-seo v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 26
- typo3/cms-setup is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-setup v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 27
- typo3/cms-tstemplate is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-tstemplate v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 28
- typo3/cms-viewpage is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-viewpage v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 29
- bk2k/bootstrap-package is locked to version 11.0.4 and an update of this package was not requested.
- bk2k/bootstrap-package 11.0.4 requires ext-dom * -> it is missing from your system. Install or enable PHP's dom extension.
Problem 30
- georgringer/news is locked to version 8.6.0 and an update of this package was not requested.
- georgringer/news 8.6.0 requires typo3/cms-core ^9.5.17 || ^10.4.12 -> found typo3/cms-core[v9.5.17, ..., v9.5.31, v10.4.12, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 31
- friendsoftypo3/tt-address is locked to version 5.3.0 and an update of this package was not requested.
- friendsoftypo3/tt-address 5.3.0 requires typo3/cms-core ^9.5.20 || ^10.4.6 || ^11.3 -> found typo3/cms-core[v9.5.20, ..., v9.5.31, v10.4.6, ..., v10.4.34, v11.3.0, ..., v11.5.22] but these were not loaded, likely because it conflicts with another require.
Problem 32
- yolftypo3/sav-charts is locked to version 10.4.0 and an update of this package was not requested.
- yolftypo3/sav-charts 10.4.0 requires typo3/cms-core >=9.5,<11.0 -> found typo3/cms-core[v9.5.0, ..., v9.5.31, v10.0.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 33
- clickstorm/go_maps_ext is locked to version 4.2.0 and an update of this package was not requested.
- clickstorm/go_maps_ext 4.2.0 requires typo3/cms-core ^10.0 -> found typo3/cms-core[v10.0.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 34
- sjbr/static-info-tables is locked to version v6.9.6 and an update of this package was not requested.
- sjbr/static-info-tables v6.9.6 requires php ^7.0 -> your php version (8.1.2) does not satisfy that requirement.
Problem 35
- jambagecom/static-info-tables-de is locked to version v6.7.13 and an update of this package was not requested.
- jambagecom/static-info-tables-de v6.7.13 requires typo3/cms-core ^10.4 || ^11.5 -> found typo3/cms-core[v10.4.0, ..., v10.4.34, v11.5.0, ..., v11.5.22] but these were not loaded, likely because it conflicts with another require.
Problem 36
- codingms/rss-app is locked to version 1.0.7 and an update of this package was not requested.
- codingms/rss-app 1.0.7 requires ext-dom * -> it is missing from your system. Install or enable PHP's dom extension.
Problem 37
- sjbr/sr-feuser-register is locked to version v7.0.5 and an update of this package was not requested.
- sjbr/sr-feuser-register v7.0.5 requires typo3/cms-core ^9.5 || ^10.4 -> found typo3/cms-core[v9.5.0, ..., v9.5.31, v10.4.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 38
- evoweb/sf-register is locked to version 10.2.0 and an update of this package was not requested.
- evoweb/sf-register 10.2.0 requires typo3/cms-core ^10.4 -> found typo3/cms-core[v10.4.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 39
- sjbr/sr-freecap is locked to version v2.6.2 and an update of this package was not requested.
- sjbr/sr-freecap v2.6.2 requires typo3/cms-core ^10.4 -> found typo3/cms-core[v10.4.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 40
- evoweb/recaptcha is locked to version 10.0.3 and an update of this package was not requested.
- evoweb/recaptcha 10.0.3 requires typo3/cms-core ^10.4 -> found typo3/cms-core[v10.4.0, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 41
- typo3/cms-dashboard is locked to version v10.4.34 and an update of this package was not requested.
- typo3/cms-dashboard v10.4.34 requires typo3/cms-core 10.4.34 -> found typo3/cms-core[v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 42
- jweiland/weather2 is locked to version 3.1.3 and an update of this package was not requested.
- jweiland/weather2 3.1.3 requires typo3/cms-core ^9.5.17 || ^10.4.2 -> found typo3/cms-core[v9.5.17, ..., v9.5.31, v10.4.2, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 43
- felixnagel/generic-gallery is locked to version 4.3.0 and an update of this package was not requested.
- felixnagel/generic-gallery 4.3.0 requires php >=7.2,<7.5 -> your php version (8.1.2) does not satisfy that requirement.
Problem 44
- netzmacher/slick is locked to version 6.1.12 and an update of this package was not requested.
- netzmacher/slick 6.1.12 requires typo3/cms-core ^6.2 || ^7.6 || ^8.7 || ^9.6 || ^10.4 || ^11.5 -> found typo3/cms-core[v8.7.7, ..., v8.7.32, v10.4.0, ..., v10.4.34, v11.5.0, ..., v11.5.22] but these were not loaded, likely because it conflicts with another require.
Problem 45
- clickstorm/cs-seo is locked to version 6.4.1 and an update of this package was not requested.
- clickstorm/cs-seo 6.4.1 requires typo3/cms-core ^10.4.16 -> found typo3/cms-core[v10.4.16, ..., v10.4.34] but it conflicts with your root composer.json require (11.5.0).
Problem 46
- friendsoftypo3/extension-builder is locked to version v10.0.5 and an update of this package was not requested.
- friendsoftypo3/extension-builder v10.0.5 requires php ^7.2 -> your php version (8.1.2) does not satisfy that requirement.
Problem 47
- jambagecom/addons-em is locked to version v0.5.1 and an update of this package was not requested.
- jambagecom/addons-em v0.5.1 requires typo3/cms-core ^9.5 || ^10.4 || ^11.5 -> found typo3/cms-core[v9.5.0, ..., v9.5.31, v10.4.0, ..., v10.4.34, v11.5.0, ..., v11.5.22] but these were not loaded, likely because it conflicts with another require.
Problem 48
- undefined/translate-locallang is locked to version 2.8.1 and an update of this package was not requested.
- undefined/translate-locallang 2.8.1 requires typo3/cms-core >=10.4.0 <=11.5.99 -> found typo3/cms-core[v10.4.0, ..., v10.4.34, v11.0.0, ..., v11.5.22] but these were not loaded, likely because it conflicts with another require.

To enable extensions, verify that they are enabled in your .ini files:
- /etc/php/8.1/cli/php.ini
- /etc/php/8.1/cli/conf.d/10-mysqlnd.ini
- /etc/php/8.1/cli/conf.d/10-opcache.ini
- /etc/php/8.1/cli/conf.d/10-pdo.ini
- /etc/php/8.1/cli/conf.d/20-apcu.ini
- /etc/php/8.1/cli/conf.d/20-calendar.ini
- /etc/php/8.1/cli/conf.d/20-ctype.ini
- /etc/php/8.1/cli/conf.d/20-curl.ini
- /etc/php/8.1/cli/conf.d/20-exif.ini
- /etc/php/8.1/cli/conf.d/20-ffi.ini
- /etc/php/8.1/cli/conf.d/20-fileinfo.ini
- /etc/php/8.1/cli/conf.d/20-ftp.ini
- /etc/php/8.1/cli/conf.d/20-gd.ini
- /etc/php/8.1/cli/conf.d/20-gettext.ini
- /etc/php/8.1/cli/conf.d/20-gmp.ini
- /etc/php/8.1/cli/conf.d/20-iconv.ini
- /etc/php/8.1/cli/conf.d/20-imagick.ini
- /etc/php/8.1/cli/conf.d/20-intl.ini
- /etc/php/8.1/cli/conf.d/20-ldap.ini
- /etc/php/8.1/cli/conf.d/20-mbstring.ini
- /etc/php/8.1/cli/conf.d/20-mysqli.ini
- /etc/php/8.1/cli/conf.d/20-pdo_mysql.ini
- /etc/php/8.1/cli/conf.d/20-phar.ini
- /etc/php/8.1/cli/conf.d/20-posix.ini
- /etc/php/8.1/cli/conf.d/20-readline.ini
- /etc/php/8.1/cli/conf.d/20-shmop.ini
- /etc/php/8.1/cli/conf.d/20-sockets.ini
- /etc/php/8.1/cli/conf.d/20-sysvmsg.ini
- /etc/php/8.1/cli/conf.d/20-sysvsem.ini
- /etc/php/8.1/cli/conf.d/20-sysvshm.ini
- /etc/php/8.1/cli/conf.d/20-tokenizer.ini
- /etc/php/8.1/cli/conf.d/20-zip.ini
You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode.
Alternatively, you can run Composer with `--ignore-platform-req=ext-dom` to temporarily ignore these required extensions.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
</code></pre>
I also tried to run a command listing all components and versions explicitly - but more or less same result.
<pre><code class="lang-auto">composer require typo3/cms-core:^V11.5.0 typo3/cms-backend:^V11.5.0 typo3/cms-extbase:^V11.5.0 typo3/cms-extensionmanager:^V11.5.0 typo3/cms-filelist:^V11.5.0 typo3/cms-fluid:^10.4 typo3/cms-frontend:^V11.5.0 typo3/cms-install:^V11.5.0 typo3/cms-recordlist:^V11.5.0 typo3/cms-adminpanel:^V11.5.0 typo3/cms-belog:^V11.5.0 typo3/cms-beuser:^V11.5.0 typo3/cms-fluid:^V11.5.0 typo3/cms-fluid-styled-content:^V11.5.0 typo3/cms-form:^V11.5.0 typo3/cms-impexp:^V11.5.0 typo3/cms-info:^V11.5.0 typo3/cms-lowlevel:^V11.5.0 typo3/cms-opendocs:^V11.5.0 typo3/cms-recycler:^V11.5.0 typo3/cms-redirects:^V11.5.0 typo3/cms-reports:^V11.5.0 typo3/cms-rte-ckeditor:^V11.5.0 typo3/cms-scheduler:^V11.5.0 typo3/cms-seo:^V11.5.0 typo3/cms-setup:^V11.5.0 typo3/cms-tstemplate:^V11.5.0 typo3/cms-viewpage:^V11.5.0 typo3/cms-dashboard:^V11.5.0 typo3/cms-about:^V11.5.0 bk2k/bootstrap-package:^12.0.0 georgringer/news:^10.0.3 yolftypo3/sav-charts:^11.5.0 clickstorm/go_maps_ext:^5.1.0 sjbr/static-info-tables:^v11.5.3 jambagecom/static-info-tables-de:^v6.7.13 codingms/rss-app:^2.0.3 sjbr/sr-feuser-register:^v11.5.4 evoweb/sf-register:^11.1.3 sjbr/sr-freecap:^v11.5.2 evoweb/recaptcha:^11.0.4 jweiland/weather2:^4.0.1 felixnagel/generic-gallery:^5.2.0 clickstorm/cs-seo:^7.3.1 friendsoftypo3/extension-builder:^v11.0.9 netzmacher/slick:^10.0.1 friendsoftypo3/tt-address:^7.0.0 undefined/translate-locallang:^2.8.4 jambagecom/addons-em:^v0.5.1 gaalferov/php-ext-domain-connect:^1.3 --update-with-dependencies --ignore-platform-req=ext-dom --ignore-platform-req=ext-xml --ignore-platform-req=ext-simplexml
The TYPO3 extension package "sjbr/sr-freecap", does not define an extension key in its composer.json. Please report this to the author of this package. Specifying the extension key will be mandatory in future versions of TYPO3 (see: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ComposerJson.html#extra)
./composer.json has been updated
Running composer update typo3/cms-core typo3/cms-backend typo3/cms-extbase typo3/cms-extensionmanager typo3/cms-filelist typo3/cms-fluid typo3/cms-frontend typo3/cms-install typo3/cms-recordlist typo3/cms-adminpanel typo3/cms-belog typo3/cms-beuser typo3/cms-fluid-styled-content typo3/cms-form typo3/cms-impexp typo3/cms-info typo3/cms-lowlevel typo3/cms-opendocs typo3/cms-recycler typo3/cms-redirects typo3/cms-reports typo3/cms-rte-ckeditor typo3/cms-scheduler typo3/cms-seo typo3/cms-setup typo3/cms-tstemplate typo3/cms-viewpage typo3/cms-dashboard typo3/cms-about bk2k/bootstrap-package georgringer/news yolftypo3/sav-charts clickstorm/go_maps_ext sjbr/static-info-tables jambagecom/static-info-tables-de codingms/rss-app sjbr/sr-feuser-register evoweb/sf-register sjbr/sr-freecap evoweb/recaptcha jweiland/weather2 felixnagel/generic-gallery clickstorm/cs-seo friendsoftypo3/extension-builder netzmacher/slick friendsoftypo3/tt-address undefined/translate-locallang jambagecom/addons-em gaalferov/php-ext-domain-connect --with-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- layershifter/tld-extract[2.0.0, ..., 2.0.1] require php ^5.5.0 || ^7.0 -> your php version (8.1.2) does not satisfy that requirement.
- gaalferov/php-ext-domain-connect 1.3 requires layershifter/tld-extract ^2.0 -> satisfiable by layershifter/tld-extract[2.0.0, 2.0.1].
- Root composer.json requires gaalferov/php-ext-domain-connect ^1.3 -> satisfiable by gaalferov/php-ext-domain-connect[1.3].
</code></pre>
Any help appreciated!

1 post - 1 participant

Hello everybody, I’m fairly new to Typo3 and I have just made my first form - the problem is, when I use the form finisher “redirect to page” it throws an Error “Class ‘0;’ not found” when I submit the form.

I need to set a variable depending on the applicationContext, and this works in TYPO3 v10.4: [applicationContext == "Development/Testing"] page.footerData.50.value = 3 [applicationContext == "Production/Staging"] page.footerData.50.

Hi all, new to this group and also new to Typo3… Want to edit a site from a friend, but the backend looks weird to me, see screenshot. Have tried different browsers, computers, etc. the tabs, checkboxes, etc.

Hello,

I’m creating a backend module in File category.

I need to use the folders where I’m in using the file tree directory.

How can I get the folder name?

Thanks for your help!

1 post - 1 participant

Hello,

I’m creating a backend module in File category.

I need to use the folders where I’m in using the file tree directory.

How can I get the folder name?

Thanks for your help!

1 post - 1 participant

Hello TYPO3 Community, today we've released TYPO3 11.5.22 LTS, which is ready for you to download. This version is a maintenance release and contains bug fixes only. For details about the release, please see: https://get.typo3.

Themen:

TYPO3 und Vite - Integration von modernen Frontend-Tools (Florian Geierstanger)
Vite ist eine neue Art von Frontend-Build-Tools, das die Möglichkeiten bei der Frontend-Entwicklung deutlich verbessert. Florian zeigt uns, was Vite ist und wie es in TYPO3 integriert werden kann.

Composer Pakete in Extensions für TER Upload integrieren (Alexander Grein)
Alex Grein zeigt uns, wie man eine Extension, die Composer-Pakete nutzt, so anpasst, das man sie ins TER stellen kann, damit auch eine Installation ohne Composer aber mit allen Abhängigkeiten möglich ist.

Das Treffen findet ausschließlich online statt!

Alle Infos gibts hier:
Meetup

TYPO3 und Vite - Integration von modernen Frontend-Tools | TYPO3 Meetup...

**Themen:** * **TYPO3 und Vite - Integration von modernen Frontend-Tools** (Florian Geierstanger) [Vite](https://vitejs.dev/) ist eine neue Art von Frontend-Build-Tools, d


1 post - 1 participant

Hi,

I would like to integrate an exception handler into my extension when sending mail, to catch errors of the mailer when sending. Unfortunately the Mail API does not provide anything like this, see: https://docs.typo3.org/m/typo3/reference-coreapi/10.4/en-us/ApiOverview/Mail/Index.html

In the Symfony docs this is implemented with the TransportExceptionInterface, see:https://symfony.com/doc/current/mailer.html#handling-sending-failures
Unfortunately, this is not implemented in TYPO 3 (v10.4).

For now, I implemented a TYPO3\CMS\Core\Exception, since the Symfony\Component\Mailer\Transport uses it as well.

Has anyone already implemented an error handling for sending mail?

3 posts - 2 participants

Hi,
with Typo3 version 12.1.3
When uploading an extension i get a failure.

Extension bootstrap_package is not available
Extension site-package is not available

Any Clue ?
Best regards,
Hugo

2 posts - 2 participants

How to configure a site to work with
www.sitename.com
and
sitename.com.
in dns all is fixed.

For example. a wordpress site
www.kirsten-mare.com works.
kirsten-mare.com works
www.kirstenMare.com works
and KirstenMare.com works.
How to do the same in typo 3

Best regards,
Hugo

3 posts - 2 participants

Hi,

Typo 3 12.1.3 Upload extensions
I can not upload any extensions any clue.
and yes login with admin elevated all rights etc.
does not even try fails directly ?

Best regards,
Hugo

1 post - 1 participant

Hi, I am using version 10.4.32 and I am not very familiar with typo 3. All is working fine with www.xxx.de but when I just use xxx.de without the www there is an error shows up.

Hi, I am using version 10.4.32 and I am not very used to typo 3. All is working fine with www.xxx.de but when I just use xxx.de without the www there is an error shows up.