2

Fucking retard Liferay.....

At least 2 users (one inour team and another at client's) are claiming they've successfully opened a portlet view multiple times at day X. And a month later it stopped working.

I open up Liferay's (tomcat's) localhost_access.log and can see all the portlet requests at day X have returned http:400

Normally I would consider the human factor and rule this as a human error, assuming they were connected to another environment, another server, etc. But since this is The Fucking Liferay - I'm not that fast in trusting even logs :(

Who the fuck made this piece of shit....

Comments
  • 1
    @kescherRant I mean I already have a splitting headache.... Haven't had one for months. Haven't been "doing liferay" for months. I mean that can't just be a coincidence..

    I think I should list Liferay in the "Allergies" field next time I'm going to teh doctor...
  • 1
    Seems to be a thing recently. We have an API on tomcat we routinely call that returns the payload, with a 403 status code. They won't fix it because, "it just the dock-oo-ment, it fine." Imagine if all the competent people got together one a single team 😆
  • 0
    @kescherRant are you referring to lifeway?
Add Comment