Closed (won't fix)
Project:
BUEditor
Version:
8.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2019 at 17:35 UTC
Updated:
11 Jul 2019 at 16:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
damontgomery commentedHere is a patch with the token support and a patch with the example that works for views.
Comment #3
damontgomery commentedHere is the insert_view_adv submodule: https://www.drupal.org/project/insert_view_adv/issues/3065733
Comment #4
damontgomery commentedComment #5
kbentham commentedThanks for creating this patch Dan!
Comment #6
damontgomery commentedI've had more time working with BUEditor and the advanced insert view module and I think it might make more sense to move all of this functionality into advanced insert view.
I'd appreciate feedback.
I think this makes more sense because the tokens we are creating use a non-standard format of
[view:my_view=my_display=my_arguments].I would expect a token system to use `:` based on how I've used tokens in Drupal in other places.
So, I'll move all these new methods into the javascript. This is possible because the BUE and Editor are passed in to that javascript, so I can define my own methods / extend the objects as needed. I've created a proof of concept for media embed tokens which I'm working on as well.
I think I'll be able to tackle this towards the end of this week.
Comment #7
a.dmitriiev commentedNice, btw the token syntax is legacy from insert view module, so it is also compatible with it and for migration purposes (from d6, d7 to d8), so there is no need to change the markup. Maybe it is better to use the new syntax, with standard formats of tokens? If it is easier to implement and will make it more generic. I am ok with changing the filter itself, to support other formats.
Comment #8
damontgomery commentedI've put all of this into https://www.drupal.org/project/insert_view_adv/issues/3065733#comment-13....
I'll close this now.
Thanks.