Add an example for `storagePid` set via TypoScript
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- php
- Domain
- documentation
Research direction
The issue names no file, so first search the tea repository for existing storagePid usages and any TypoScript setup that sets it, then decide where a new example belongs. The payload does not say what form the example takes, so confirm the expected output with the maintainers before writing it. Done means a documented TypoScript example of storagePid that a newcomer can follow to see it work.
Written by the indexing model from the issue text.
Description
This is helpful for learning extension development.
- Dominant language
- PHP
- Stars
- 92
- Forks
- 34
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 64
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TYPO3BestPractices/tea
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TYPO3BestPractices/tea#2460 ·
Maintainers usually reply within 1 day
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TYPO3BestPractices/tea#2458 ·
Maintainers usually reply within 1 day
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TYPO3BestPractices/tea#2457 ·
Maintainers usually reply within 1 day
-
runTests.sh
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TYPO3BestPractices/tea#2456 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TYPO3BestPractices/tea#2117 ·
Maintainers usually reply within 1 day
All issues in TYPO3BestPractices/tea
Similar issues
-
enhancement priority Sales
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
novalo-dev/Prestashop-MCP-Server#201 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Include flows spanning the full report time windowPossibly taken @somethingwithproof claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Cacti/plugin_flowview#306 ·
Maintainers usually reply within 1 day
-
bug origin: upstream priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mattytap/Mattytap-Sermons#105 ·
-
priority:low type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
crazy-goat/workerman-bundle#1189 ·
Maintainers usually reply within 1 day