-2
\$\begingroup\$

Here at Code Review, I get the extremely annoying message :

Your post appears to contain code that is not properly formatted as code. Please indent all code by 4 spaces using the code toolbar button or the CTRL+K keyboard shortcut. For more editing help, click the [?] toolbar icon.

While at Stack Exchange, I was allowed to upload the post just fine!

\$\endgroup\$
14
  • \$\begingroup\$ My markdown works just fine at Stack Exchange. But I get an error when I try to post it here! Is this a bug that can be fixed? \$\endgroup\$
    – Henke
    Feb 26 at 19:05
  • 1
    \$\begingroup\$ Are you able to add specific portions of the code to determine which sections may be causing the error to occur? Are there any errors appearing in the browser console? Are you able to add screenshots of when the error occurs? \$\endgroup\$
    – Sᴀᴍ Onᴇᴌᴀ Mod
    Feb 27 at 6:24
  • 1
    \$\begingroup\$ If you provide an example of when this happens, a specific block of text/code causing this, we'll see if it can be fixed. At the moment, there's very little to go on. You posted a big post with multiple formatting options used, if you could narrow it down to which part is the cause of your message that would be of great help. \$\endgroup\$
    – Mast Mod
    Feb 27 at 6:57
  • \$\begingroup\$ Are you essentially looking for a review of the SO answer you wrote a while ago? \$\endgroup\$
    – Mast Mod
    Feb 27 at 6:59
  • 1
    \$\begingroup\$ Thanks for migrating my question. The error Your post appears to contain code that is not properly formatted as code is a well-known bug that occurred years ago at Stack Overflow. Since then, it has been fixed at SO, and apparently also at Meta Stack Exchange. I've no idea why it hasn't been fixed here at Code Review. My view is that it ought to be the responsibility of the company Stack Exchange to fix this bug. I'm not sure what your responsibility as moderators is, but I suggest you escalate the bug report to staff members. \$\endgroup\$
    – Henke
    Feb 27 at 9:04
  • \$\begingroup\$ > Are you able to add specific portions of the code to determine which sections may be causing the error to occur? -- Honestly, I have absolutely no intention of trying to find a workaround for a bug that should have been fixed years ago. If you want to experiment with my markdown, just go ahead and do it! You can copy-paste the complete Markdown code from meta.stackexchange.com/posts/360883/edit. Here is what you will find: i.imgur.com/tQY8LWT.png. It doesn't make any sense to me to spend time on a well-known bug that should have been fixed long ago. \$\endgroup\$
    – Henke
    Feb 27 at 9:11
  • \$\begingroup\$ For anyone who wants to confirm that there is nothing wrong with my Markdown code, I recommend doing the following. From meta.stackexchange.com/posts/387042/edit, copy my Markdown. Then go to Formatting Sandbox, and answer that "question" by pasting my Markdown code as an "answer", and pressing Enter. You won't get any error saying Your post appears to contain code that is not properly formatted [...] ! \$\endgroup\$
    – Henke
    Feb 27 at 11:14
  • \$\begingroup\$ > if you could narrow it down to which part is the cause of your message that would be of great help -- OK. Try copying the Markdown code of meta.stackexchange.com/posts/360883/edit. Then try using that code to ask a question here at Code Review. Here is what I got when I tried that: i.imgur.com/GC3cOzx.png. \$\endgroup\$
    – Henke
    Feb 27 at 11:58
  • 1
    \$\begingroup\$ Does adding a newline after your codeblock work? If so, it may be related to this old bug. \$\endgroup\$
    – Mast Mod
    Feb 27 at 14:38
  • 1
    \$\begingroup\$ The reason why you're not seeing it on MSE but do on Code Review, is posts on MSE have different filters. They don't have this one. \$\endgroup\$
    – Mast Mod
    Feb 27 at 14:44
  • 1
    \$\begingroup\$ @Mast. Thanks for taking the time to look into this. -.- >Does adding a newline after your codeblock work? -- No! Adding a newline does not help. This is a Stack Exchange bug that was prevalent on Stack Overflow for many years, but has now been fixed. I intend to write about it at Meta Stack Overflow, and then report back here. In the meanwhile, I strongly encourage both you and others to reproduce the bug as per my suggestion in this comment. Get the Markdown from meta.stackexchange.com/posts/360883/edit ! \$\endgroup\$
    – Henke
    Feb 27 at 15:09
  • 2
    \$\begingroup\$ That Markdown makes no sense. Why would you be trying to post this? The filter is not a false-positive; it's blocking you from posting invalid Markdown that, if you really need to post it, verbatim should almost certainly be formatted as code. \$\endgroup\$
    – Cody Gray
    Feb 28 at 4:50
  • \$\begingroup\$ The point of my Markdown at meta.stackexchange.com/posts/360883/edit is that it reproduces the "not properly formatted as code" BUG. Anyone who is interested in that bug can easily see that the bug has been reported over and over and over and over again. \$\endgroup\$
    – Henke
    Feb 28 at 8:20
  • 1
    \$\begingroup\$ Related: Visualizing a mashup API in Postman (migrated) \$\endgroup\$
    – Mast Mod
    Feb 28 at 9:31

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .