MCP in Practice for TYPO3Episode 7 · Chapter 2: Ask and edit · 1:00

Schedule TYPO3 pages and short-lived redirects from chat

One request on our demo install sets a start and an end time on a hidden TYPO3 page and adds a short link /winter for the same window, in one batch after a dry run. The page and the link went live and expired on time; menus on cached pages needed a cache clear; one undo put it all back.

Read the full guideAll videos
The prompt in this videoPut our Winter Collection page live in a few minutes and take it down again ten minutes later. Add a short link /winter that points to it only for that time. Dry run first.
Transcript: every screen and subtitle
  1. 0:00MCP in Practice for TYPO3 · Episode 7: Schedule TYPO3 pages and short-lived redirects from chat
  2. 0:02The request: Winter Collection live at 13:02, down at 13:12, plus a /winter short link. Dry run first.
  3. 0:05The step list names the connector: AI Universe Demo.
  4. 0:07The first dry run is rejected, nothing is written. Claude retries, then applies.
  5. 0:09Read back: the page is visible 13:02 to 13:12, with the short link /winter.
  6. 0:12A temporary 302; the hidden flag is off, the end time expires the page.
  7. 0:14Now check it in TYPO3.
  8. 0:15The page tree: Winter Collection now carries a timer icon.
  9. 0:24Access tab: Publish Date and Expiration Date are set, Page visible is on.
  10. 0:32Redirect Management: /winter with status code 302 and a timer icon.
  11. 0:40On the website before the start, the page answers Page Not Found.
  12. 0:45At 13:02, /winter leads to the Winter Collection page.
  13. 0:50Schedule and short link, from prompt to answer, instead of setting start and end times and a redirect by hand.
  14. 0:52Read the post: t3planet.de/en/blog/typo3-schedule-pages-and-redirects/
The postSchedule TYPO3 pages and short-lived redirects from chatRead the post
In this video
Questions

Questions about this video

What does this video show?

One request in Claude on our demo install: put the Winter Collection page live at 13:02 and take it down at 13:12, with a short link /winter for the same window, dry run first. The first dry run is rejected and nothing is written, then the change is applied. Then the video shows the timer icon in the page tree, the Access tab of the page properties, Redirect Management and the website before and at 13:02.

Why is the redirect a 302?

The short link is temporary. A 302 tells browsers and search engines not to treat the move as permanent.

Why did the menu not show the page at once?

Pages cached before the start time kept their old menu. A page cache clear after the start time brought the new page into the menu.

Episode 7

The other video of this episode

Previous and next

More videos

All videos