Shopware writes a ton of log messages. That is great if you’re looking for something, as you can be quite sure that it’s in there – somewhere.
But getting an overview and finding the right error message in 100 lines of log per request can be tricky, so highlighting helps.
Today I configured Ideolog to highlight *.log files with the shopware log format. There is no way to add microseconds and I didn’t get milliseconds to work either – until I restarted PHPstorm. So I guess you can have microseconds as well, but for me, it works fine without them:
| Message pattern | ^[(\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}).\d{6}+\d{2}:\d{2}]\s+(\w+).(\w+):\s+(.*)$ |
| Message start pattern | ^[ |
| Time format | yyyy-MM-dd'T'HH:mm:ss |
| Time capture group | 1 |
| Severity capture group | 3 |
| Category capture group | 2 |
And a blogpost about Symfony format recommended to add a Severity pattern with this nice format:
^\s*c(ritical)?\s*$Anyway, that does the trick.
If you have another working setup, feel free to leave a comment!
In one of our projects PHPStorm ran a while on 100% CPU, an investigation showed, that the process „checking for available composer updates“ ran and used all the resources. Most likely it got stuck somewhere. To get rid of the problem, one can turn off this feature. In IDEA Ultimate here: [Settings] -> Languages & […]
We all know custom fields – hopefully – at least this is not about the basics. You can add custom fields to nearly all entites: orders, products, categories, … You can name them whatever you like, e.g. pluginname.property – but using dots . in your custom field name is a bad idea, because then you […]
I was doing some work, when suddenly my git failed to commit changed. I dig a little around, asked StackOverflow but it didn’t help. Finally when running the commit manually and not through PHPStorm I got a proper error: Ah! The key is expired! Got it. Did you know you can extend a GPG key? […]
