Sudden red "topic not available" message

[waclawek.jan]

I was typing a reply to a post, when suddenly the following red message appeared (before taking the screenshot, I erased the relatively short text I had already typed there):

After reloading, the thread had a post from other user, which was not there previously. However, I've encountered previously that threads I was commenting on had seen comments from other users meantime. Also, the text of that message nor its appearance (red = something went very wrong) does not reflect this event.

JW

[Andrew Neil]

There's one post in that thread which has been edited:

https://community.st.com/t5/stm32cubeide-mcus/debugging-call-hierarchy-wrong/m-p/651884/highlight/true#M25250

could it be that you caught it "mid edit" ?

:thinking_face:

[waclawek.jan]

Maybe; but that still does not mean I should be scared by a red message which basically does not tell the truth anyway...

JW

[Lina_DABASINSKAITE]

Hi @waclawek.jan , 

Thanks for reporting this. I am  looking into this to see what caused the error message. I will get back with more news once clarified. 

Regards,
Lina

[Andrew Neil]

Maybe unrelated, but it seems that the name/title of that thread was changed at some point?

This seems to be confusing the notification emails - which sometimes use the old title, and sometimes use the new one!

 

[waclawek.jan]

> name/title of that thread was changed at some point

Aaaaah now I understand...

Changing opening post's subject changes the URL; not only the "string" portion of it, which is apparently ignored by the server (you can try e.g. this very thread can be invoked by https://community.st.com/t5/feedback-forum/blah-blah/m-p/652679 or https://community.st.com/t5/feedback-forum/mumbla-bumbla/m-p/652679 etc.), but there the "number" changed, too, i.e. internally the original thread probably ceased to exist.

Quite a nasty one. I wouldn't want to be the poor lad in Khoros who's going to be assigned the task to fix this.

JW

 

[Tesla DeLorean]

Yeah Khoros ain't fixing anything..

ST really needs to get some penalty clauses in their contracts so their suppliers are motivated to fix problems and deficiencies in a timely manner.

Swimming upstream in molasses.. 

[Lina_DABASINSKAITE]

Hello @waclawek.jan , 

Getting back to you here. The screenshot shows that when you tried to post the comment, the topic was posted on STM32 MCUs products and it's on STM32CubeIDE (MCUs) now. The process of moving the topic began when you tried to post it. This scenario matches the error that occurred when you took this action.

Hope it helps! Let me know if you have any questions or notice similar behavior in other scenarios. 

Regards,
Lina

[Andrew Neil]

I've had a couple of these recently

[Lina_DABASINSKAITE]

Hello @Andrew Neil , 

Can you share the links of those threads you faced the issue? 

Thanks,
Lina

[waclawek.jan]

Hi @Lina_DABASINSKAITE ,

So, you just declare it being a feature, rather than a bug.

I see.

It is was a very confusing experience. Now, I'm seasoned through years of experiencing crаp software instead of proper forum here, but consider what impression does it leave to the uninitiated.

JW

[Andrew Neil]

Another one just now:

https://community.st.com/t5/microcontrollers/seeking-guidance-establishing-spi-communication-between/td-p/661720 

[waclawek.jan]

Note, that the link in your screenshot is different:

https://community.st.com/t5/stm32-mcus-products/seeking-guidance-establishing-spi-communication-between/td-p/661720

so some moderator probably moved the thread to different "subforum", and the red message is likely to be a consequence of that.

Yes, it's very annoying bug, clearly stemming from lack of Khoros' experience with real fora.

JW

[Andrew Neil]

This one was annoying because I did lose all I'd typed.

:frowning_face: