Reasons tablibs wouldn't work in an ADT? Reasons tablibs wouldn't work in an ADT? https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=119188176 2026-04-04T03:38:53Z 2026-04-04T03:38:53Z RE: Reasons tablibs wouldn't work in an ADT? Sushil Patidar https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=119190185 2020-05-19T06:21:22Z 2020-05-19T06:21:22Z Hi,It doesn&#39;t make any difference for the taglib to work in any scope. Probably the reason for error is something different.It looks like in the global scope attributes passed are not correct. And the specific line is  throwing null values.Detailed stack trace would be helpful to identify the cause of the error.Regards Sushil Patidar 2020-05-19T06:21:22Z Reasons tablibs wouldn't work in an ADT? Lee Jordan https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=119188175 2020-05-18T19:03:42Z 2020-05-18T19:03:42Z <html><head></head><body>Anyone know of a reason why a taglib wouldn't work in an asset publisher ADT?<br><br>I'm trying to take a copy of this template:<br><a href="https://github.com/liferay/liferay-portal/blob/master/portal-web/test/functional/com/liferay/portalweb/dependencies/adt_asset_publisher_rich_summary.ftl">https://github.com/liferay/liferay-portal/blob/master/portal-web/test/functional/com/liferay/portalweb/dependencies/adt_asset_publisher_rich_summary.ftl</a><br><a href="https://github.com/liferay/liferay-portal/blob/master/portal-web/test/functional/com/liferay/portalweb/dependencies/adt_asset_publisher_rich_summary.ftl"></a><br>Into my own template to customize the rich summary.&nbsp; The document in my asset publisher has a related document and the template above works in 7.0. However a copy of that template in the global scope refuses to bring in taglibs. The error I get on related assets from that macro is ...<br><br><pre><code>The following has evaluated to null or missing: ==&amp;gt; liferay_asset["asset-links"] [in template "20116#20160#379048" at line 39, column 19] ---- Tip: It's the final [] step that caused this error, not those before it.</code></pre></body></html> Lee Jordan 2020-05-18T19:03:42Z