[#id] [#id,option(s)] [#id,option(s) comment]
Linodef is an input filter for embedding content of your Drupal installation (Drupal objects) into any textarea and link to it. The tags are based exclusively on object IDs which enables a highly dynamic usage. So links won't break and the embedded content stays up to date. Editor buttons help users to find their desired object and insert the corresponding Linodef tag into the textfield.
- embedding of nodes, fields, views and terms
- short and extensible tags
- configurable buttons allow users to insert objects without having to know their Linodef tags
- customizable message system for detailed reports about faulty tags
- Filter: This enables the possibility to add content to new nodes without node id.
- Taglists: and use the themed output of views. This can be used to e.g. select images by clicking on image thumbs.
- Embed users (in preparation for D7 field handling)
- update translation templates (pot)
- Filter/Taglists: evaluate the best way to embed fields (using node/user/etc ID or using field directly if possible)
- Add a port D6->D7 module for existing tags in textfield. This could also be used to replace deprecated options.
- Taglists: Support inline autocomplete with the help of the taglist data:
- WYSIWYG: Use feature above to replace tags in rich-text by actual content.
- Filter: Supporting dynamic arguments (e.g. tokens or linodef own joker feature) for the option arguments to embed content sensitive views.
- Deactivate the old linodef modules and delete the old linodef modules folder. So deprecated modules don't remain in your modules list.
- When using BUEditor replace your existing Linodef buttons code with the new taglist code.
Additional hints when upgrading from rc2 or older:
- Linking to nodes using an own text with the syntax
<#nid>Text</#>is marked as deprecated (it is still supported). Instead use the new option
- Option values are now encircled by double quotes
". So you may use almost every 8bit character in option values (except double quote
"). Therefore when you already use
translation=enyou should change it to
translation="en"(the old syntax without double quotes is still supported but marked as deprecated).
- Maintenance status: Unknown
- Development status: Unknown
- Reported installs: 217 sites currently report using this module. View usage statistics.
- Downloads: 4,106
- Last modified: May 14, 2012