Ask Questions and Find Answers

Hey Matteo,

Sorry for the frustration. I'd try to see if you can use the Impl class and this method. If calling

${journalContentImpl}

doesn't work try calling

${journalContent}

If you have article Id you can pass in the other variables really easily with variables from init.ftl

This was a frustrating read ... the OP isn't wanting to embed a portlet but a web content article. I would like to do this to add a global footer links section in 7.0 but the trouble would be that the article ID's would be different on DEV QA and Production servers. I looked at adding the article ID in the look-and-feel.xml as a theme custom field, that didn't seem to work.

Since this is the first result in a google search for this subject I think it's useful too add that since some time ago you can use the JSP taglibs in freemarker. 
This means that, to display an article  in the footer  you can include something like this in your theme's portal_normal.ftl:

<@liferay_journal["journal-article"]
    articleId=footer_article_id
    groupId=page_group.groupId
/>

Additionally, if you want to use a theme setting config you must:
 
1. Add the setting to the liferay-look-and-feel.xml file from your theme

<settings>
&nbsp; &nbsp; <setting configurable="true" key="footer-article-id" type="text"  />
</settings>

2. Convert the setting into a variable in init_custom.ftl

<#assign footer_article_id = getterUtil.getString(themeDisplay.getThemeSetting("footer-article-id"))/>

HTH

Fernando

That would work for sure, but I have 500 sites. Nobody on my team is going to go through 500 sites setting a theme setting, multiply that by 3 because we have three environments. Nope.  The issue as stated with the article ID, it's going to be different between three environments, so you can't deploy the theme to different environments with an article ID hard-coded.

Also ... defaultPreferences="${freeMarkerPortletPreferences}" doesn't seem to work and there's zero helpful documentation, beyond setting the decorator to borderless. Which ok is helpful but that one example doesn't then tell anyone how to access actual portlet configurations, there's no codex or index of these possibilities, in fact there is zero documentation on the inbuilt portlets for developers period. Liferay documentation is written with a lot of assumptions by people who are close to Liferay. Nobody else has a chance with the documentation. Litterally the documentation is ok you can set barebones, you're a pro!!!

The only suggestion seems to be to get the portlet preferences by looking at the database? A front end developer is not going to be looking at a database table, sorry they just won't.

I am using theme settings though to allow users to hide show UI elements though.