Skip to Content

[Status update] Like beating my head against a wall....

...except, beating my head against a wall will eventually lead to knocking myself out and stopping. However, I just keep coming back here hoping things get better/change/fix while also trying to tell others to be patient as well.

Today, I hit the following for about the 4th time in the past week or so....I make a response/post to some thread/blog....quite long and takes time.....click "submit".....and viola.....following error and all work lost.



I guess I should know better and go back to creating in a Word doc and then cut-n-paste, but you know....I was being foolish and just expected it to work fine. ARGGGG!!!

(*if it helps....for whatever reason....I was logged into the SAP Learning Hub (authenticated there) ...then came to SCN (with same credentials)....and this happened. This should NOT matter in the slightest but who knows.)

capture.jpg (20.3 kB)
* Please Login or Register to Comment on or Follow discussions.

27 Comments

  • Aug 24, 2017 at 07:07 PM

    I'm sorry about that. I had thought this bug was addressed. I can look into it. I'm also trying to get "securty" fixed too.

    One question: Was there anything in the post that might have triggered the profanity filter? I was under the impression that that was the common reason for this error. (Here's an example.)

    • Aug 24, 2017 at 07:09 PM

      Nope. Someone had an issue with SAP Learning Hub back in 2015 which I am still having today and was asking if there was any fix/update on this.

  • Aug 25, 2017 at 08:14 AM

    Colleen stumbled upon the same issue:

    https://answers.sap.com/questions/283524/security-permissions-for-saving-comment-on-a-blog.html

    So you're at least not alone. ;)

  • Aug 25, 2017 at 03:15 PM

    Always copy your post before submitting

    @Jerry - surely the developer could search for spelling mistake for root cause?

    • Aug 28, 2017 at 05:14 PM

      there are several there :), the search might show too many results

  • Sep 01, 2017 at 05:08 PM

    They got me too. :( Hey, they fixed "securty" but I think it should be something like this:

    Was able to post the same comment after simply hitting "back" button, so it's obviously not related to the specific comment text. Or security.

    image.jpg (7.5 kB)
    • Sep 04, 2017 at 09:28 AM

      Same here!

    • Sep 04, 2017 at 02:28 PM

      The Only feasible "Workaround" I found so far is: Ctrl+A, Ctrl+C, WinKey+R, Notepad, CTRL+V

      :-(

  • Sep 05, 2017 at 06:42 PM

    After losing the comments 3 days in a row I feel like reopening the good old I've had it with the motherf*g snakes :(

    • Sep 07, 2017 at 09:01 PM

      I did not want to repost, but I ignorantly thought "hey, maybe they have fixed this now once and for all...." as I clicked the submit button for a comment......that's when I realized my ignorance was real. Fool me once, shame on me.....fool me fifteen times, I might need therapy.

    • Sep 13, 2017 at 01:34 PM

      Maybe we need a CC post for headbangers ball, or facepalm experiences? After finding both coffee pots empty when getting about 6 oz. into my 12 oz. post-consumer fiber cup, I opened my activity feed to this view...guess it's going to be one of those days...

      cjgoodhumpday.jpg (34.1 kB)
  • Oct 26, 2017 at 06:38 PM

    I'm at SAP TechEd Bangalore, and as a general rule, I Iike to focus on shows while at shows, but I was excited to learn that the bug with the securty...er...security risk has been resolved.

    Just check out the first fix for October 24.

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

    BTW...does it qualify as irony if security is mispelled as "securtiy"...as one of the requests with the job ticket was spelling "securty" correctly?

    • Oct 27, 2017 at 06:29 AM

      Just to be secure any possible problem was fixed, under any shape..

    • Oct 27, 2017 at 07:11 AM

      I think that what qualifies as irony is that the message did not become more helpful by fixing the typo. :)

  • Add comment
    10|10000 characters needed characters exceeded