Ask Questions and Find Answers

Hi Alessandro --

Looks like you are stuck with it, sort of. If you look at the JournalArticleAssetRenderer you will see this code (and where the version is added).

[code]@Override
public String getURLViewInContext(
      LiferayPortletRequest liferayPortletRequest,
      LiferayPortletResponse liferayPortletResponse,
      String noSuchEntryRedirect)
   throws Exception {

   ThemeDisplay themeDisplay =
      (ThemeDisplay)liferayPortletRequest.getAttribute(
         WebKeys.THEME_DISPLAY);

   Layout layout = _article.getLayout();

   if (layout == null) {
      layout = themeDisplay.getLayout();
   }

   Group group = themeDisplay.getScopeGroup();

   if (!_isShowDisplayPage(group.getGroupId(), _article)) {
      String hitLayoutURL = getHitLayoutURL(
         layout.isPrivateLayout(), noSuchEntryRedirect, themeDisplay);

      if (Objects.equals(hitLayoutURL, noSuchEntryRedirect)) {
         hitLayoutURL = getHitLayoutURL(
            !layout.isPrivateLayout(), noSuchEntryRedirect,
            themeDisplay);
      }

      return hitLayoutURL;
   }

   if (group.getGroupId() != _article.getGroupId()) {
      group = GroupLocalServiceUtil.getGroup(_article.getGroupId());
   }

   if (_assetDisplayPageFriendlyURLProvider != null) {
      String friendlyURL =
         _assetDisplayPageFriendlyURLProvider.getFriendlyURL(
            getClassName(), getClassPK(), themeDisplay);

      if (Validator.isNotNull(friendlyURL)) {
         return friendlyURL;
      }
   }

   String groupFriendlyURL = PortalUtil.getGroupFriendlyURL(
      LayoutSetLocalServiceUtil.getLayoutSet(
         group.getGroupId(), layout.isPrivateLayout()),
      themeDisplay);

   StringBundler sb = new StringBundler(5);

   sb.append(groupFriendlyURL);
   sb.append(JournalArticleConstants.CANONICAL_URL_SEPARATOR);
   sb.append(_article.getUrlTitle(themeDisplay.getLocale()));
   sb.append(StringPool.SLASH);
   sb.append(_article.getVersion());

   return PortalUtil.addPreservedParameters(themeDisplay, sb.toString());
}

Unfortunately, there is no logic around the version (something like a configuration setting or a property to toggle it on and off) which means I think the out of the box is with the version and that's it.  There is something you could try though, if you don't want to use the freemarker bult-ins. You COULD choose to create an override for the JournalArticleAssetRendererFactory and then in that override return you own CustomJournalArticleRenderer, which would basically be identifcal, except remove the line where the version is added to the string bundler. 

Unfortunately, I don't think that you can extend the JournalArticleAssetRenderer that Liferay provides out of the box (it doesn't appear to be exported?) which means you either have to copy the code, or use David's trick for forcing packages to be exported. Either way, you should give some thought to the approach because it means that future changes to the JournalArticleAssetRenderer may require you to intervene to take advantage of them. Freemaker string functions, as you are doing right now, maybe in fact be your safest bet.

Thank you, Andrew, I see...but this appended version was added recently, because in version 7.0 it was not present.
I solved with the following snippet:

<#list entries as curEntry>
  <#assign urlViewInContext = curEntry.getAssetRenderer().getURLViewInContext(renderRequest, renderResponse, currentURL) />
  <#assign versionCharIdx = urlViewInContext?last_index_of("/") - 1 />
  <#assign urlView = urlViewInContext?string[0..versionCharIdx] />
&nbsp; <a href="${urlView}" target="_self">${curEntry.getTitle(locale)}</a>
<!--#list-->