Skip to main content


Currently working through the #TYPO3 “Community Budget Ideas 2024 Q2” as a company. Discussing and submitting our votes.

I really like the democratic approach and would like to see the same for our society.


Peter Kraume :typo3: reshared this.


Nikita published version 0.6.0 of #TYPO3 extension content_blocks: https://github.com/nhovratov/content-blocks/releases/tag/0.6.0

Awesome progress, really looking forward TYPO3 v13 LTS. Give the extension a try within TYPO3 v12 already :)

reshared this



Sometimes the #IT job can be very frustrating. Our beloved #CMS #TYPO3 is moving to ShadowDom (WebComponents).
We have custom Acceptance tests via #WebDriver to cover functionality within the backend of the CMS.

Now ShadowDom support has landed in WebDriver. But at least Firefox seems to lack support for XPath selectors … But I am not aware of other selectors to find elements based on their text content …

And how is your day going?


AndreasKessel reshared this.


Just updated my website to #TYPO3 13.0.0 in order to test and report issues.

That also means my EXT:tracking is now compatible with v12 LTS and v13.0.0.
I'll keep it within a branch and verify with my website prior tagging new release.

in reply to Peter Kraume :typo3:

On the other hand the upstreams and community will profit :) It is your decision. I don't know timing, budget, etc.

Wish you all the best :)

in reply to Daniel Siepmann

Well, it's a private non for profit project but nevertheless it's overdue and expected to be ready soonish.

Peter Kraume :typo3: reshared this.


Nikita published v0.5.0 (none breaking) of EXT:content_blocks for #TYPO3 today: https://github.com/nhovratov/content-blocks/releases/tag/0.5.0

Thanks to him and all involved.

reshared this


Munich TYPO3 User Group (MTUG) reshared this.


Next #TYPO3 UserGroup in NRW: 29.01. at 18:30 Uhr at TYPO3 GmbH in Düsseldorf. Topic will be Roadmap of TYPO3 13 by @Luisa Faßbender.

reshared this


Kay Strobach reshared this.


I'm curious. Which #TYPO3 topics are you working on or interested in right now?

I'm currently in another update from 10 to 12. Invested some time in understanding ES6 JavaScript modules and how to use the TYPO3 modules within custom TypeScript for our own backend module.

in reply to Daniel Siepmann

it's also too much for me, so this'll be on my plate for a while. The AST/Tokenizer trip was very entertaining, hope to finish this with a un-influencad mind next week 😅

AndreasKessel reshared this.


Really motivating. Currently working on the #TYPO3 content-blocks extension to provide out of the box inline rendering. content_blocks allows easily create relations to other records. E.g. to content for tabs, accordion, slider etc. Or to other records like fe_users. TYPO3 already allows defining custom renderer for all types of records to provide a proper preview in TYPO3 backend.

Many thanks to Nikita who seems to be the main driver right now.

content_blocks will hopefully provide a ready to use rendering of those relations. Current progress (https://github.com/nhovratov/content-blocks/pull/73):

This entry was edited (2 months ago)

reshared this

in reply to Daniel Siepmann

Thanks. The photo was set to be private. I adjusted that, seem to work now. Thanks for reporting :)


Followup with learnings to my rant about #PWA: https://friendica.daniel-siepmann.de/display/3db7c7b4-1065-93cd-970c-145455374190

It is working right now. The issue seems to be #Firefox. I really love the browser, but it doesn't allow me to develop and debug ServiceWorkers and PWA properly.

Chromium on the other hand has all the necessary tools. Ensure to properly provide the scope to ServiceWorker registration in order to intercept network requests.
That last thing was missing. I use a CMS (#TYPO3) which will load assets from special folders. The folder itself will be the default scope of a service worker. A service worker only can intercept requests of its own scope. So adding the proper scope to registration fixed my last issue.

And Firefox still doesn't allow me to install the PWA on Android … But the service workers are running within Firefox is our real goal to allow users to use a part of the website while being offline on location is reached.


Sorry, but I need to #rant about this situation.

I'm a backend developer but couldn't find a #frontend developer to help me out. So I tried to get into #PWA on my own.
I head over to Mozilla Developer Network and everything looked so simple. I tried to convert my web app into a PWA and debugged via Firefox. But didn't get any issues, except it didn't work. I tried to find more help. MDN links to Microsoft and GitHub for concrete, way to complex, examples.
I turn on chromium to use lighthouse to get a proper report. That helps and I could fix some issues. Which accordingly to MDN would not be necessary.. But it now yells at me without concrete issues, and without concrete to dos.

Is this the modern internet? I learned the internet as a way where everyone with some free and open sources could put things on.

But it now feels like you need first to buy some knowledge from some closed source companies like Microsoft using closed source software in order to finally achieve something.

BTW: This project is not to make money, it is to help preserve memory of holocaust in Germany at a location where there is no mobile network. Therefore the project needs to work was PWA. https://buchenwaldbahn.de

Maybe someone can jump in a point me to a very minimal example that is working? Or other helpful sources or has some hints how to debug? Current status: I can't install the PWA. You can find current proof of concept here: https://tmp.daniel-siepmann.de/projects/

Lighthouse tells me it is installable. But Firefox doesn't allow me to install the PWA. How can I debug installation of PWA for #Firefox or find a linter, or something? And Chromium won't execute my service worker.



Mathias Bolt Lesniak reshared this.


Playing with #TYPO3 content blocks this week. And I don't want to life without them already.

You need to get used to something new, as often. But it is way easier, streamlined, no headache and just works.

It really is a pleasure to use TYPO3 that way. Even if you never complained about the old way.

Thanks to everyone involved. I'm really looking forward to see this "finished" and officially part of TYPO3.

reshared this