/o//commerce-media/accounts/-1/images/18666193?download=true
HowLong2Read
DXP App
HowLong2Read is a plugin compatible with Liferay version 7.2 CE, and targeted towards those sites that offer text content to their users and want to offer their clients that little bit extra of usability.
With this plugin there will be available, once a content has been updated or created, an estimation of the time required to completely read such content, by means of an algorythm specially created for the evaluation of each text.
That way, site users will be able to decide which content to read based on their available time, specially useful for those that only have their free time spread in little breaks between the daily tasks. HowLong2Read es un plugin compatible con la version 7.2 CE de Liferay orientado a aquellas páginas que ofrecen contenido en texto a sus clientes y desean cuidarles un poco más.
Con este plugin se dispondrá, al crear o actualizar algún contenido, de una estimación del tiempo necesario para completar la lectura del mismo, mediate el uso de un algoritmo desarrollado especialmente para la evaluación de cada texto.
De ese modo, los usuarios de la web podrán valorar qué contenido leer en función del tiempo de que disponen, algo ideal especialmente para aquellas personas que sólo disponen de pausas breves entre obligaciones.
With this plugin there will be available, once a content has been updated or created, an estimation of the time required to completely read such content, by means of an algorythm specially created for the evaluation of each text.
That way, site users will be able to decide which content to read based on their available time, specially useful for those that only have their free time spread in little breaks between the daily tasks. HowLong2Read es un plugin compatible con la version 7.2 CE de Liferay orientado a aquellas páginas que ofrecen contenido en texto a sus clientes y desean cuidarles un poco más.
Con este plugin se dispondrá, al crear o actualizar algún contenido, de una estimación del tiempo necesario para completar la lectura del mismo, mediate el uso de un algoritmo desarrollado especialmente para la evaluación de cada texto.
De ese modo, los usuarios de la web podrán valorar qué contenido leer en función del tiempo de que disponen, algo ideal especialmente para aquellas personas que sólo disponen de pausas breves entre obligaciones.
DEVELOPER
处理模板时发生错误。
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 16, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 16, column 1]
----
1<#assign
2 channels = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
3 channelId = ""
4/>
5
6<#list channels.items as channel>
7 <#if channel.name == "Marketplace Channel">
8 <#assign channelId = channel.id />
9 </#if>
10</#list>
11
12<#if (CPDefinition_cProductId.getData())??>
13 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
14</#if>
15
16<#if specifications?has_content && specifications.items?has_content>
17 <#list specifications.items as specification>
18 <#if specification.specificationKey?has_content && specification.specificationKey == "developer-name">
19 ${specification.value}
20 </#if>
21 </#list>
22</#if>
DEVELOPER
21-7-2 上午12:00
Published date
处理模板时发生错误。
The string doesn't match the expected date/time/date-time format. The string to parse was: "21-7-2 上午12:00". The expected format was: "MM/dd/yy HH:mm".
The nested reason given follows:
Unparseable date: "21-7-2 上午12:00"
----
FTL stack trace ("~" means nesting-related):
- Failed at: ${CPDefinition_displayDate.getData()?... [in template "3192443#3192485#null" at line 4, column 9]
----
1<#setting date_format="MMMMM d, yyyy">
2
3<#if (CPDefinition_displayDate.getData())??>
4 ${CPDefinition_displayDate.getData()?datetime("MM/dd/yy HH:mm")?date}
5</#if>
Published Date
21-7-2 上午12:00
SUPPORTED OFFERINGS
Self-Hosted, Self-Managed
Supported Versions
7.2
Resource Requirements
处理模板时发生错误。
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 17, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 17, column 1]
----
1<#assign
2 channelId=""
3 channels=restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
4 filteredSpecifications=[]
5/>
6
7<#list channels.items as channel>
8 <#if channel.name=="Marketplace Channel">
9 <#assign channelId = channel.id />
10 </#if>
11</#list>
12
13<#if (CPDefinition_cProductId.getData())??>
14 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
15</#if>
16
17<#if specifications?has_content && specifications.items?has_content>
18
19 <#assign
20 cpuQuantity = ""
21 memoryQuantity = ""
22 />
23
24 <#list specifications.items?sort_by("specificationKey") as specification>
25 <#if stringUtil.equals(specification.value, "cloud")>
26 <script>
27 var resourceRequirements = document.querySelector(".marketplace-resource-requirements")
28
29 resourceRequirements.classList.remove("d-none");
30 </script>
31 </#if>
32
33 <#if specification.specificationKey?has_content && (stringUtil.equals(specification.specificationKey, "cpu") || stringUtil.equals(specification.specificationKey, "ram"))>
34 <#if stringUtil.equals(specification.specificationKey, "cpu" )>
35 <#assign cpuQuantity = specification.value />
36
37 <#if cpuQuantity?has_content>
38 ${cpuQuantity}
39 <#if cpuQuantity?eval gt 1>
40 CPUS
41 </#if>
42 <#if cpuQuantity?eval lt 2>
43 CPU
44 </#if>
45 </#if>
46 </#if>
47
48 <#if stringUtil.equals(specification.specificationKey, "ram")>
49 <#assign memoryQuantity = specification.value />
50
51 <#if cpuQuantity?has_content && memoryQuantity?has_content >,</#if>
52 </#if>
53
54 <#if stringUtil.equals(specification.specificationKey, "ram")>
55 <#assign memoryQuantity = specification.value />
56
57 <#if memoryQuantity?has_content>
58 ${memoryQuantity} GB RAM
59 </#if>
60 </#if>
61 </#if>
62 </#list>
63</#if>
Edition
CE, EE
PRICE
处理模板时发生错误。
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 16, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 16, column 1]
----
1<#assign
2 channelId=""
3 channels=restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
4 filteredSpecifications=[] />
5
6<#list channels.items as channel>
7 <#if channel.name=="Marketplace Channel">
8 <#assign channelId = channel.id />
9 </#if>
10</#list>
11
12<#if (CPDefinition_cProductId.getData())??>
13 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
14</#if>
15
16<#if specifications?has_content && specifications.items?has_content>
17 <#list specifications.items?sort_by("specificationKey") as specification>
18 <#if specification.specificationKey?has_content>
19 <#if stringUtil.equals(specification.specificationKey, "price-model" )>
20 <#assign priceModel = specification.value />
21 <#if priceModel?has_content>
22 ${priceModel}
23 </#if>
24 </#if>
25 </#if>
26 </#list>
27</#if>
help & support
Terms & Conditions
SHARE LINK
HTML Example
A paragraph is a self-contained unit of a discourse in writing dealing with a particular point or idea. Paragraphs are usually an expected part of formal writing, used to organize longer prose.