@AswiniLakshminarayanan topicmeta metadata works when topicmeta tags are
directly child nodes put under map. Something like this. Product
Keyword 1234 It is not working
if it is under a keydef node. So is it possible to get the value out of
this topicmeta OR we have to change the placement of the topicmeta?
Product Keyword 1234
Using AEM Guides on Cloud AEM 1. Created a sample ditamap 2. Tried to
generate a PDF using a sample preset created having a Hi-Tech OOTB
template did not create a PDF with TOC Does it need more settings? Or
this is an issue?
As you have already confirmed it works fine in local publisher (it means
you have enabled post method in servlet class and felix config also). I
believe your servlet path is /bin/pdf/view and in filters.any it is
allowing only GET method in your screenshot. Just allow post method for
the same path.
@AswiniLakshminarayanan Thank you for the explanation. A few questions
around this 1. We are not using bookmap where we can define bookmeta
tags. Can we using keydef tags keyword and map attribute 'product' value
as well in the plain map (not bookmap)? If yes what is the expression to
access them? Product Keyword
1234 2. Is it possible
to inject jcr:content or /jcr:content/metadata node properties of the
ditamap asset into native PDF publishing?
As explained here
it is mentioned we can also add metadata information as variables or
fields in your page layout. This metadata is stored in your source DITA
map content, and it can be easily inserted in your page layout. Please
provide a code syntax on how to get the values of these custom metadata
variables in the templates...
@VivekK 1. First question: Its good to hear the all the map dashboard
features are being added to current side where native PDF publishing is
available. But currently native publishing presets are available only
for that map. It is not feasible solution for authors to create presets
for every map. Hope we will have a ability to create the global presets
for all Map. 2. Do you have any timelines? like Nov 2022 or early 2023?
How do we use the metadata it in Native PDF publishing? Provide example
with a code syntax. This links
talks about how to create metadata but not how to use them in the .plt
file (code syntax to use that metadata)
Why this issue happens custom pages? In we-retail pages it works,
because cq.shared library is included as part of the page itself in the
one of the scripts for ex:
To fix the issue, copy the same the below lines code in any of the
head.html where head is included in your custom page scripts.