Skip to Content
author's profile photo

This blog post was published!?

I got this feedback message after commenting on Werner's blog post.

Now, we can get into semantic discussions about whether it's still the same blog post after it was commented on or not, but my simple end-user expectation would have been:

1. my comment appears somewhere after the end of the blog post

2. that's it. No additional feedback message required if everything worked fine.

I'm not going to scour the website for finding the "correct" feedback channel once again but leave this here. Whoever feels responsible/interested in the SCN development team can just find this right here.

* Please Login or Register to Comment on or Follow discussions.

5 Comments

  • Dec 26, 2019 at 11:07 PM

    Already discussed number of times, latest here: https://answers.sap.com/questions/12931116/blog-published-message-when-posting-a-comment-its.html

    P.S. And to my mind, Coffee Corner is not the right place for bug reports... SAP Community tag is a correct place.

  • Dec 27, 2019 at 01:45 PM

    Hi Lars,

    your comment makes sense. it' not always true, but comments can add more value than the original post and become the main draw for that original post. it doesn't subtract from its value, but rather complements it. coffee corner works in a similar fashion, a comment refreshes the original post and puts right on top. it's a bit confusing but not necessarily a bug when the blurp remains from the original, that hasn't changed, together with the name of the person who made the last change, but i think one can get used to it.

    cheers and happy 2020,

    greg

    P.S. in my mind, (hash)tags are free form. they can help, but should not be mandatory.

  • Jan 02 at 04:18 PM

    As Vadim noted, it's actually an old bug. This seems to happen intermittently and so far SCN team stated they cannot reproduce it. I don't see any pattern, there was nothing special at all about how my comment was posted. If I was a developer, I'd look at the conditions that trigger this message. It should not be displayed to anyone other than the blog author, so even if I had trouble finding the exact root cause it shouldn't be super hard to patch.

  • Add comment
    10|10000 characters needed characters exceeded