t3olayout issueshttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues2024-03-15T15:33:32Zhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/668TYPO3 logo in the footer overflows its container2024-03-15T15:33:32ZJonas GötzeTYPO3 logo in the footer overflows its container@see https://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/645@see https://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/645https://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/667Contact form: Separate choice for account and data removal requests2024-01-23T09:21:29ZMathias Bolt LesniakContact form: Separate choice for account and data removal requestsThe form is currently missing this option. The address dpo@typo3.org has been set up and can be used for this purpose.The form is currently missing this option. The address dpo@typo3.org has been set up and can be used for this purpose.Mathias Bolt LesniakMathias Bolt Lesniakhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/664Integrate mission and vision parts for team pages2023-04-18T09:03:34ZThomas LöfflerIntegrate mission and vision parts for team pagesBoth has a short sentence and a longer description. In the backend there should be two text elements. In frontend the description should be extendable.Both has a short sentence and a longer description. In the backend there should be two text elements. In frontend the description should be extendable.Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/6633 column container re uses colPos 30 which is "normal"2023-01-16T08:50:43ZDaniel Siepmann3 column container re uses colPos 30 which is "normal"### Summary
The colPos 30 is re used for container child elements.
The result is that content elements within the container column are rendered twice, within the container and the normal column of the page.
### Steps to reproduce
1. C...### Summary
The colPos 30 is re used for container child elements.
The result is that content elements within the container column are rendered twice, within the container and the normal column of the page.
### Steps to reproduce
1. Create a page of Backend Layout "Team Page"
2. Create a Container "3 Column"
3. Insert content in third column "Right"
The content should appear twice. In Page module as well as in frontend.
### Example URL
https://typo3.org/community/teams/best-practices
### What is the current *bug* behavior?
Content is rendered twice on the page, with an unwanted position.
### What is the expected *correct* behavior?
The content of column "Right" of "3 Column" container is only rendered within its column
**Acceptence Criterias**
* [ ] The content element is rendered only within its container column.
### Relevant logs and/or screenshots
![image](/uploads/c13efde97192f319c9b479865574ca0d/image.png)
An Screenshod where Content Element "Łukasz Uznański" is placed in column "Right" of "3 Column" container.
It is rendered above the container as well. Same for frontend.
It is the same UID of the content element.
![image](/uploads/315227e86365b50df1780f885f497209/image.png)
(I've removed the other content elements from the screenshot for better overview).
### Possible fixes
https://git.typo3.org/services/t3o-sites/common/t3olayout/-/blob/main/Configuration/TCA/Overrides/tt_content_ce_ContainerElements.php#L121
Should also be an issue for other container elements.https://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/662Missing CSS class "container" on some <section> tags for CE2023-01-16T06:16:13ZDaniel SiepmannMissing CSS class "container" on some <section> tags for CE### Summary
Content elements have different spacing to top.
### Steps to reproduce
Create a new "Text" Content Element.
### Example URL
https://typo3.org/community/teams/best-practices (Currently hidden, log into backend to see hidd...### Summary
Content elements have different spacing to top.
### Steps to reproduce
Create a new "Text" Content Element.
### Example URL
https://typo3.org/community/teams/best-practices (Currently hidden, log into backend to see hidden page)
### What is the current *bug* behavior?
Content elements have different spacing to top.
### What is the expected *correct* behavior?
Content elements have same spacing to top.
### Relevant logs and/or screenshots
Might be related to #657?
Looks like css class `container` is missing on `<section>` elements under some circumstances? Leading to additional spacing to top. I could not see any field within the content element (backend user `layne.obserdia`, maybe I just don't have access to a special field?)
![image](/uploads/27ef38bc8a5efdd2f24c2c4da828ceec/image.png)
![image](/uploads/5e0a3914ecd59cb1471613f4b90163a0/image.png)Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/658How to integrate responsive menu2023-01-15T20:56:12ZOliver HaderHow to integrate responsive menu
Using `sidebar` to position a menu (right-aligned) next to content works on larger/desktop devices - however, when showing in smaller/mobile devices the menu is shown between other content elements, which makes it difficult to identify ...
Using `sidebar` to position a menu (right-aligned) next to content works on larger/desktop devices - however, when showing in smaller/mobile devices the menu is shown between other content elements, which makes it difficult to identify it as navigation component.
What's the proper/better way to provide sub-menu navigations on typo3.org that can be recognized as navigation component?
---
PoC: https://typo3.org/community/teams/security
Corresponding `sidebar` elements are highlighted in red in the screenshots below.
![Screen_Shot_2021-07-21_at_09.43.25](/uploads/7847353969839fb543f68b9427aae5e5/Screen_Shot_2021-07-21_at_09.43.25.png)
*backend wireframe view*
---
![screencapture-typo3-org-community-teams-security-2021-07-21-09_42_45](/uploads/979f4f575c418428dec4f9fdc4a9f324/screencapture-typo3-org-community-teams-security-2021-07-21-09_42_45.png)
*frontend view on small/mobile device*BacklogThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/657Introduce fullwith CE2022-09-13T14:09:40ZStefan BusemannIntroduce fullwith CEAs an editor I want to use content elements, with a full coloured background.
It should be capable to go fullwith and to contain different types of content. Next to that it must be possible to configure the backend to the colors or grad...As an editor I want to use content elements, with a full coloured background.
It should be capable to go fullwith and to contain different types of content. Next to that it must be possible to configure the backend to the colors or gradients of the styleguide
AC:
- [ ] Create a concepts for Introduce fullwith CE
- [ ] Create a ticket to implement the changes in the SASS / CSS and HTML Prototype
- [ ] Create a ticket to implement the integration via container elements and or content elements (frames)Backloghttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/656Add a consent solution2023-06-15T19:05:49ZStefan BusemannAdd a consent solutionAs a visitor of the website, I want to decide, which data about me are collected.
Relation with: https://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/645
AC:
* integrate a GDPR compliant banner solution (composer req dmin...As a visitor of the website, I want to decide, which data about me are collected.
Relation with: https://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/645
AC:
* integrate a GDPR compliant banner solution (composer req dmind/cookieman)Relaunch 2023Stefan BusemannStefan Busemannhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/652Add backend layout with right side menu, based on content structure2023-06-15T19:22:14ZThomas LöfflerAdd backend layout with right side menu, based on content structureExample page: https://typo3.org/project/association/contact/fields-of-responsibility
Using scrollspy: https://getbootstrap.com/docs/4.6/components/scrollspy/Example page: https://typo3.org/project/association/contact/fields-of-responsibility
Using scrollspy: https://getbootstrap.com/docs/4.6/components/scrollspy/_Ready for sprintThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/649Provide search results in the flyout menu2022-04-04T14:44:42ZStefan BusemannProvide search results in the flyout menuAs a visitor, I want to see search results, while I am typing in my search words
AC:
- [ ] Create a design, which fits into our current page
- [ ] Design is added to the stlyeguide / HTMLAs a visitor, I want to see search results, while I am typing in my search words
AC:
- [ ] Create a design, which fits into our current page
- [ ] Design is added to the stlyeguide / HTMLBackloghttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/647Layoutoption for section index (Feature Overview)2022-04-04T14:46:49ZStefan BusemannLayoutoption for section index (Feature Overview)As an editor, I want to use the content element "Section index" in a new layout option
![Content](/uploads/92ed648af3cc58c3adc4ca93b2c89592/Content.png)
AC
- [ ] Content Element "Menu - Section Index" offers Layout "with blue backgrou...As an editor, I want to use the content element "Section index" in a new layout option
![Content](/uploads/92ed648af3cc58c3adc4ca93b2c89592/Content.png)
AC
- [ ] Content Element "Menu - Section Index" offers Layout "with blue background"
```
<style type="text/css">
.metacatergory-feature-menu{
background-image: linear-gradient(99deg, #538bb3, #426f8f);
padding: 15px;
margin-top:50px;
}
.metacatergory-feature-menu-link{
color: #ffffff;
}
</style>
```
Current HTML Code
```
<div class="metacatergory-feature-menu">
<div class="container">
<div class="row">
<ul class="checked">
<li>
<a href="/cms/typo3-cms-new/features-draft/secure-performant-scalable/#c9215" class="metacatergory-feature-menu-link">Performance & Scalability </a>
</li>
<li>
<a href="/cms/typo3-cms-new/features-draft/secure-performant-scalable/#c9227" class="metacatergory-feature-menu-link">Security, Reliability, and Compliance </a>
</li>
<li>
<a href="/cms/typo3-cms-new/features-draft/secure-performant-scalable/#c9251" class="metacatergory-feature-menu-link">Site Management, Updates, Upgrades, and Administration </a>
</li>
<li>
<a href="/cms/typo3-cms-new/features-draft/secure-performant-scalable/#c9253" class="metacatergory-feature-menu-link">Hosting, System, and Environment </a>
</li>
</ul>
</div>
</div>
</div>
```Backloghttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/646Move news configuration and templates to t3org_template2021-08-19T13:24:03ZThomas LöfflerMove news configuration and templates to t3org_templateAs the news extension is only used on typo3.org website, we don't need to handle templates and configuration in t3olayout.As the news extension is only used on typo3.org website, we don't need to handle templates and configuration in t3olayout._Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/645Integrate usercentrics and remove default cookie banner2023-06-15T19:05:51ZThomas LöfflerIntegrate usercentrics and remove default cookie bannerRepository: https://github.com/TYPO3GmbH/ext-usercentricsRepository: https://github.com/TYPO3GmbH/ext-usercentricsRelaunch 2023Thomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/635New build chain with webpack2023-06-15T19:05:51ZBoris SchauerNew build chain with webpackNew build chain should use webpack.New build chain should use webpack.Relaunch 2023Boris SchauerpixeldesuBoris Schauerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/633Check for libraries to replace2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to replace_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/632Check for libraries to update2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to update_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/631Check for libraries to remove2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to remove_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/622Frontend Editing2022-04-07T06:59:57ZStefan BusemannFrontend EditingAs an editor I want to edit content in the frontend
AC
* Frontend Editing is installed
* Content Elements Supports editing
* News are editable
* events are editableAs an editor I want to edit content in the frontend
AC
* Frontend Editing is installed
* Content Elements Supports editing
* News are editable
* events are editable_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/621Processed/compressed image resource are not used on client device2022-04-04T14:46:50ZOliver HaderProcessed/compressed image resource are not used on client devicee.g. https://typo3.org/article/recap-of-the-combined-sprint-of-typo3org-and-server-team/
Independent of which screen resolution or device simulation is used, the full fallback image is downloaded (Google Chrome Version 76.0.3809.100 on ...e.g. https://typo3.org/article/recap-of-the-combined-sprint-of-typo3org-and-server-team/
Independent of which screen resolution or device simulation is used, the full fallback image is downloaded (Google Chrome Version 76.0.3809.100 on macOS). I'm experienced the same on a native iOS device (iPhone & iPad) connected with 3G.
By looking at the responsive images part, it becomes obvious that no image processing is happening. All source-sets deliver the same original image.
> I guess image processing is not configured properly on typo3.org, most probably the settings for a development container are different to the production website which is not reflected in `.env` or `AdditionalConfiguration.php`
```
<picture>
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 1200px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 992px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(min-width: 768px)">
<source srcset="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" media="(max-width: 767px)">
<!---Fallback--->
<img class="img-fluid" title="TYPO3.org- and Server-Team" src="/fileadmin/t3o_common_storage/news/2019/05/2019-05-22-Combined-Sprint-Stuttgart-Team.jpg" width="3095" height="2060" alt="" />
</picture>
```
![Screenshot_2019-08-15_at_17.39.34](/uploads/f34ccc5374f58332866548e61d65f4e8/Screenshot_2019-08-15_at_17.39.34.png)Backloghttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/620Restructure and separate templates/partials/layouts from page and content ele...2022-06-16T10:13:59ZThomas LöfflerRestructure and separate templates/partials/layouts from page and content elements<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Look for all Fluid files wh...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Look for all Fluid files which are used by pages and content elements.
Then put all files into the folders they belong to.
Currently the file `Layouts/Default.html` is used by content elements and pages.
### Steps to reproduce
Put HTML code to `Layouts/Default.html` (which should handle pages only).
The HTML code appears on every content element as well.
### Example URL
(Add an Url where we can see the issue)
### What is the current *bug* behavior?
One layout file used by page and content elements
### What is the expected *correct* behavior?
Separate layout files and make it more clear which file is used for what.
**Acceptence Criterias**
* [ ] Clear structure for page templates
* [ ] Clear structure for content element templates
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)_Ready for sprint