<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Gerd,</p>
<p>great that you got it working. The Errors are due to the mercury
template version. Commenting out the lines in the template is very
sufficient.</p>
<p>The searchform module was my fault - it was present in earlier
versions, but was integrated in the default documentation module
for the 11th version documentation - so it's simply not existing
anymore.</p>
<p>Best, Daniel.<br>
</p>
<div class="moz-cite-prefix">Am 28.05.20 um 21:30 schrieb Gerd
Schrick:<br>
</div>
<blockquote type="cite"
cite="mid:960559851.464478.1590694201503@webmail.strato.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="UTF-8">
<div> Thank you Daniel! <br>
</div>
<div> <br>
</div>
<div> It was easy to follow your detailed description. <br>
</div>
<div> <br>
</div>
<div> Just two small issues: <br>
</div>
<div> a) module "com.alkacon.opencms.documentation.searchform" is
not contained in the modulesZip folder (so I didn't install it)
<br>
</div>
<div> <br>
</div>
<div> b) when I opened /opencms-documentation/introduction/ I got
these three errors: <br>
</div>
<div> An error occurred.<br
/>/WEB-INF/jsp/offline/system/modules/com.alkacon.opencms.documentation/templates/documentation-template.jsp
(line: 68, column: 0) According to the TLD or the tag file,
attribute contentUri is mandatory for tag meta-info <br>
An error occurred.<br
/>/WEB-INF/jsp/offline/system/modules/com.alkacon.opencms.documentation/templates/documentation-template.jsp
(line: 151, column: 1) According to the TLD or the tag file,
attribute contentPropertiesSearch is mandatory for tag pageinfo
<br>
An error occurred.<br
/>/WEB-INF/jsp/offline/system/modules/com.alkacon.opencms.documentation/templates/documentation-template.jsp
(line: 157, column: 0) According to the TLD or the tag file,
attribute contentPropertiesSearch is mandatory for tag
privacy-policy-banner </div>
<div> <br>
</div>
<div> I solved that by commenting out the respective lines in the
mentioned template JSP. <br>
</div>
<div> Is this possibly related to the missing searchform module? <br>
</div>
<div> <br>
</div>
<div> Best regards, <br>
</div>
<div> Gerd <br>
</div>
<blockquote type="cite">
<div> Daniel Seidel <a class="moz-txt-link-rfc2396E" href="mailto:d.seidel@alkacon.com"><d.seidel@alkacon.com></a> hat am 27. Mai
2020 07:32 geschrieben: </div>
<div> <br>
</div>
<div> <br>
</div>
<p>Hi Gerd,</p>
<p>currently the ready-made modules are not provided, but you
can get the documentation from <a
href="https://github.com/alkacon/opencms-documentation/tree/branch_11_0_x"
moz-do-not-send="true">https://github.com/alkacon/opencms-documentation/tree/branch_11_0_x</a>
where you find and checkout the sources. <br>
</p>
<p>To build the modules:</p>
<p> - change the 'build_directory' property in the
'gradle.properties' file to your favorite folder (e.g.
'build') and change the 'opencms_version' to '11.0.1'.</p>
<p> - then run './gradlew bindist' in the repositories main
folder.</p>
<p>Afterwards, you'll find find the modules in a 'moduleZip'
subdirectory of the build folder and moreover some libs in the
'libs' subfolder. Copy the libs to your OpenCms installation's
lib folder and then install the modules:</p>
<p> - com.alkacon.opencms.documentation</p>
<p> - com.alkacon.opencms.documentation.content</p>
<p> - com.alkacon.opencms.documentation.searchform</p>
<p>The other modules you do not need.</p>
<p>When done, in the default-site you have a subfolder
"opencms-documentation" holding the documentation. And you can
play with the examples below the "demo" folder.</p>
<p>Best, Daniel.<br>
</p>
<div class="moz-cite-prefix"> <br>
</div>
<div class="moz-cite-prefix"> Am 27.05.20 um 03:37 schrieb Gerd
Schrick: <br>
</div>
<blockquote type="cite">
<div> Oh stupid me! ... <br>
</div>
<div> <br>
</div>
<div> Thank you Daniel, </div>
<div> you're right, I was struggling with this (great!)
feature but in a weird way: <br>
</div>
<div> In the template JSP I accidentally put the reference to
the css for the editor in that property (instead of property
"template"). <br>
</div>
<div> So your hint solved 2 problems: <br>
</div>
<div> a) the selection in the List editor works as expected
and <br>
</div>
<div> b) the editor css now has an obvious effect ;-) <br>
</div>
<div> plus: <br>
</div>
<div> I now understand the idea of the
"template.display.types" property (although I already came
across that part in the documentation before). <br>
</div>
<div> <br>
</div>
<div> A question regarding the documentation: <br>
</div>
<div> Are there documentation modules (as mentioned here: <a
href="https://documentation.opencms.org/opencms-documentation/demos/"
moz-do-not-send="true">https://documentation.opencms.org/opencms-documentation/demos/</a>
) for 11.0.1? <br>
</div>
<div> Or can I lookup the template code elsewhere? Git? <br>
</div>
<div> Especially the code for the breadcrumbs navigation? <br>
</div>
<div> In the List and detail pages III demo here: <br>
</div>
<div> <a
href="https://documentation.opencms.org/opencms-documentation/demos/lists-and-detail-pages-iii/"
moz-do-not-send="true">https://documentation.opencms.org/opencms-documentation/demos/lists-and-detail-pages-iii/</a>
<br>
</div>
<div> when I click on a list entry, it shows up in the
breadcrumb nav (of the detail page). <br>
</div>
<div> How is this done? <br>
</div>
<div> <br>
</div>
<div> Best regards, <br>
</div>
<div> Gerd <br>
</div>
<blockquote type="cite">
<div> Daniel Seidel <a href="mailto:d.seidel@alkacon.com"
class="moz-txt-link-rfc2396E" moz-do-not-send="true"><d.seidel@alkacon.com></a>
hat am 26. Mai 2020 22:40 geschrieben: </div>
<div> <br>
</div>
<div> <br>
</div>
<p>Hi Gerd,</p>
<p>I'm not completely sure, but you may struggle with this
feature:</p>
<dl>
<dt> template.display.types </dt>
<dd>
<p>This option is mainly useful if you have several
websites with different templates on your OpenCms
instance and different templates use different sets of
display formatters.</p>
<p>If the option is provided, the property <code>template.display.type</code>
is looked up recursively at the currently edited
content and it's parent folders. If not found, it is
looked up at the template JSP used at the place where
the edited content is located. The property should
contain a comma-separated list of container types. If
the property is found and not empty, display
formatters will be selectable only if they match to
one of the containers of the given types. See the <a
href="https://documentation.opencms.org/opencms-documentation/content-in-opencms/formatters-and-their-configuration/#formatter_configuration_basic_options"
moz-do-not-send="true">formatter configuration</a>
to see how matching containers are specified. If the
property is not found, the matching conditions are
simply ignored.</p>
</dd>
<dt> (see <a class="moz-txt-link-freetext"
href="https://documentation.opencms.org/opencms-documentation/content-in-opencms/defining-a-content-type/defining-the-contents-behavior/adjusting-the-contents-appearance-in-the-content-editor/widget-configuration/#2.25"
moz-do-not-send="true">https://documentation.opencms.org/opencms-documentation/content-in-opencms/defining-a-content-type/defining-the-contents-behavior/adjusting-the-contents-appearance-in-the-content-editor/widget-configuration/#2.25</a>)
</dt>
</dl>
<p>Probably somewhere the property is set to "mercury-list"
(even in your own site/template) and therefor, your
formatters are not displayed.</p>
<p>Best, Daniel.<br>
</p>
<div class="moz-cite-prefix"> Am 26.05.20 um 19:46 schrieb
Gerd Schrick: <br>
</div>
<blockquote type="cite">
<div> Hi Daniel, <br>
</div>
<div> <br>
</div>
<div> thank you for your reply ... but the selection is
still empty. <br>
</div>
<div> <br>
</div>
<div> Yes, that's all done (as far as I can see); </div>
<div> Regarding config, my module and site is similar (but
way simpler) to the Demo site and the module
"alkacon.mercury.template": <br>
</div>
<div> - formatters and resource types configured in a
sitemap master config in the module <br>
</div>
<div> - in the site's sitemap config this master config is
included <br>
</div>
<div> - in all formatters Match is set to container type
"maincontent" (the only container used in my
site/template) <br>
</div>
<div> - 2 (intended to be used in the list) of the 4
formatters have the "display formatter type" set <br>
</div>
<div> - all formatters work in the template/pages <br>
</div>
<div> <br>
</div>
<div> INTERESTING 1: </div>
<div> I copied my list config to the "shared" folder then
right click->Edit and all display formatters (Mercury
+ mine) are listed <br>
</div>
<div> INTERESTING 2: </div>
<div> (that finally confused me ;) I set/added in
formatter config Container type to "mercury-list" and my
formatter immediately showed up in the list editor
within the Demo site!? (did not add it to the Demo
site's config anywhere) <br>
</div>
<div> <br>
</div>
<div> So that seems that the empty selection in my site is
somehow related to the formatters' Match/container type.
<br>
</div>
<div> But how? </div>
<div> I wasn't able to figure out why seemingly only
container type "mercury-list" is what matters whereas
eg. "accordion" or "article" don't <br>
</div>
<div> (as detected in
/system/modules/alkacon.mercury.template/formatters/display/accordion/article.xml)
<br>
</div>
<div> <br>
</div>
<div> And from where does the List (config/editor/app)
know what container type will match when I juat create a
List in the List Workspace App (and not on a
page/tamplate)? <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
<div> Thank (all of) you in advance for any de-confusing
hints :-) <br>
</div>
<div> <br>
</div>
<div> Best, <br>
</div>
<div> Gerd <br>
</div>
<blockquote type="cite">
<div> Daniel Seidel <a class="moz-txt-link-rfc2396E"
href="mailto:d.seidel@alkacon.com"
moz-do-not-send="true"><d.seidel@alkacon.com></a>
hat am 26. Mai 2020 07:54 geschrieben: </div>
<div> <br>
</div>
<div> <br>
</div>
<p>Hi Gerd,</p>
<p>did you activate your display formatters in the
configuration or in some (sub-)sitemap config? And not
disable them in some (sub-)sitemap config? Do the
formatters have any Match (via container type)
defined? If all this is the case and a value for
display formatter type is provided, you should be able
to select the formatter.<br>
</p>
<p>Best, Daniel.<br>
</p>
<div class="moz-cite-prefix"> Am 25.05.20 um 19:16
schrieb Gerd Schrick: <br>
</div>
<blockquote type="cite">
<div class="default-style"> Dear all, <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> (in 11.0.1) </div>
<div class="default-style"> I have a resource type
"sd-project" and two formatters for this type, both
with a non-empty "Display formatter type" setting
(current value: "list-sd-project:compact"; also
tried other values, e.g. the suggested default
"display"). <br>
</div>
<div class="default-style"> I then created a List
following the docu "Lists with the integrated list
type" </div>
<div class="default-style"> here: <a
href="https://documentation.opencms.org/opencms-documentation/content-in-opencms/lists-and-detail-pages/building-lists/lists-with-the-integrated-list-type/"
class="moz-txt-link-freetext"
moz-do-not-send="true">https://documentation.opencms.org/opencms-documentation/content-in-opencms/lists-and-detail-pages/building-lists/lists-with-the-integrated-list-type/</a>
<br>
</div>
<div class="default-style"> and "Lists and detail
pages III" <br>
</div>
<div class="default-style"> here: <a
href="https://documentation.opencms.org/opencms-documentation/demos/lists-and-detail-pages-iii/"
class="moz-txt-link-freetext"
moz-do-not-send="true">https://documentation.opencms.org/opencms-documentation/demos/lists-and-detail-pages-iii/</a>
<br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> My problem is, that the
dropdown "Content type" in the list's config (app)
still remains empty, </div>
<div class="default-style"> although as the docu (2nd
link) says: <br>
</div>
<div class="default-style"> "The selectable formatters
are collected automatically. To get your formatter
to the list, the " Display formatter type" option in
the formatter configuration has to be set:" <br>
</div>
<div class="default-style"> what is the case for both
of my formatters. <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> When I edit the list
config's control code (according to what I see in
the lists of the Demo site) </div>
<div class="default-style"> and set/add element <br>
</div>
<div class="default-style">
<TypesToCollect>sd-project:efb48fe8-9e33-11ea-aabc-485b3939753f</TypesToCollect>
</div>
<div class="default-style"> ("sd-project" is the type;
UUID is the one of the formatter config I'd like to
use) <br>
</div>
<div class="default-style"> anything seems to work
perfectly, except the "Content type" selection (that
now only shows the entered value as-is). <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> In the Demo site the
selection shows many entries all with nice names and
(since hours) I tried to figure out the difference
... but still w/o success. <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> Obviously I missed
something, so my questions are: </div>
<div class="default-style"> What (in addition) has to
be done that the formatters show up? <br>
</div>
<div class="default-style"> Is there some special
logic (naming?) for the formatter's "Display
formatter type" setting to follow? <br>
</div>
<div class="default-style"> Anything else to be
configured somewhere? <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> Any help is greatly
appreciated :-) <br>
</div>
<div class="default-style"> <br>
</div>
<div class="default-style"> Best regards, <br>
</div>
<div class="default-style"> Gerd <br>
</div>
<br>
<pre class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev" class="moz-txt-link-freetext" moz-do-not-send="true">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature">--
Kind Regards,
Daniel.
-------------------
Daniel Seidel
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a href="http://www.alkacon.com" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.alkacon.com</a> - <a href="http://www.opencms.org" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.opencms.org</a> </pre>
_______________________________________________ <br>
This mail is sent to you from the opencms-dev mailing
list <br>
To change your list options, or to unsubscribe from the
list, please visit <br>
<a class="moz-txt-link-freetext"
href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev"
moz-do-not-send="true">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<pre class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev" moz-do-not-send="true">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
_______________________________________________ <br>
This mail is sent to you from the opencms-dev mailing list <br>
To change your list options, or to unsubscribe from the
list, please visit <br>
<a
href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev"
class="moz-txt-link-freetext" moz-do-not-send="true">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<pre class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev" class="moz-txt-link-freetext" moz-do-not-send="true">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature">--
Kind Regards,
Daniel.
-------------------
Daniel Seidel
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a href="http://www.alkacon.com" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.alkacon.com</a> - <a href="http://www.opencms.org" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.opencms.org</a> </pre>
_______________________________________________ <br>
This mail is sent to you from the opencms-dev mailing list <br>
To change your list options, or to unsubscribe from the list,
please visit <br>
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a> <br>
<br>
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Kind Regards,
Daniel.
-------------------
Daniel Seidel
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a class="moz-txt-link-freetext" href="http://www.alkacon.com">http://www.alkacon.com</a> - <a class="moz-txt-link-freetext" href="http://www.opencms.org">http://www.opencms.org</a> </pre>
</body>
</html>