Having "fun" with Khoros editor failures

[waclawek.jan]

The "member callout bubble" remained stuck even after having made the post i.e. editor pane closed. It overlaps the post and scrolls together with it.

Oh yes, reload "fixes" it, but ain't it a hillarious fail?

JW

Hi @waclawek.jan 

Thanks for your feedback, we are investigating this issue.

Michael

Hi @waclawek.jan ,

Unfortunately we were unable to replicate this issue. Please let us know if you experience it again.

Adam

[Tesla DeLorean]

Perhaps it is Browser or System related?

[waclawek.jan]

Hi @unknown ,

> Please let us know if you experience it again.

And then happens what?

JW

Hi @waclawek.jan ,

We will investigate it again.

Best,
Adam

[waclawek.jan]

@unknown,

Here you are:

 

JW

[Tesla DeLorean]

@waclawek.jan not meaning to hijack thread, but the code or JavaScript nonsense behind the dialog and page rendering needs a good review and understanding. Hopefully by focusing resources on blatant failings in this area of Khoros' implementation we can get resolution of multiple issues.

Also perhaps the slowness and kitchen-sink approach of the editor dialog, which takes forever to load and come ready enough for me to type content.

[Tesla DeLorean]

For the love of god we need to get the User Call out to work effectively for 60000 users, not fking 6 !!!

There's no scroll, there's no wild card, it's almost entirely useless. It matches stuff not typed, and it's very difficult to get the exact sequences to find users you know are in the system but unsure of exact spelling or punctuation..

[Tesla DeLorean]

I get odd caching update behaviour. I type "lina d" I get 5 bad guesses, I type "lina da" I find the user I want, then subsequent start with "lina d" comes up with the right suggestion. Initial typing of AT gets me a list of posters more localized to the thread, and while this makes some sense, pulling in other more experienced or specific users is appropriate to get eyes/attention on a thread.

I do find this all a bit hit-and-miss, and gravely limiting for a forum exceeding 60,000 users, and trying to narrow with the first 3 characters. I need this to be a lot smarter and more intuitive. Instead I've got a solution that misses the mark by four orders of magnitude in terms of scaling to problem.

[waclawek.jan]

> Hopefully by focusing resources on blatant failings in this area of Khoros' implementation we can get resolution of multiple issues.

No. ST nor Khoros do care. They just make small and easy changes to placate us (and that's not just the forum).

Honestly, through this and several other threads, I just entertain myself. I've gave up on trying to help ST to get their act together when they chose to ignore the list of basic and substantial defects we told them just at the beginning of the Khoros era.

JW

[waclawek.jan]

Btw. +1 on @Tesla DeLorean 's sentiment, the whole callout  is a mess. I figured up to first 3 characters the participants of current thread are referred regardless of name match, but after that there's just "magic" picking up from the database; and editing (deleting etc.) the typed in name results in havoc, as you've said.

Oh, and the original bug is easy to reproduce: just keep the callout bubble open when clicking on Reply. That much for the effort paid to investigation.

JW

@unknown  @somerandomname

 

[waclawek.jan]

 

[Tesla DeLorean]

@Trying to replicate

[Tesla DeLorean]

[Tesla DeLorean]

Sticky too, the red is where it was left after replying to thread with call-out open, clicking Reply. Chrome on Win10

Green boxing for clarity, outlines of my images so as not to get confused with post

[Lina_DABASINSKAITE]

Hi all, 

This issue is identified as BUG and is being tackled by the platform Engineering team. I will notify once the issue is resolved. Apologies for the inconveniences you are all currently facing.

Regards,
Lina

[waclawek.jan]

A similar one (the dangling "Numbered list" bubble remained there errorneously after making the post, and now moves together with that post when moving the thread up and down).

Yes, the underlying reason is always the same: overcomplicated solution not fully understood by the authors. Many such problems would be solved by simply reloading the thread after making the post, instead of just inserting it ajaxy style.

Do you still insist on refusing inviting Khoros people here to share the shame?

JW