Hey, so I haven’t had a good topic to blog about recently…
I have one in mind about log configuration options, but it’s not all that exciting…
Anyone have ideas for new blog posts?
1 Like
A blog article about Object and performance.
Recently I have a lot of performance issues in production about getting objects with headless WS.
I learn that generated WS Rest API do not use ElasticSearch and the performances are bad if you want to filter and paginate without anything in cache.
The solution is to use GraphQL, in this case if your Object is maked as indexeable, GraphQL use ElasticSearch and not the database !
I create a ticket to Liferay but no solution for me… i switch to GraphQL and now my calls are speed 
Hi Dave,
an article about Liferay testing (frontend, backend, services - you name it) would be highly appreciated. We just discussed this internally and I think one interesting aspect is what to test and how to decide which tests produce results that matter. Also, ideas for tools and procedures would be highly appreciated. Looking forward to your insights on this topic!
Andreas
Perhaps an updated blog for overriding JS content/features in Liferay?
I still have not managed to follow this Liferay blog post of Roselaine Marques which was for version 7.4.1, I think it was from 2020/21 (judging by comment dates)?
Basically it would be a blog post on overriding various JS features in the latest version of Liferay, perhaps with using Vite? In the linked blog post it was overriding features of Liferay commerce, which is what I was also trying to do.
@Christoph_Rabel this one is for you: Grouping Users in Liferay - Liferay
Hi David,
A great topic could be around best practices for development in Liferay – comparing traditional Java development, use of objects, client extensions, and other modern features. It would be really useful to see guidance on when to use each approach – especially in scenarios like migrating an existing project vs. starting a new one. That perspective would definitely make for a practical and insightful post.
Sure, I just liked the idea of being able to replace little bits of functionality that I didn’t like.
For me, in this instance, the Liferay commerce cart component is what I was wanting to target. It displays some content that I don’t want, and does not display some that I do want, which makes it appear to total things incorrectly.
For example, here is the summary at the bottom of the slide out cart component.
So there are a couple of things wrong (from my point of view) with the current implementation, some things I want to hide and some things I want to add.
I don’t want to show those discount fields giving customers the idea that they can get discounts (unless they did get a discount). I can hide those by CSS, though this would hide it even if they did get a discount.
You will also notice that the total does not add up. The current commerce cart does not show the sales tax, but does include it in its total, which would be confusing for a customer. (Probably a bug that might get fixed at some stage, but if I could have a way to relatively easily temporarily fix it, that would be useful.)
The original blog post looked like a promising/interesting way to get these changes made. I imagine there might be other small bits of functionality that you might like to alter. But yes, I guess it might tie the changes quite tightly to the current implementation, and might easily break. But it you are aware of that, it would seem simpler than making a whole new commerce cart component.
@Moozo you said:
It would be nice a blog about concurrency/ multi thread in Liferay. Each thread working on business Logic inside LocaleServices?
I’m wondering what is the context you’re looking for? I mean, just a background thread started by clicking on a UI element? A scheduled job that runs to do it’s thing?