@brotkrueml Thank you very much for the great instructions. This is useful for my v12/13 extensions.
To be able to structure TypoScript files better, I like to import entire directories that can contain several *.typoscript files. So far I have used the directories Constants/ and Setup/ under Configuration/TypoScript/.
Would you leave these directories there in future or also move them to Configuration/Sets/<Identifier>/?
@brotkrueml
The fact that these are TypoScript files, which have historically always been located under Configuration/TypoScript/, speaks against the move.
An argument in favor of the move is that the included files belong to the site set.
Finally, the question remains whether there are any technical problems if additional directories are created in the site set folder.
@danielsiepmann Good catch, absolutely right, thank you very much!
Although I went through the code several times, I overlooked it. strangely enough, the frontend output still delivered the correct image path 😆
@danielsiepmann I investigated this further and found out that all information after path:EXT:sitepackage/Resources/Public/ is transferred directly to the frontend output.
@Xitnelat Interesting objection. I currently have 5 websites on my home screen. Unfortunately, 3 of them don't have an app icon, which would make it easier to recognise them. They are websites that I visit frequently for various reasons. Precisely because we don't know how users use our website, we should incorporate these little things, especially if they hardly involve any significant effort. In the end, perhaps one user will be helped. You can also see it as a step towards accessibility.
Today is the last day for #TYPO3 Association members to vote for Q2 Community Budget Ideas - links were sent to you by mail - so don't forget to vote and if you like the #TransFusion extension, please give it the full 6 points! https://phpc.social/@ErHaWeb/112114116405861731
As several people have asked him for a presentation on different channels, here's a demo from our #Translation Handling Initiative Team Member Jo Hasenau showing you the latest features of the #TYPO3#TransFusion#Extension!
@danielsiepmann@ProvenPudding Yes, I love this uncomplicated, unbureaucratic way of using the association's funds. Communication and coordination take place directly with the community. The members have a direct influence. Applicants receive immediate feedback. I would like to see this form of funding expanded further. 👍
Frontenders often use <f:debug> to see available properties but then they can’t find the get/has/is functions that Fluid supports as properties. I’m experimenting with adding these to debugger output. Good idea?
The #TYPO3#Debug#ViewHelper in #Fluid sometimes confuses #integrators. Think of public getter without class property like FileReference::getProperties usable via yourFileRef.properties. Wouldn't it be better to list ALL information that can be used? What do you think?
@danielsiepmann First of all, I wanted to address the issue and get your opinion on it as I occasionally come across it when giving help in online forums. It's great that you already have an implementation for this 👍 I think it's a good idea to integrate this into the core sooner or later to improve the integrators' experience with the system. I don't see myself in a position to get something like this off the ground due to lack of time, but I support the idea to the best of my ability.
@danielsiepmann Another cool TYPO3 hobby project 😄. Unfortunately I already have so many of them. Hopefully there will be someone™️ else in the community who will take care of it. Your POC is definitely a good basis. I have at least created an issue for it https://forge.typo3.org/issues/102927
It was pretty easy to provide talks for user groups, camps, etc. when I was attending lots of them. Because I didn't need to prepare anything. I was into the topic and mood and could keep improving each talk.
But nowadays, I'm attending only two camps and way less user groups than the last years. That makes it pretty hard.
I now understand better why many people don't provide talks. But maybe we can also lower the expectations and barriers? Maybe provide a “safe zone” like an explicit track or announcement of “none prepared” talks?
@danielsiepmann Who has these expectations or creates barriers? For my part, I am very grateful at barcamps for any useful information, even if it is not given as part of an elaborately prepared presentation. A relaxed exchange about a topic is also usually helpful. I would like to see every presentation designated as a "safe zone" in this sense, in the hope that more experts will share their knowledge with the community, without hesitation, in any form.
@danielsiepmann It's great that you have high standards for your presentations, and it's also great that other speakers have high standards too. It's a blessing to not only have experts in the industry who share their knowledge, but do so with such dedication.
But at the end of the day, as a listener/session participant, I prefer information in a less prepared form than none at all 😉. No expert should feel discouraged from sharing their knowledge just because it doesn't fit the "expected" mold.
@danielsiepmann So am I not allowed to upload to TER if I'm not willing to take on that responsibility? What about Helmut's approach of recreating the library on every Travis build? Is that the solution?