Assembly

This service has only one interface for content administration, which can be made available to content editors through an instance on a restricted page of the portal, where only the content editors will have access after logging in, or it can be accessed through the Content Administration mode.

The assembly of this service for the end user depends on the channel where it is instantiated and the properties of the service instance.

The HTML contents added with this service are inserted on all pages in the subtree of the channel in which the service is instantiated.

The HTML injection is not done by default in page block, but with the property lumis.service.htmlinjector.ignore set to "false", the service will perform HTML injection and when set to "true", the service will not perform HTML injection even on pages that are not page blocks.

If there are more than one instance of the service to Insert HTML in different channels above a page, the contents created for those service instances will be inserted into the page according to the priority of their HTML processors defined for each service in their General Properties, with the contents of the service instance with the highest priority for its HTML processors being inserted first.

The contents of an instance of this service, in turn, are inserted according to its priority, defined in its registration, with the contents of higher priority being inserted first.

Example

For the structure above, Page 1.1 will only have the contents of the service instance "Inject HTML 1.1", while Page 2.1 will have the contents of the service instance "Inject HTML 2.1" inserted before the contents of the service instance "Inject HTML 1.1", if the priorities of the HTML processors of the service instances are the same.

If the priority of the HTML processors of the service instance "Inject HTML 1.1" is higher than the priority of the HTML processors of the service instance "Inject HTML 2.1", the contents of the service instance "Inject HTML 1.1" will be inserted on Page 2.1 before the contents of the service instance "Inject HTML 2.1".

Assuming also that the service instance "Inject HTML 1.1" has two contents, one with priority 0 and another with priority 1, the content with priority 1 will be inserted before the content with priority 0, both on Page 1.1 and on Page 2.1.

In other words, if the service instance "Inject HTML 1.1" has the priority of its HTML processors equal to 1 and the following contents registered:

• Content 1.1:
  • HTML: <p style="color:red; padding:10px;">Content 1.1</p>
  • Priority: 0
  • Position: Beginning of the page body
• Content 1.2:
  • HTML: <p style="color:green; padding:10px;">Content 1.2</p>
  • Priority: 1
  • Position: Beginning of the page body

and if the service instance "Inject HTML 2.1" has the priority of its HTML processors equal to 0 and the following contents:

• Content 2.1:
  • HTML: <p style="color:blue; padding:10px;">Content 2.1</p>
  • Priority: 0
  • Position: Beginning of the page body
• Content 2.2:
  • HTML: <p style="color:pink; padding:10px;">Content 2.2</p>
  • Priority: 1
  • Position: Beginning of the page body

The display of Page 2.2 will look as follows:

Permission Assignment

For the content editor to access the news administrative environment, the portal administrator must grant him the permission "Edit service instance content". This permission is granted in the access control of the service instance.