Wrong path for page TSconfig of backend layouts

Open
  • Is something wrong?
#1,572 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #1573 by @Hawkeye1909 — closed without merging

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

Inspect the imports under Configuration/TsConfig/Page/Mod/WebLayout/BackendLayouts and compare them with the expected Configuration/Sets/BackendLayouts/PageTsConfig/BackendLayouts path. Reproduce the issue through the Page TSconfig module and confirm that the syntax scanner no longer reports a missing file.

Written by the indexing model from the issue text.

Description

bug

Bug Report

Prerequisites

  • Can you reproduce the problem on TYPO3 v11.5 LTS
  • Can you reproduce the problem on TYPO3 v12.4 LTS
  • Did you perform a cursory search
    to see if your bug or enhancement is already reported?

Description

The import path for the page TSconfig of the backend layouts in folder Configuration/TsConfig/Page/Mod/WebLayout/BackendLayouts is wrong: Sets/ is missing...

Steps to Reproduce

  1. Include backend layout config either via @import in own file or via page settings.
  2. Open module "Page TSconfig"
  3. Select "Included page TSconfig"
  4. See error message/warning from syntax scanner like Import does not find a file in "EXT:bootstrap_package/Configuration/TsConfig/Page/Mod/WebLayout/BackendLayouts/default.tsconfig", line number "1"
Expected behavior

Import should work, thus the path should be like @import 'EXT:bootstrap_package/Configuration/Sets/BackendLayouts/PageTsConfig/BackendLayouts/default.tsconfig'

Actual behavior

Current import looks like @import 'EXT:bootstrap_package/Configuration/BackendLayouts/PageTsConfig/BackendLayouts/default.tsconfig'

Versions

Since v15.0.2 - commit 493e840 to be more precise...

Dominant language
PHP
Stars
354
Forks
209
Avg merge
1m
Merged PRs (30d)
2

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from benjaminkott/bootstrap_package

All issues in benjaminkott/bootstrap_package

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.