Security permissions for saving comment on a blog

[Colleen]

Hi

Just tried to comment on a blog and on save got this error...

blog was: https://blogs.sap.com/2017/08/13/more-voices-from-the-community-at-sap-teched-barcelona-2017/comment...

[jerryjanda]

"Securty."

*sigh*

OK, since this seems unrelated to the blacklist error, I'll see what might be causing it. I don't recall ever seeing it before. Then again, I don't recall seeing the "duplicate comment" error that Jeremy shared at https://answers.sap.com/articles/282579/status-updatestatus-updatedouble-vision.html either.

[Colleen]

Spelling mistake might make it easier to find root cause 😀

[jerryjanda · Accepted solution]

I'm at SAP TechEd Bangalore and out of touch with the things back at home, but thankfully, Capra informed me that this bug has been fixed. (See first bug fix at

https://wiki.scn.sap.com/wiki/display/WHP/SAP+Community+Release+Notes.)

[Colleen · Accepted solution]

jerry.janda - I saw the release notes. I'm glad Capra was there handling the communications.

[JL23]

Such question under the MM tag and I would answer "this must be a home made message, assumption made on the incorrect spelling of the word securty "

Ironically this message hits you who is a subject matter expert in the Security field

[Colleen]

hahaha I never noticed that. I double checked my own spelling to see if I made the mistake

After so long with career as carrier I don't notice missing vowels anymore

And yes, I was busy scratching my head thinking but I am security.... Realised I'm not securty

[Colleen]

Did the developers think the issue was the spelling mistake?

The error now reads "Comment can not be saved due to security reason."

I was replying to a comment against my own blog

[jerryjanda]

Hi, Colleen:

No, the spelling mistake was part of the ticket...but not the only issue in the ticket. The bigger issue is still under investigation.

And you're not the only one who noticed that the spelling was fixed. Jelena had her own thoughts about the text....

--Jerry

[jerryjanda]

FYI, IT opened a ticket for this particular bug and I'm told that it's resolved. If anyone still experiences, please let me know.

RE: the two other bugs in Jeremy's Coffee Corner post (https://answers.sap.com/articles/282579/status-updatestatus-updatedouble-vision.html) -- two tickets have been opened for these as well. I'm trying to get more info for there, although Audrey already made a comment about the double emails (which is an issue that requires a vendor to fix).

[Colleen]

Sorry Jerry

No dice - just got it again when I commented on https://blogs.sap.com/2017/08/17/improvements-coming-to-content-lists-in-your-profile/comment-page-1...

However, I did attempt a second time and it did post

[Jelena]

Yep, not resolved. Just happened to me when trying to post a comment in a blog. Did not do anything special, went straight to SCN, logged in, opened a blog, wrote a comment... aaaand it's gone. 😞

[jerryjanda]

You know, one of these days, and it may not be soon, I'm going to say that a bug has been fixed, and I won't have opened my mouth too soon. What a glorious day that will be.

So, yes, sorry, the ticket is still open. I'll continue to track it and provide (accurate) information when I get it.

I'm also told that the fix will include correcting the spelling of "securty." I realize that's the least of the issue (losing a comment is maddening), but it makes me wince.

[jerryjanda]

Sorry. The official mea culpa is above (in response to Colleen).

[jerryjanda]

You know, one of these days, and it may not be soon, I'm going to say that a bug has been fixed, and I won't have opened my mouth too soon. What a glorious day that will be.

So, yes, sorry, the ticket is still open. I'll continue to track it and provide (accurate) information when I get it.

I'm also told that the fix will include correcting the spelling of "securty." I realize that's the least of the issue (losing a comment is maddening), but it makes me wince.

[patelyogesh]

This issue is not resolved yet.

[jerryjanda]

Hi, Yogesh:

Yes, I know. I'm still tracking the bug ticket. Will give a little nudge that this remains an issue.

Best regards,

--Jerry

[Steffi_Warnecke]

Could this be connected to the info Audrey posted in the Moderator Jam group?

.

Regards,

Steffi.

[VeselinaPeykova]

I think it is more likely that this has something to do with SOC-5589.

[Colleen]

I only congratulated Eng in a comment so not sure how it could have been a blacklisted word.

[Steffi_Warnecke]

Ehm... darn, that's the one I actually meant. 😄 In my mind those two melted together. *g*

[Steffi_Warnecke]

Was it with "bad" words? 😉

Hmm... someone went a bit overboard with the filter, huh?

.

[Colleen]

also - this is in the blogs and not answers - does SOC-5589 only apply to Q&A?

[Steffi_Warnecke]

The blacklist filter seems to put out another message (see my comment above, I got the message for "n aughty". Funny enough "darn" is ok. ^^).

Or maybe they are not done implementing the same thing for blogs and this is the interim message? Checking the update logs, they say it's done for q&a and the CC.

[Colleen]

Maybe the blacklist was taken too literally to disallow n@ughty

[VeselinaPeykova]

You are right - it must be a different SOC, this one says (Answers)... but they are making some changes for blogs, even though it is not documented...

I have never encountered the message, which Jeremy posted in CC yesterday: https://answers.sap.com/articles/282579/status-updatestatus-updatedouble-vision.html