Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given. #34

Open
stephangrass opened this issue Jun 16, 2020 · 10 comments
Labels
bug Something isn't working

Comments

@stephangrass
Copy link

After updating to TYPO3 10.4.4 with luxletter 2.2.0 I get the error

TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given.

when trying to send an test-newsletter and trying to send the regular newsletter.

Where's the problem?

@einpraegsam
Copy link
Collaborator

I don't know but the extension needs to be used via composer - see https://github.com/in2code-de/luxletter#technical-requirements

@stephangrass
Copy link
Author

Arghhh ...

@stephangrass
Copy link
Author

OK. I will try to migrate this project to Composer ...

@stephangrass
Copy link
Author

I migrate to composer, the error still appears ...

@einpraegsam
Copy link
Collaborator

Can you please give me some more information about the failure. Or can you please provide a screenshot?

@stephangrass
Copy link
Author

OK. The whole error message, after trying to send a test email:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1561583127: TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given. | InvalidArgumentException thrown in file /.../typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php in line 798. Requested URL: https://.../index.php?route=%%2Fajax%%2Fluxletter%%2FtestMail&token=--AnonymizedToken--&origin=https%%3A%%2F%%2F...%%2F...%%2F...&email=...%%40...&subject=test

@stephangrass
Copy link
Author

Hi again.
Here's the problem:

I try to use my own Templates/Partials:

plugin {
    tx_luxletter_fe {
        view {
            templateRootPaths {
                10 = EXT:myext/Resources/Private/Extensions/Luxletter/Templates/
            }
            partialRootPaths {
                10 = EXT:myext/Resources/Private/Extensions/Luxletter/Partials/
            }
            layoutRootPaths {
                10 = EXT:myext/Resources/Private/Extensions/Luxletter/Layouts/
            }
        }
        features.requireCHashArgumentForActionArguments = 0
    }
}

When I copy this to module, so that the send newsletter will also use the templates

module.tx_luxletter < plugin.tx_luxletter_fe

I get the error above.

Without
module.tx_luxletter < plugin.tx_luxletter_fe
the newsletter will be send, but by using the standard tempates from luxletter.

@stephangrass
Copy link
Author

The "solution":

In my template I tried to use TypoScript constants in this way:

<f:cObject typoscriptObjectPath="lib.footer_bottom"></f:cObject>

lib.footer_bottom:

lib.footer_bottom = TEXT
lib.footer_bottom.value = {$footer_bottom}

{$footer_bottom} ist some text defined in the typoscript constans in the root template.

This doesn not work (in TYPO3 10) and results in the described error.

... Hmmmm ...

@einpraegsam
Copy link
Collaborator

Probably the same issue as described here: #45

@einpraegsam einpraegsam added the bug Something isn't working label Sep 22, 2020
@einpraegsam
Copy link
Collaborator

Can you please check with the latest version 4.0 if this problem still exists?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants