Tag options manipulate the way how tags are substituted. Here are some examples for options Linodef tags can use.

type
Set the type of object that is substituted.
  • node (default, includes fields)
    Example: [#1,type="node"] or short: [#1]
  • term
    Example: [#12,type="term"] (no shorthand)
  • view
    Example: [#viewname,type="view"] (no shorthand)
Content (content)
Select certain content of an object, e.g. fields, body, the complete node content or a views title. This option is also valid as short syntax [#id:content].
Examples:
[#1234,type="node",content="title"] or short: [#1234]
[#1234,type="node",content="field_myfield"] or short: [#1234:field_myfield]
Field value number (contentvalue)
If a field has multiple values you can select a certain value of that field. If this option is omitted the first value (0) is used. This option is also valid as short syntax [#id:content:contentvalue].
Examples:
[#1234,type="node",content="field_myfield",contentvalue="0"] or short: [#1234:field_myfield]
[#1234,type="node",content="field_myfield",contentvalue="1"] or short: [#1234:field_myfield:1]
HTML attributes (attributes)
Append HTML attributes to the embedded object.
Example: [#1234,attributes="rel=nofollow"] to nofollow a link
No link (nolink)
The embedded element is not linked. This option is set automatically (by default) for objects that contain block level elements (e.g. when you embed a whole view).
Example: [#1234,nolink]
Override embedded content (override)
Instead of the node title, taxonomy term, field value etc this custom text will be inserted as link to the object.
Example: (to be added here)
Build mode visibility (visibility)
The object will be embedded only in the selected build mode. Fields already heed build mode by using formatters.
Example:
[#4234:field_image,visibility="full"] to embed the field in full view only
[#4234:field_image,visibility="teaser"] to embed the field in teaser view only
Hint: if you don't use a formatter for the field, the default formatter is used (according to the setting on the admin/content/node-type/#/display page). So, if the default formatter is <hidden>, don't expect to get a valid value with this linodef tag. You should use
  • another default formatter for the field on the display tab and check "exclude from display" instead
  • or specify a formatter on the linodef tag
For node object types:
CCK formatter (formatter)
Override the default CCK build mode sensitive formatter of a field.
Example: [#2345:field_image,formatter="small_url"]
The formatter must be on of the internal formatter names.
Hint: Different ways to retrieve the internal formatter names:
  • Go to the filter/tips section of the input format that uses Linodef. There a list of available formatters is at hand. (since January 14, 2010 releases)
  • Useage of firefox and its extension firebug: Go to the content type fields display page (e.g. admin/content/content-type/image/display). Then open the firebug window (press F12) and on the toolbar of the window click on the button to search items on the web page. Now click on the formatter dropdown of your image field. In the option list of this field the option values are the available formatter names.
  • Or view the source code of the content type fields display page and search for the formatter names yourself.
Translation
If the embedded node has a translation in the specified language than the translated node is embedded instead. Useful if you embed a node which has no translated node yet but you want to embed the translated node as soon as it is created.
As value use the abbrevation of the language. Often a Drupal language uses the abbrevation defined by ISO 639-1/2.
Example: [#1874,translation="de"]

For view object types:

Display
Select a certain display of a view. Make sure the HTML filter you use allows those HTML tags required by the view, e.g.
for a view display using a table. Otherwise the embedded view will look weird.
Example: (to be added here)
View arguments (arguments)
Arguments passed to the view.
Example: (to be added here)
viewtitle: replaced by content="title"
Only the viewtitle with a link to the view will be embedded. The link heeds the values for display and arguments.
By default the embedded view is not linked to itself, because a view contains HTML block tags what would cause a weird output if surrounded with an inline link tag. So if you would like to embed a full view but also want to link to it then the usage of a second tag with this option is the recommended way.
Example: (to be added here)

Comments

pkej’s picture

In the CCK Formatter part, perhaps a mention of Custom Formatters would be in its place? If I understood that module it lets the user configure new formatters, and since linodef lets you decide which formatter to use, the synergy would be tremendous.

Now, if there only were a WYSIWYG (the module) integration with a good GUI to select all these things...

Paul K Egell-Johnsen