Problem/Motivation
This module is great and has been a great fit for one of our current projects. I might be missing something, but I think it would be really cool if the add content block included an option for the destination.
If I include a manage content view, (I cloned one from the admin/content view), the destinations are baked into the operations automatically. For the add content block they're not.
I imagine that some workflows might want to be redirected to the node view page itself, that's why it can be a configuration that's default is 0.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3349167.patch | 3.12 KB | asherry |
Comments
Comment #2
asherry commentedHere's a patch to start things off. I'm going to move this to "needs review" to see if it's something that is worth moving forward on.
Comment #3
asherry commentedComment #4
asherry commentedI forgot to mention that in the configuration form there is an accent in the title "Menü items". I fixed that as well in this same patch, but let me know if I should create another ticket.
Comment #5
erik seifert commentedComment #6
erik seifert commentedWe should have a better label than "Include destination". Something like "Return to dashboard after create content".
Comment #7
erik seifert commentedComment #8
asherry commentedSorry, I was just following precedent, the views entity operation links has the same label.
Drupal\views\Plugin\views\field\EntityOperationsI'm not saying I'm in love with the label of "include destination", haha, but at least for developers it matches other interfaces, and it's clearer as to what will actually happen. "Return to dashboard after create content" to me might mean we'd be doing a redirect.
Is there an ability also for these dashboard blocks to be placed with the regular block layout? Or might there be any possibility in the future for placing a dashboard entity in another context? That would also be confusing for this label.
Maybe, "Include destination query parameter"?
Comment #10
erik seifert commented