Various post version fixes #4369
Conversation
- "Current" is now most like the old format -- It is therefore now the default for post versions - Only show the actual edits in their own column - Show the current state at that version in another column - On the "previous" view, don't double-show full list of tags for the first post versions, so leave edits blank
- Tag matches allows a user to search for a single tag -- Since testing for multiple tags would require converting the "tags" string to an array which would most likely fail even for single tags - Is new for quick searching of uploads or not uploads
I'm skeptical of this. I think in most cases showing the full unchanged state will be distracting and will take up a lot of space.
The version field is known to be wrong in some cases. Some posts start with version 2 and don't have a version 1.
This isn't necessarily going to do what people expect. Something like |
Fixes #4364, fixes #4365, fixes #4366.
Alternate post versions HTML format
Converts the column Tags and places all of the current state of the post at that time (to included unchanged tags) into it. It also supports tag categories and was partially based off of the display for comments.
Adds an additional column Edits and lists only the actual items that were added and removed for that particular post version. It also does away with the "+" and "-" to facilitate ease in copying. Finally, it brings back the "obsolete" category for the "subsequent" and "previous" views.
Current
The "previous" mode does not have any additional comparisons to make against since those are the comparison values, so it has no "obsolete" category. No tag changes are shown on the "New" versions even though the tags are new, since that would just be a doubling up of the information found in the tags column.
Previous
Since the "current" mode is most like the old presentation of the post versions, it is now the new default mode for that model. Besides those, it also fixes the post drill-down link in the Versions column to also include the type parameter.
Add additional Search operators
The is_new parameter is a more user friendlier version of the versions parameters with a focus on the first versions. The tag_matches parameter facilitates searching for a single tag, which it partially enforces by taking the first non-whitespace block of text as input. Searching for one or more tags would require doing a tag split on the "tags" parameter in the SQL, something which would undoubtedly cause it to fail for even single tag searches.
Advanced search parameters
Clicking the "Advanced search" link will retain all of the current search parameters. This was left off the secondary menu link because it may be desired to return to quickly return to a fresh search state.