掲示板
Asset publisher "$dlFileEntry.getIcon()" not working
7年前 に Ra Jo Ga Cha によって更新されました。
Asset publisher "$dlFileEntry.getIcon()" not working
Junior Member 投稿: 77 参加年月日: 17/01/19 最新の投稿
The icons for the attached documents aren't been shown properly, "$dlFileEntry.getIcon()" isn't working because the final URL is something like "there/are/the/icons/.png", so "$fichIconPre$dlFileEntryIcon$fichIconPost" is just concatenating URL+blank+iconformat.
This was working good in 6.1 but upgrading to 6.2 I can't get it working. I've tried with standard template for standard web contend in a standard asset publisher disabling my plugins but it's still unable to get the type of document.
This was working good in 6.1 but upgrading to 6.2 I can't get it working. I've tried with standard template for standard web contend in a standard asset publisher disabling my plugins but it's still unable to get the type of document.
7年前 に Fernando Fernandez によって更新されました。
RE: Asset publisher "$dlFileEntry.getIcon()" not working
Expert 投稿: 396 参加年月日: 07/08/22 最新の投稿
Hi Ra,
This code works well in my portlets on 6.2.
I know it's not exactly the same situation as yours but I hope it can help.
Fernando
This code works well in my portlets on 6.2.
String fileIcon = "<img src="\"/html/themes/control_panel/images/file_system/small/"+fileEntry.getIcon()+".png\"">";
I know it's not exactly the same situation as yours but I hope it can help.
Fernando
7年前 に Ra Jo Ga Cha によって更新されました。
RE: Asset publisher "$dlFileEntry.getIcon()" not working
Junior Member 投稿: 77 参加年月日: 17/01/19 最新の投稿
Hi Fernando,
I wasn't still able to get it that way, sounds good but by any reason it's not working for me. Finally achieved it getting a substring from the name of the file, in this case there was a customized class that eased this but probably there are Liferay core methods to reach this same solution.
Thanks for your help!
I wasn't still able to get it that way, sounds good but by any reason it's not working for me. Finally achieved it getting a substring from the name of the file, in this case there was a customized class that eased this but probably there are Liferay core methods to reach this same solution.
Thanks for your help!