Tracing the code client side, it does seem to get to toaster.success(message), but no toast appears. We are probably re-rendering the toast context too many times since new posts result in a page navigation and are therefore losing the toast entry.
reply
It works!
reply