Changes between Version 12 and Version 15 of Ticket #6608
- Timestamp:
- 12/06/2022 03:15:16 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #6608 – Description
v12 v15 9 9 ✅ Ensure that `@mention` work appropriately. Currently it lists Site Users, where it should pull from those who have interacted with the current Thread. This should NOT suggest moderators by default, or those whose replies are hidden (spammed, archived, awaiting moderation, etc). 10 10 - 🔲 Consider whether to always include the support reps for the current plugin/theme. 11 🔲 Ensure that pasting logs works. The existing "wrap it in code tags" doesn't work well, and when pasting into the Block Editor it will split it into many blocks instead. This behaviour makes sense for most uses of the Block Editor, but creates a worse UX for the forums, especially when it comes to attempting to combine the logs into a singular block.12 11 🔲 Ensure that fixes we've applied for `<li>` in the past continue to work. See #20. The fix currently in place via [9601] breaks/prevents nested lists in the Block Editor. 13 12 🔲 Ensure that blocks copy-pasted from other Block Editor Instances pastes correctly into the Support forum editor. 14 🔲 Evaluate if an option to disable the Block editor on a per-user profile option is practical. With early iterations of testing support, this wasn't possible. [https://github.com/Automattic/blocks-everywhere/issues/55 upstream issue]15 🔲 Evaluate additional blocks to be enabled, or created, for the forums. This may include a "Pasted content" block as above, or other blocks such as pre-defined replies for members of the support team and/or plugin/theme support reps.13 🔲 Evaluate if an option to disable the Block editor on a per-user profile option is practical. This might be an option, we still need to decide if we wish to support that though. [https://github.com/Automattic/blocks-everywhere/issues/55 upstream issue] 14 🔲 Evaluate additional blocks to be enabled, or created, for the forums. This may include a "Pasted content" block as below, or other blocks such as pre-defined replies for members of the support team and/or plugin/theme support reps. 16 15 🔲 Evaluate Upstream issues in [https://github.com/Automattic/blocks-everywhere/issues Automattic/blocks-everywhere]. ''(please report any major issues in the plugin upstream, if it doesn't seem WordPress.org-specific)'' 16 17 '''Upstream Blockers''' 18 🔲 Ensure that pasting logs works. The existing "wrap it in code tags" doesn't work well, and when pasting into the Block Editor it will split it into many blocks instead. This behaviour makes sense for most uses of the Block Editor, but creates a worse UX for the forums, especially when it comes to attempting to combine the logs into a singular block. [https://github.com/Automattic/blocks-everywhere/issues/54 Upstream Issue] 17 19 18 20 ''Additional items to be edited in here as discovered, please comment below. Bug Gardeners: Please edit my ticket too! ''