|
One was a change that did not appear when the post was saved and re-displayed but did appear when the post was immediately re-edited. Another example was a change that was successfully saved and immediately re-displayed, but was gone when the post was re-displayed hours later (and it did not reappear on re-edit). The workaround is to perform all data entry and updates in local text files... if you give a rat's patootie, that is :) |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 23 Apr '17, 09:47
question was seen: 1,357 times
last updated: 23 Apr '17, 10:55
FWIW sqlanywhere.blogspot.com suffers from HTML drift where old posts become subtly corrupted (e.g., leading spaces removed from PRE sections) and must be refreshed from local text files... another reason "local files" are important in this Brave New Cloud :)
Well, I have also noticed some issues when doing two or more edits rather immediately after another, or when changing a comment to an answer and then editing that. I guess sometimes one has to be somewhat patient... - I have learnt to check my postings after 2-3 minutes.
Nevertheless, no problems compared to the SAP community user experience...