Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
As a (for now at least) casual user, I can report that a bad first impression is that there are way too many "500 server errors". Within a few tens of minutes I ran into two, one for some profile ...
Answer
#3: Post edited
by
Peter Mortensen
·
2021-12-03T01:37:58Z (over 2 years ago)
Minor (but is there an edit grace period or not?)
- As a (for now at least) casual user, I can report that a bad first impression is that there are way too many *"500 server errors"*.
- Within a few tens of minutes I ran into two, one for some profile action (clicking on some tab in a user profile?) and one for en edit action.
It was the same impression some months ago and, like for [submitting comments to the official Stack Overflow blog](https://pmortensen.eu/world2/2020/06/24/formatting-wordpress-comments-e-g-on-the-stack-overflow-official-blog/), I now know to save everything offline in a text file in order not to risk losing content and/or have the option to try again some time in the future (including when submitting this very post). That shouldn't be necessary.- If there are some known errors or limitations, I think users should at least be informed somehow (e.g., information about workarounds or things to avoid).
- Perhaps take a look at those *500 server error* error logs?
- As a (for now at least) casual user, I can report that a bad first impression is that there are way too many *"500 server errors"*.
- Within a few tens of minutes I ran into two, one for some profile action (clicking on some tab in a user profile?) and one for en edit action.
- It was the same impression some months ago and, like for [submitting comments to the official Stack Overflow blog](https://pmortensen.eu/world2/2020/06/24/formatting-wordpress-comments-e-g-on-the-stack-overflow-official-blog/), I now know to save everything offline in a text file in order not to risk losing content and/or to have the option to try again some time in the future (including when submitting this very post). That shouldn't be necessary.
- If there are some known errors or limitations, I think users should at least be informed somehow (e.g., information about workarounds or things to avoid).
- Perhaps take a look at those *500 server error* error logs?
#2: Post edited
by
Peter Mortensen
·
2021-12-03T01:36:34Z (over 2 years ago)
Added a second reason for saving content offline.
- As a (for now at least) casual user, I can report that a bad first impression is that there are way too many *"500 server errors"*.
- Within a few tens of minutes I ran into two, one for some profile action (clicking on some tab in a user profile?) and one for en edit action.
It was the same impression some months ago and, like for [submitting comments to the official Stack Overflow blog](https://pmortensen.eu/world2/2020/06/24/formatting-wordpress-comments-e-g-on-the-stack-overflow-official-blog/), I now know to save everything offline in a text file in order not to risk losing content (including when submitting this very post). That shouldn't be necessary.- If there are some known errors or limitations, I think users should at least be informed somehow (e.g., information about workarounds or things to avoid).
- Perhaps take a look at those *500 server error* error logs?
- As a (for now at least) casual user, I can report that a bad first impression is that there are way too many *"500 server errors"*.
- Within a few tens of minutes I ran into two, one for some profile action (clicking on some tab in a user profile?) and one for en edit action.
- It was the same impression some months ago and, like for [submitting comments to the official Stack Overflow blog](https://pmortensen.eu/world2/2020/06/24/formatting-wordpress-comments-e-g-on-the-stack-overflow-official-blog/), I now know to save everything offline in a text file in order not to risk losing content and/or have the option to try again some time in the future (including when submitting this very post). That shouldn't be necessary.
- If there are some known errors or limitations, I think users should at least be informed somehow (e.g., information about workarounds or things to avoid).
- Perhaps take a look at those *500 server error* error logs?
#1: Initial revision
by
Peter Mortensen
·
2021-12-03T01:23:47Z (over 2 years ago)
As a (for now at least) casual user, I can report that a bad first impression is that there are way too many *"500 server errors"*. Within a few tens of minutes I ran into two, one for some profile action (clicking on some tab in a user profile?) and one for en edit action. It was the same impression some months ago and, like for [submitting comments to the official Stack Overflow blog](https://pmortensen.eu/world2/2020/06/24/formatting-wordpress-comments-e-g-on-the-stack-overflow-official-blog/), I now know to save everything offline in a text file in order not to risk losing content (including when submitting this very post). That shouldn't be necessary. If there are some known errors or limitations, I think users should at least be informed somehow (e.g., information about workarounds or things to avoid). Perhaps take a look at those *500 server error* error logs?