Study guide · Page properties, cache and admin panel
Page properties, cache and Admin Panel in everyday editing
In the page properties you decide what a page is called, which address it has, how it looks in search engines and when it is visible. After that you learn why a change is sometimes not visible right away and what the cache has to do with it. Finally, you check pages in the frontend with the Admin Panel.
The example: Weidenau City Library
All examples take place on the website of the Weidenau City Library. The page tree contains pages such as Home, Events, Media, Opening hours and Contact. The page Story time sits below Events. Lena is an editor and maintains the content. Tom is the administrator and looks after permissions, extensions and settings.
Lena has three tasks today. The page "Story time" should be renamed "Reading for children" and get a new address. It should look good in search engines and when people share it. And an Advent campaign should only appear in December.
Opening the page properties
The page properties belong to the page itself, not to its content. Lena opens them like this:
- In the Layout module in the Content area, she selects the page in the page tree. In the docheader, the bar above the content area, she clicks the "Edit page properties" button.
- Alternatively, she right-clicks the page in the page tree and chooses "Edit" in the context menu.
The form is split into tabs. Which tabs and fields Lena sees depends on three things: the page type, her user permissions and the configuration of the installation. For example, the SEO tab only exists for standard pages, and only with the system extension seo.
The General tab: titles and navigation title
The General tab holds the page type and the titles. Which page types you can choose depends on the site package and on your permissions.
The page title, labelled "Page title" in the form, is the most important field. TYPO3 uses it as the label in menus and in the title tag in the head of the HTML page, which is what the browser tab shows. The URL segment is also normally generated from the page title.
Sometimes the title is too long for the menu. That is what the alternative navigation title is for, labelled "Alternative Navigation Title". It only replaces the label in menus. The title tag and every other place keep using the page title.
The Subtitle field only appears somewhere if the site package outputs it. It does not replace the title in the menu, and it does not automatically become the description for Google.
The URL segment and redirects
The URL segment, also called the slug, is the part of the address under which the page can be reached. For the Events page, for example, that is the segment "events" after the domain. TYPO3 usually fills it in automatically from the title and the position in the page tree.
Important: if you rename or move a page later, the URL segment stays the same at first. Lena changes the title from "Story time" to "Reading for children". The address still ends in "story-time". Next to the field there are two buttons with icons. Their tooltips give their names:
- "Recalculate URL segment from page title" generates the segment again from the current title.
- "Toggle manual URL segment" unlocks the field so you can type the segment by hand.
A new address has a consequence: old links and bookmarks lead nowhere. If the system extension redirects is installed and automatic creation is active, TYPO3 helps. When you save, it creates a redirect from the old address to the new one. Subpages also get new segments and redirects.
Right after saving, TYPO3 shows a notification that slugs were updated and redirects were created. It offers two actions:
- "Revert update" undoes the whole slug change including the redirects.
- "Revert redirects only" removes only the redirects that were created, and the new address stays.
SEO and social media
The SEO tab comes with the system extension seo. It contains:
- Title for search engines: a separate title for the title tag that search engines display.
- Description: the description for search results.
- Robot instructions with the switches "Index this page" and "Follow this page".
- Canonical Link: the pointer to the original version when content is duplicated.
- The sitemap fields Change frequency and Priority.
If Lena switches off "Index this page", search engines are told not to include the page. In addition, the page drops out of the XML sitemap. "Follow this page", on the other hand, only controls whether search engines follow the links on the page. Nothing is deleted or hidden.
The Canonical Link tells search engines which address is the original when the same content exists under several addresses. If Lena points it to another page, search engines treat that other page as the original. Visitors are not redirected, and the content stays as it is. Without an explicit value, TYPO3 points to the page itself. A canonical link that is set also removes the page from the XML sitemap.
Priority says how important a page is compared with the other pages of the same website. The default value is 0.5, and you can choose values from 0.0 to 1.0. Change frequency is only a hint in the sitemap about how often the page changes, for example "Hourly" or "Daily". Neither field affects the cache, and neither can keep a page out of search engines.
In the Social Media tab you define how a shared link looks. There are two groups, each with a title, a description and an image:
- Open Graph for platforms such as Facebook and LinkedIn.
- X Cards, formerly Twitter Cards. Here you also choose the card type: Summary or Summary with large image. In the form they are labelled "Summary Card" and "Summary Card with a large image".
Metadata, Appearance and Resources
The Metadata tab contains the Abstract, the Keywords and editorial details such as Author Name and Last Update. Whether these appear in the frontend depends on the site package.
In the Appearance tab you choose the page layout, also called the backend layout. It defines which content areas, that is columns, exist in the Layout module. It is usually tied to its own frontend template, so it also changes how the website looks. You can change the layout at any time, not only when creating the page. It has nothing to do with the colours of the backend.
In the Resources tab you link media files to the page. What happens with them, for example a header image at the top of the page, is decided by the frontend configuration. You will not find content elements or translations there.
Behavior, Access, Categories and Notes
In the Behavior tab, spelled "Behaviour" in some guides, editors usually have little to do. Two areas matter:
- Under Caching you find the Cache Lifetime, which sets how long the rendered page stays in the cache. More on that below.
- Under Miscellaneous you find the switch "Include in Search". Advanced editors use it to exclude a page from the website's own search.
"Include in Search" affects the website's search. "Index this page" in the SEO tab affects external search engines such as Google.
The Access tab controls whether and when the page is visible:
- "Page visible" switches the whole page on or off. A hidden page cannot be reached by visitors at all.
- "Page enabled in menus" only hides the page in menus. It stays reachable through its address.
- Publish Date and Expiration Date control visibility by time. Before the publish date the page is invisible, and after the expiration date as well.
- Under Frontend User Group Access Rights you release the page only to certain frontend groups.
The Categories tab assigns categories to the page. Whether that has any effect in the frontend is up to the site package. By default nothing happens.
The Notes tab is for your own editorial notes, such as reminders or to-dos for the team. TYPO3 shows them in the backend, but never in the frontend. So they are not footnotes and not comments from visitors.
What the page cache does
Rendering a page for the frontend takes time and server resources. TYPO3 collects data from different sources and puts it together. That is why TYPO3 stores finished pages in a cache, a temporary store for results that have already been calculated.
When someone requests a page, TYPO3 first looks in the cache. If the page is there, the finished result is delivered right away. Otherwise TYPO3 renders it again and stores it for the next visitor. This way pages are delivered faster, and the server is relieved.
The catch: you only see a change once the cache has been cleared. TYPO3 clears the cache of a page automatically in these cases:
- You change something about the page itself, for example its title. TYPO3 then also clears the cache of the parent page and of the pages on the same level.
- You change content on that page, such as a text or an image, and save it.
- At regular intervals, usually once a day.
- Content with a start or end time becomes visible or invisible.
- In other cases that the integrator has set up.
The cache is not cleared when someone simply views the page, or when an editor opens it in the Layout module or logs out.
When a change is not visible
The automatic route only clears the cache of the page that changed and its direct neighbors in the page tree. All other pages stay as they are. This leads to three typical cases:
- New title in the menu: Lena changes the title "Story time". On the page itself everything is fine. The menu on the home page still shows the old title. The reason: TYPO3 cleared the cache of the page itself, its sibling pages and the Events page. The home page is one level higher, so its cache was kept.
- New record: Lena creates a new event as a news record. It is missing from the list on the Events page. Creating a record only clears the cache of the folder it is stored in. The page with the list stays in the cache unless the integrator has set something up.
- Content on many pages: Lena changes the phone number in the footer, which appears on every page. Many pages still show the old number because they still come from the cache.
Clearing one page. In the Layout module, the docheader has a button with a lightning bolt and the tooltip "Clear cache for this page". It clears the cache of exactly this page. In most installations that is harmless. In the first case Lena clears the cache of the home page this way, in the second the cache of the Events page. The content of the page stays, of course.
Clearing all pages. Using the lightning bolt in the top bar of the backend, you choose "Flush frontend caches". This clears the cache of all pages. Only users with the right permission see this button. If it is missing, ask your administrator. In the footer case Lena does this if she has the permission, otherwise Tom does.
A shorter lifetime. For pages whose content changes often, you set the Cache Lifetime in the Behavior tab under Caching. Besides the default value there are steps from 1 minute through 1 hour and 1 day up to 1 month. If the Opening hours page shows how busy the reading rooms are, updated every hour, Lena chooses "1 hour". Change frequency in the SEO tab does not help here, because it is only a hint for search engines.
Viewing without the cache. If you are not allowed to clear the cache, add the parameter no_cache with the value 1 to the address. TYPO3 then shows the page freshly rendered, the way it would look after clearing. The administrator can disable this parameter.
https://www.weidenau-library.example/events?no_cache=1The browser cache. Your browser also stores pages. If you cleared the cache on the server and still see the old version, the browser is often to blame. Do a hard reload: on Windows with Ctrl and F5, on a Mac with Cmd, Option and R. Or open a private window. It shows the page like a new visitor would see it. TYPO3 cannot clear other people's browser caches, and a private window does not clear the cache on the server.
The Admin Panel in the frontend
The Admin Panel is a bar at the bottom of the frontend page. It is not a backend module and not a dashboard widget. The extension is part of the core, but it is not active from the start. An administrator has to enable it. By default only administrators see it, but Tom can enable it for other backend users or groups. It then appears for those users when they are logged in to the backend and view the website. Normal visitors never see it.
Its main purpose is debugging. It also offers switches for previewing.
Even the closed bar shows key figures:
- For TypoScript, the number of messages.
- For Info, the load time of the page and the memory usage.
- For Debug, the number of errors and warnings, plus the number of SQL queries and how long they took.
Other controls:
- A link opens the current page in the backend ("Open page in backend"). Lena does not have to search for it in the page tree.
- The Settings entry with the cog holds the settings for Preview and Cache.
- When Lena opens a section such as TypoScript or Debug, there is another cog at the top right. It opens the settings of that section, such as the TypoScript tree display or the log levels in the Debug section.
- A switch at the bottom right of the bar turns the Admin Panel on and off for the page.
Info, preview and cache in the Admin Panel
Info. When Lena clicks Info, the General tab shows the document size, the page ID and the page type. It also shows the frontend user group, the cache status, the USER_INT objects and the total time it took to render the page. USER_INT objects are plugins that are rendered again on every request and can slow the page down. There is also a separate USER_INT tab with details. That mainly interests integrators.
Without a frontend login, the frontend user group shows the value 0,-1. That is the default and means nobody is logged in to the frontend, so the view without login applies.
Preview. Under Settings, in the Preview part, Lena controls what she sees in the frontend:
- "Show hidden pages" shows hidden pages.
- "Show hidden records" shows hidden records, such as hidden content elements.
- "Ignore start and end time" shows all time-controlled content, whether or not its period is running.
- "Simulate time" shows the page as it would look at a chosen date and time.
- "Simulate user group" shows the page as members of a particular frontend group see it.
All of these settings only apply to your own view. If Lena activates "Show hidden records", normal visitors see none of it. Hidden content stays hidden for them. The Admin Panel also does not change content, and it does not replace the page properties in the backend.
Cache. Also under Settings, in the Cache part, Lena can clear the cache of the current page ("Clear cache of current page"). With the right permission she can clear the whole frontend cache ("Clear frontend cache"). Or she switches off caching for her view ("No caching").
TypoScript and Debug are meant for integrators and developers. They show the loaded configuration, log entries and the SQL queries.
Key points
- You open the page properties with "Edit page properties" in the docheader or with "Edit" in the context menu. Which fields you see depends on page type, permissions and configuration.
- The page title appears in the menu and in the title tag. The alternative navigation title only changes the menu, and the subtitle only appears if the site package uses it.
- Renaming does not change the URL segment. The recalculate button, "Recalculate URL segment from page title", generates it again. With redirects, a redirect is created, and the notification offers "Revert update" or "Revert redirects only".
- SEO contains Title for search engines, Description, Index this page, Follow this page, Canonical Link, Change frequency and Priority with the default 0.5.
- Appearance holds the backend layout, Behavior the Cache Lifetime and Include in Search, Access the visibility and publishing dates, and Notes internal notes.
- Saving only clears the cache of the changed page and its direct neighbors. Menus further up, lists with new records and footers need manual clearing.
- "Clear cache for this page" clears one page, and the lightning bolt in the top bar clears all pages, but only with the right permission. After that, clear the browser cache if needed.
- The Admin Panel is a bar in the frontend that an administrator enables. It shows page ID, cache status and load time, simulates time and frontend groups, and only affects your own view.
Terms
- Admin Panel
- Bar at the bottom of the frontend for logged-in backend users, for debugging and previewing.
- Backend layout
- Page layout that defines the content areas in the Layout module and usually the frontend template.
- Cache
- Temporary store for finished results such as rendered pages.
- Cache Lifetime
- How long a rendered page stays in the cache, adjustable from 1 minute to 1 month.
- Canonical link
- Pointer that tells search engines the original version of duplicated content.
- Page properties
- Form with all settings of a page, split into tabs.
- URL segment
- Part of the address under which a page can be reached, also called slug.
- USER_INT
- Plugin that is rendered again on every request and is not cached.
- X Cards
- Preview cards for links on X, formerly Twitter Cards.