Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Timeout message times out ... Why?
https://issues.liferay.com/browse/LPS-107574
A gripe since DXP began. The timeout messages timeout. Useless. What good is a timeout message that vanishes? Keep it visible. How are users supposed to know that their session timed out? Must they sit there and wait for it to time out to be informed it timed out?
The message should remain on the screen.
A gripe since DXP began. The timeout messages timeout. Useless. What good is a timeout message that vanishes? Keep it visible. How are users supposed to know that their session timed out? Must they sit there and wait for it to time out to be informed it timed out?
The message should remain on the screen.
Your forum post about timing out of timeout messages has just timed out.
Classy. So some cases the message stays visible. I think it's where the user would have a modal window open? Maybe, I mean who knows this thing is getting harder and harder to use and understand.
Also just read it. There are no buttons, there are however links. You also don't press it, you would click it or on mobile tap it. Aaaaaand if we really wanted to make a good experience for the user, when it goes red there would be a resume button????
How do you also "Please save any data you may have entered before refreshing the page." ... if the session has timed out, how are you going to save your work when half the interface no longer works? And at this point how can you redeem this experience if the user is about to loose a tonne of edits (which is why people write content outside of Liferay and copy paste it because you loose work if you don' t). QC stamped and approved and released. Passing, just copy paste something about this being expected, normal and ok. I don't think there is an X in DXP, if anything the X stands for "you're going to have a bad day", this is just getting less and less joyful as a product as old problems just stay there untouched, unloved, forgotten because effort is being expended on new features while there are still things broken from 4 years ago.
Like 7.0 was a wonder, it really was, it was brilliant. A unicorn perhaps.
Where are the UX people? What are they doing?
How do you also "Please save any data you may have entered before refreshing the page." ... if the session has timed out, how are you going to save your work when half the interface no longer works? And at this point how can you redeem this experience if the user is about to loose a tonne of edits (which is why people write content outside of Liferay and copy paste it because you loose work if you don' t). QC stamped and approved and released. Passing, just copy paste something about this being expected, normal and ok. I don't think there is an X in DXP, if anything the X stands for "you're going to have a bad day", this is just getting less and less joyful as a product as old problems just stay there untouched, unloved, forgotten because effort is being expended on new features while there are still things broken from 4 years ago.
Like 7.0 was a wonder, it really was, it was brilliant. A unicorn perhaps.
Where are the UX people? What are they doing?
Attachments:
Sorry for trying to add some levity. I did vote for your issue, btw.
David H Nebinger:
Sorry for trying to add some levity. I did vote for your issue, btw.
Heh, thank you. Also on clay ... the deprecation warning itself deprecated. Shifting sands.
Attachments:
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™