Bobcares

TYPO3 No TypoScript template found – Quick Fix!

by | Jan 23, 2020

Are you looking for why TYPO3 is showing the error no TypoScript template found? We can help you fix it.

Usually, the error shows up if there is not template enabled at the root level flag.

At Bobcares, we often get requests to fix TYPO3 errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix this error.

 

What is the TypoScript template?

TYPO3 CMS has a clear separation between contents and its design. But this works in coordination because of the configuration language, TypoScript.

For instance, TypoScript reads content from the database, prepares it to display, then it shows up in the frontend. Hence, a TypoScript defines how a webpage contents should be rendered in the frontend.

Basically, a TypoScript template, created in the template module can exist on any page. But mistakes in the TypoScript template can end up in errors. So, let’s discuss the error Service Unavailable (503).

The complete error message appears as,

TYPO3 error no TypoScript template found.

 

How we fix the error no TypoScript template found?

Now let’s see how our Support Engineers fix this error. Usually, the error shows up when there is no template enabled with the root level flag in the page tree.

So to fix this error, we need to enable the root level flag. And we do this as follows:

1. Initially, we login to the TYPO3 backend.

2. Now from the module menu, we choose the option WEB >> Template.

3. Next, we select the root page from the page tree. And this opens the Template tool window.

4. Here we select the option Info/Modify from the dropdown in the Docheader.

5. Then we select the option Edit the whole template record.

6. Here our Support Engineers check the entries under the option General. This is where we add the page object. For instance, a standard entry of the page setup appears as,

page = PAGE
page.10 = TEXT
page.10.value = <Page setup>

7. Next under the Options tab, we ensure to enable the checkbox Rootlevel.

8. Later, in the Includes tab, we add the appropriate template options.

Finally, we check that the error doesn’t show up again.

[Still, having trouble in fixing TYPO3 errors? – We can help you.]

 

Conclusion

In short, the TYPO3 error ‘No TypoScript template found’ shows up if there is no template enabled at the root level flag. In today’s writeup, we saw how our Support Engineers fix this error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF