Posts of category: TYPO3 CMS
In the future I would collect the best and most useful articles/websites collect in a list to hold on the one side my list of read articles small and maybe it helps someone on the other side. If anyone even reads my blog. Which I am not assuming.
So let’s start:
- Xdebug or actually the sponsoring page from Derick, who is the maintainer and inventor of the best debug tool for PHP. Go! Support! Because also developer want to earn money.
- TYPO3 Rector: actually I wanted to use my vacation for a lot of learning and looking about things over the holidays, but sometimes it happens different. I will use it for the next refactoring/migration and will report about it.
- Laragon: I am a strong advocate of DDEV for a server environment for local development with TYPO3. Laragon apparently wants to be something like that. Unfortunately I haven’t seen it yet, because I’m more than satisfied with DDEV.
- A nice “Everything was better (different) before” article about OpenSource development: The Golden Age of Open Source is Over
In the last year which is not allowed to be called by name, I had so many plans and really achieved only a little bit of it. Because I'm doing something wrong (or different) than everyone else who was also in the home office and felt had have always leisure time or at least were so deeply relaxed, that I have started with meditation in the later summer to get to the same level. The meditation I've given up fast because that is a thing that just doesn't work for me. Apparently you have to believe in it just like with homeopathy, and that's just not what my brain is made for.
I didn't get into blogging as I had planned. Just write texts. For me. And put them on the Internet. For whatever reason. Because that's how it was done in the early times of the Internet. Where the internet wasn't quite as broken as it is today.
Maybe I'll even publish a blogroll here soon, because it there is it still there! The little blogosphere and also the tech bloggers. But I will start with a selection of articles and websites that I saved in Pocket last year and forgot. Of the almost 300 entries I will left these here, maybe one or the other will find something that will help them.
- patternlab.io: Pattern library for the documentation of design elements in web design- storybook.js.org: Pattern library for React, Vue and Angular, as well as other frameworks
- Design-Systeme mit Fluid umsetzen: Blog article on using Fluid to represent a design system
- Frontend File upload: File upload in the frontend for TYPO3 8 and 9
- Error management mit Sentry: Application monitoring with sentry.io, Integration in TYPO3
- Rector für TYPO3: Automated migration of legacy code, actually indispensable, Rector auf GitHub
- PSR-14 Events in TYPO3: Nice post about using events and listeners in TYPO3
- ddev für TYPO3 anpassen: there you will definitely find a few delicacies to look at
- 20 Most Common TYPO3 Errors (And How to Fix Them): Who doesn't know the error messages that TYPO3 can throw at you
- The Best Guide to TYPO3 Composer: no idea why you should even set up TYPO3 without composer
- Fully integrate DDEV and PHPStorm - including Unit Tests with Coverage: I've wanted to try it out for a long time, fire tests directly in PhpStorm in DDEV
- Validating site config of TYPO3: proof of concept validating the TYPO3 site configuration
- Integrating PHPStan in PHPStorm / PHPStan Pro
- Deploy TYPO3 with Surf and GitLab CI: Base of my script that I am currently using for deployment
- OWASP ZAP: Scanner to check web apps for various vulnerabilities
- From Dev to Prod with GitLab CI - Stephan Hochdorfer - PHP UK Conference 2019: Prasentation about the use of GitLab CI (unfortunately not yet seen myself)
- GitLab CI for building and deploying TYPO3 websites with deployer: Deployment receipt from spoonerweb to get TYPO3 onto the target system using a deployer
- TYPO3-Projekt Buildchain mit Gilab-CI: a lot of cool stuff to check out
- TYPO3: Migrate fluid pagination widget to paginator API
- Data Transfer Objects in Extbase
- Rector: Automated migration of legacy code
- blackfire.io: PHP application performance testing
- Is Your Code Up To Sniff?: Blog article about using PHP CodeSniffer and PHP CS Fixer
Programming in general
- Develop, Debug, Learn? A time to re-think our tooling.: interesting article about using our everyday tools
- Learn regex the easy way: I hate regular expressions
- Softwarequalität wird nicht bezahlt: Blog article about who should pay the extra work for good code
- Let's Program Like It's 1999 | Lee Byron: Nice to watch lecture on how web development has (not) changed
Update: With release of TYPO3 10.4.8 the problem is gone because the dependencies were adjusted. Apparently there were problems not only with Surf, but also with Solr and dependencies on PHP 7.2. Nevertheless, I will not install Surf with composer in the project, but instead globally in the DDEV container.
Yesterday a planned maintenance update of TYPO3 was published. Version 10.4.7. The best content management system that I know. And of course all projects should get the new version. What was previously possible without any problems with a hearty 'composer update' without any other effort. Just not yesterday.
composer absolutely refused to integrate the new version into the projects. Okay, no problem, let us approach the whole thing systematically. First with
composer clear-cache && composer update
force composer to forget everything, go through all the sources and try again. But this did not bring any new TYPO3 onto the hard drive.
Then I would look around and with the question
composer why-not typo3/cms-core:10.4.7
it became clear that typo3/surf has a dependency with symfony/console which finally has a dependency with symfony/event-dispatcher-contracts that prevented going to a larger version than 2.0. But what typo3/cms-core absolutely requires. npm, what the hell!
This morning I tried another time to find a solution but maybe I should think about another job in my elderly age. So there was only Twitter left, my grief complained and minutes later the two heroes @t3easy_de and @chriwode came around the corner.
The first attempt to run Surf locally on Windows failed miserably. Yes, Windows. I don't want to talk about that here. The whole thing fails because, among other things, Windows does not know awk and even if you install this, you will be hit with further errors.
To get to the point: so far I have setup projects using DDEV and not only installed TYPO3 and the extensions used via composer, but also Surf. In order to be able to deploy a project via the command line, for example, if no corresponding CI/CD system is available. My solution now looks like this: Surf has removed of this composer.json and is installed globally via the DDEV start hook:
hooks: post-start: - exec: composer global require hirak/prestissimo - exec: composer global require typo3/surf:^2.0
So TYPO3 10.4.7 can be installed and I can move the project to another system via surf.
There are investigations for everything. Also for how the loading time of a website affects the possible bounce rate of the visitors. And it's hard to believe, but the bottom line is that the longer it takes a website to load, the higher the chance that the visitor will close the tab. Incredible.
The AssetCollector has been integrated with TYPO3 10.3. With this, scripts and stylesheets in Fluid files can be added to the rendering process with the ViewHelpers f:asset.script and f:asset.css. They behave similar to the renderAssetsForRequest already added in 8.6, with which you could render the corresponding code via the two Fluid sections HeaderAssets and FooterAssets.
But with the simultaneous use of HTTP/2, which ensures that the resources for rendering the website are delivered to the browser before it even knows that it needs them, a speed advantage is still achieved in conjunction with the small data size and is especially noticeable in a faster rendering of the page. It is not at all bad that the resources are not integrated into the concatenation or compression process of TYPO3, as you were used to when you integrated your resources using TypoScript.
And so you have already made a few more visitors to your website happier.
And yes, I know, I have unfortunately not yet activated HTTP/2 on this page. It's not me. I'm sorry.
I always plan to do more with this blog. To tell something and perhaps give some input to others that will help them. Like the other tens of thousands of blogs and websites I can learn from every day.
The past few weeks I have been quite offline during my free time. We have build a new terrace, which was already planned when we moved into this house a few years ago. At that time, I just didn't think we would do it all alone.
Next to building and plastering a wall (at least 3,5 x 2 m in size), the extraction, the gravel, pulling of the grit and cutting the plates I've learned that there is simply no need to ask a craftsmen. If you ask how to do one or the other, you get two or three answers which are obsolet one week later. Almost like developers.
And then I taught myself how to solve a Rubik's Cube. My little son brought them in and actually wanted to learn it too. Because I can't help him, I had to have learn it by myself and so I can now solve the cube in a little bit over two minutes with the beginner method. If I will learn other algorithms to solve it in under a minute... I do not know yet.
I will start learning again for the certification of a TYPO3 developer (TCCD). I was able to extend the TCCI certification by one year last Friday, whereby I think that the procedure is worth considering. Just because I took part in a presentation of the innovations of TYPO3 10, which I held in my department in a similar way shortly after its appearance, I have collected a lot of suggestions, but I don't master them. Perhaps this is because I was one of the last ones where the certification is normally valid for three years, the new certificates are only valid for two years.
For the preparations I work through the Exam Study Guide for the Official TCCD Certification of the TYPO3 Association (https://leanpub.com/typo3certifieddeveloper-en) and this time I decided for me to write a blog post for each topic or question that I don't answer correctly when I was studying, in which I then work on this topic. The best way to learn is to write a cheat sheet. There will definitely be some posts. ;-)