The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.The Insert module is regularly used in conjugation with WYSIWYGs. If we could couple together Insert with Caption Filter (plue the feature at #696734: Integration with CKEditor or WYSIWYG?), we'd have a really kick-ass WYSIWYG solution (though still requiring 3-5 modules to get it all clicked together).
As users have mentioned here: http://drupal.org/node/696734#comment-4074778 you can already integrate Insert with Caption Filter manually by theming the Insert templates, but we could make this process quite a bit easier by implementing hook_insert_template_info() directly ourselves.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | caption_filter_insert-d6.patch | 6.27 KB | quicksketch |
| #2 | caption_filter_insert-d7.patch | 6.65 KB | quicksketch |
Comments
Comment #1
quicksketchThis problem is more complicated that I expected. Considering we don't actually want to provide *new* templates, we just want to wrap around the existing ones. More complicated yet, we need access things to like the "Description" or "Title" field in order to do our adjustments. To alleviate this problem, I've submitted a patch in the Insert queue which will be required for further enhancements here. See #1282830: Add JavaScript hook for altering inserted content.
Comment #2
quicksketchThese patches add support for the new Insert hooks added in #1282830: Add JavaScript hook for altering inserted content. The overall patch is a bit more complicated than expected due to the functionality we're adding. The patch does the following:
- Provides an option under the "Insert" category in the Field setting form ("Use title as caption").
- If that option is enabled, renames the "Title" field into "Caption" on the node form.
- If a Title is entered, wraps images in
[caption caption="Example caption"]...[/caption]upon being inserted.- As above, this patch adds support for the current WordPress syntax of
[caption caption="..."], making the caption a property on the tag. The old syntax of doing it inline is still supported with no changes. I expect this attribute-approach will be useful when it comes to the WYSIWYG integration.I've made new 1.1 releases to mark the finished D7 and bug-fixes prior to this patch being integrated. I've committed these changes afterwards, so we can look forward to a 1.2 release with these new features.
Comment #4
rezvani63 commentedI have installed caption filter 1.2 and I did all the settings regarding input formats and so on. But still when I use insert image botton, it only inserts image into editor without [caption]...[/caption] codes.
Do I have to apply this patches or they are already integrated into 1.2 version?
Because it's difficult to add [caption] codes for each image manually.
Thanks
Comment #5
quicksketchPlease do not reopen feature requests as support requests. File a new issue.
Comment #6
quicksketchThese patches are already in 1.2. The caption is only added if you add a caption (through the repurposed image title field) before you insert the image.
Comment #7
rezvani63 commentedSorry for that, because this issue is about insert module, I didn't open a new one.
I have caption textbox for image field and I write caption before inserting the image into text, but after insertion still there is no [caption] in body part although I have set all configurations required for it. Do you think is there in conflict with other modules or settings? (When I add [caption] manually it works fine).
Comment #8
rezvani63 commentedAlthough I have done all of the settings, the "Insert" botton does not include [caption] in the coding. I explained more in #7.
Please check this issue again.
Comment #9
rezvani63 commentedAlthough I have done all of the settings, the "Insert" botton does not include [caption] in the coding. I explained more in #7.
Please check this issue again.
Comment #10
patrickroma commentedSame problem here. TinyMCE does not generate the caption-Tags...
Comment #11
medienverbinder commentedsubscribe
Comment #12
kmontyPlease don't reopen closed tickets. If there is a bug, please open a new issue.