fgtclb/page-backend-layout

Helper for Backend layout overrides based on page doktype

2.0.1 2025-04-03 14:47 UTC

Requires

• php: ^8.1 || ^8.2 || ^8.3 || ^8.4
• typo3/cms-backend: ^12.4 || ^13.4
• typo3/cms-core: ^12.4 || ^13.4
• typo3/cms-fluid: ^12.4 || ^13.4

Requires (Dev)

• friendsofphp/php-cs-fixer: ^3.14
• phpstan/phpstan: ^1.10
• saschaegerer/phpstan-typo3: ^1.8
• typo3/cms-info: ^12.4 || ^13.4
• typo3/cms-lowlevel: ^12.4 || ^13.4
• typo3/cms-tstemplate: ^12.4 || ^13.4

GPL-2.0-or-later

README

TYPO3 extension page_backend_layout

This extension provides a simple possibility of adding basic information to the backend page view of TYPO3.

It is useful for giving information about page related information on top of the view without editing the whole record. A ViewHelper is added for rendering images into the view.

Installation

Install with your flavour:

• composer
• TER
• Extension Manager

We prefer composer installation:

composer req fgtclb/page-backend-layout

	URL
Repository:	https://github.com/fgtclb/typo3-page-backend-layout
Read online:	https://docs.typo3.org/p/fgtclb/page-backend-layout/main/en-us/
TER:	https://extensions.typo3.org/extension/page_backend_layout/

Version support

Page Backend Layout Version	TYPO3 Version	PHP Version
1.x	11 + 12	>=7.4
2.x	12 + 13	8.1, 8.2, 8.3, 8.4

Create a release (maintainers only)

Prerequisites:

• git binary
• ssh key allowed to push new branches to the repository
• GitHub command line tool gh installed and configured with user having permission to create pull requests.

Prepare release locally

Set RELEASE_BRANCH to branch release should happen, for example: 'main'. Set RELEASE_VERSION to release version working on, for example: '0.1.4'.

echo '>> Prepare release pull-request' ; \
  RELEASE_BRANCH='main' ; \
  RELEASE_VERSION='2.0.0' ; \
  git checkout main && \
  git fetch --all && \
  git pull --rebase && \
  git checkout ${RELEASE_BRANCH} && \
  git pull --rebase && \
  git checkout -b prepare-release-${RELEASE_VERSION} && \
  composer require --dev "typo3/tailor" && \
  ./.Build/bin/tailor set-version ${RELEASE_VERSION} && \
  composer remove --dev "typo3/tailor" && \
  git add . && \
  git commit -m "[TASK] Prepare release ${RELEASE_VERSION}" && \
  git push --set-upstream origin prepare-release-${RELEASE_VERSION} && \
  gh pr create --fill-verbose --base ${RELEASE_BRANCH} --title "[TASK] Prepare release for ${RELEASE_VERSION} on ${RELEASE_BRANCH}" && \
  git checkout main && \
  git branch -D prepare-release-${RELEASE_VERSION}

Check pull-request and the pipeline run.

Merge approved pull-request and push version tag

Set RELEASE_PR_NUMBER with the pull-request number of the preparation pull-request. Set RELEASE_BRANCH to branch release should happen, for example: 'main' (same as in previous step). Set RELEASE_VERSION to release version working on, for example: 0.1.4 (same as in previous step).

RELEASE_BRANCH='main' ; \
RELEASE_VERSION='2.0.0' ; \
RELEASE_PR_NUMBER='123' ; \
  git checkout main && \
  git fetch --all && \
  git pull --rebase && \
  gh pr checkout ${RELEASE_PR_NUMBER} && \
  gh pr merge -rd ${RELEASE_PR_NUMBER} && \
  git tag ${RELEASE_VERSION} && \
  git push --tags

This triggers the on push tags workflow (publish.yml) which creates the upload package, creates the GitHub release and also uploads the release to the TYPO3 Extension Repository.