Link Entry Readonly
<et2-link-entry_ro> | Et2LinkEntryReadonly
What it is for
The readonly form of <et2-link-entry>. You rarely write this tag yourself: eTemplate appends _ro to a widget’s tag name when it is
readonly, so <et2-link-entry readonly="true"> in a template loads this widget instead.
It is <et2-link> - same class, same properties, same
behaviour - under a second tag name, so that a field the user picks an entry with turns into a display of
that entry rather than disappearing. Read that page for what the properties do; this one only shows how the
two tags line up.
See Choosing a link widget for the rest of the family.
Examples
A link’s title comes from the server, and this documentation site has none, so the example below passes the title in with the link. In a real template the widget is given the entry and fetches the title itself.
The readonly half of a link-entry field
InfoLog’s “Project” field is <et2-link-entry id="pm_id" onlyApp="projectmanager">. On a
readonly template the same field arrives as this widget, with the ID the user picked:
<et2-link-entry_ro id="link-entry-ro-example" app="projectmanager"></et2-link-entry_ro>
<script>
const entry = document.getElementById("link-entry-ro-example");
customElements.whenDefined("et2-link-entry_ro").then(() =>
{
entry.value = {app: "projectmanager", id: "3", title: "2026-014: Website relaunch"};
});
</script>
Because it is an <et2-link>, it is still clickable: it opens the entry with
egw.open(), the same as everywhere else links are displayed.
No value
Given nothing to show - an empty field on a readonly template - it renders nothing at all, rather than an empty box or a placeholder.
<et2-link-entry_ro id="link-entry-ro-empty" app="projectmanager"></et2-link-entry_ro>
<span>(nothing above this line)</span>
Inherited properties (27)
Link
| Name | Description |
|---|---|
accesskey |
Accesskey provides a hint for generating a keyboard shortcut for the current element. The attribute value must consist of a single printable character. |
actions |
Set Actions on the widget Each action is defined as an object: move: { type: “drop”, acceptedTypes: “mail”, icon: “move”, caption: “Move to” onExecute: javascript:mail_move” } This will turn the widget into a drop target for “mail” drag types. When “mail” drag types are dropped, the global function mail_move(egwAction action, egwActionObject sender) will be called. The ID of the dragged “mail” will be in sender.id, some information about the sender will be in sender.context. The etemplate2 widget involved can typically be found in action.parent.data.widget, so your handler can operate in the widget context easily. The location varies depending on your action though. It might be action.parent.parent.data.widget To customise how the actions are handled for a particular widget, override _link_actions(). It handles the more widget-specific parts. |
align |
Used by Et2Box to determine alignment. Allowed values are left, right |
app |
Specify the application for the entry |
breakTitle |
Breaks title into multiple lines based on this delimiter by replacing it with ‘\r\n’” |
class |
CSS Class. This class is applied to the outside, on the web component itself. Due to how WebComponents work, this might not change anything inside the component. |
data |
Set the dataset from a CSV |
deferredProperties |
Any attribute that refers to row content cannot be resolved immediately, but some like booleans cannot stay a string because it’s a boolean attribute. We store them for later, and parse when they’re fully in their row. If you are creating a widget that can go in a nextmatch row, and it has boolean attributes that can change for each row, add those attributes into deferredProperties |
disabled |
Defines whether this widget is visibly disabled. The widget is still visible, but clearly cannot be interacted with. Widgets disabled in the template will not return a value to the application code, even if re-enabled via javascript before submitting. To allow a disabled widget to be re-enabled and return a value, disable via javascript in the app’s et2_ready() instead of an attribute in the template file. |
dom_id |
Get the actual DOM ID, which has been prefixed to make sure it’s unique. |
entryId |
Application entry ID |
exposeValue |
Get the info needed to determine if this widget’s value allows it to participate in expose It needs to have a path, and we use mime to determine if it can expose It’s also passed to getMedia() when we’re not reading from a nextmatch |
extraLinkTarget |
Optional parameter to be passed to egw().open in order to open links in specified target eg. _blank |
hidden |
The widget is not visible. As far as the user is concerned, the widget does not exist. Widgets hidden with an attribute in the template may not be created in the DOM, and will not return a value. Widgets can be hidden after creation, and they may return a value if hidden this way. |
id |
Get the ID of the widget |
label |
The label of the widget This is usually displayed in some way. It’s also important for accessability. This is defined in the parent somewhere, and re-defining it causes labels to disappear |
linkHook |
View link type Used for displaying the linked entry [view|edit|add] default “view” |
mediaContentFunction |
Function to extract an image list “Normally” we’ll try to pull a list of images from the nextmatch or show just the current widget, but if you know better you can provide a method to get the list. |
noLang |
Disable any translations for the widget |
parentId |
Parent is different than what is specified in the template / hierarchy. Widget ID of another node to insert this node into instead of the normal location |
statustext |
Tooltip which is shown for this element on hover |
styles |
WebComponent * |
targetApp |
Target application Passed to egw.open() to open entry in specified application |
value |
Pass value as an object, will be parsed to set application & entryId |
options |
Get property-values as object |
supportedWidgetClasses |
et2_widget compatability |
LitElement
| Name | Description |
|---|---|
updateComplete |
A read-only promise that resolves when the component has finished updating. |
Inherited methods (22)
Link
| Name | Description |
|---|---|
checkCreateNamespace() |
Checks whether a namespace exists for this element in the content array. If yes, an own perspective of the content array is created. If not, the parent content manager is used. Constructor attributes are passed in case a child needs to make decisions |
clone() |
Creates a copy of this widget. |
createElementFromNode() |
Create a et2_widget from an XML node. First the type and attributes are read from the node. Then the readonly & modifications arrays are checked for changes specific to the loaded data. Then the appropriate constructor is called. After the constructor returns, the widget has a chance to further initialize itself from the XML node when the widget’s loadFromXML() method is called with the node. |
getArrayMgr() |
Returns the array manager object for the given part |
getArrayMgrs() |
Returns an associative array containing the top-most array managers. |
getChildren() |
Get child widgets Use |
getInstanceManager() |
Returns the instance manager |
getMedia() |
Get the info needed to show the given value as slide(s) _value is (usually?) pulled from egw.dataGetUIDdata() Override this |
getPath() |
Returns the path into the data array. By default, array manager takes care of this, but some extensions need to override this |
getRoot() |
Returns the base widget Usually this is the same as getInstanceManager().widgetContainer |
loadFromXML() |
Loads the widget tree from an XML node |
loadingFinished() |
Needed for legacy compatability. |
parseXMLAttrs() |
The parseXMLAttrs function takes an XML DOM attributes object and adds the given attributes to the _target associative array. This function also parses the legacyOptions. N.B. This is only used for legacy widgets. WebComponents use transformAttributes() and do their own handling of attributes. |
set_label() |
NOT the setter, since we cannot add to the DOM before connectedCallback() TODO: This is not best practice. Should just set property, DOM modification should be done in render https://lit-element.polymer-project.org/guide/templates#design-a-performant-template |
setArrayMgr() |
Sets the array manager for the given part |
setArrayMgrs() |
Sets all array manager objects - this function can be used to set the root array managers of the container object. |
setInstanceManager() |
Set the instance manager Normally this is not needed as it’s set on the top-level container, and we just return that reference |
_handleClick() |
Just override the normal click handler |
destroy() |
et2_widget compatability |
set_class() |
Set the widget class |
set_disabled() |
Wrapper on this.disabled because legacy had it. |
set_statustext() |
supports legacy set_statustext |