I have no clue about this one, just reporting it for now. Ref the issue with the extra status textarea. When I tried a value in there (silly me) a few statuses were deleted, and the test value was added as an extended statuses – with an error displayed on render. The fix for the extra status will probably eliminate this. So, FYI…
Follow-up: Status values were Not deleted. The bogus ‘foo’ status simply caused the list to stop rendering and other valid status values were not displayed. Deleting the ‘foo’ value (which only existed because I added the foo value in the textarea that is being removed) eliminated the list render issue and the other status codes are present and displayed properly.
Let’s call this a non-issue, but I’m leaving here in case someone else trips on similar conditions and results.
- This topic was modified 23 minutes ago by . Reason: added Follow-up
- This topic was modified 21 minutes ago by . Reason: Modified subject to avoid worrying other users