留言板

look and feel for portlets not working

Tameez Lal,修改在9 年前。

look and feel for portlets not working

New Member 帖子: 20 加入日期: 13-10-25 最近的帖子
Hi ,
We are facing an issue , where we are able to see the "look and feel" button on each portlet. But on click , it doesn't show up the "look and feel" menu. Earlier it used to work, and we used to change the setting in the "look and feel" menu . But, we don't know since when it has stopped working. As we have a critical issue on our Prod system, where we need to access this menu to make a portlet work.

Here are few points we have checked.

1. Admin user is able to click on the button but no menu comes up.
2. It seems if we create a new page and put a Liferay's built-in portlet on it. The issue still exists.
3. There is no exception thrown in the back end.
4. If we remove our theme and use Liferay's default theme, still the issue is there.
5. The issue not independent of browser. It doesn't work on any of them.


Hoping for a quick response on this.

Thanks
Tameez Lal
thumbnail
Olaf Kock,修改在9 年前。

RE: look and feel for portlets not working

Liferay Legend 帖子: 6403 加入日期: 08-9-23 最近的帖子
make sure that you indeed are using the default Liferay theme when you switch back to classic. I've seen situations where people messed up with the built-in theme in order to quick-fix something, breaking it on the go. To check this, you might want to run a diff on your Liferay installation vs. a fresh unzip and have a look especially at the themes subdirectories.
Tameez Lal,修改在9 年前。

RE: look and feel for portlets not working

New Member 帖子: 20 加入日期: 13-10-25 最近的帖子
Thank you for your valuable replay
I have resolved that issue, actually We have overwritten a property (portlet.add.default.resource.check.whitelist) in portal-ext.properties without including the original values when we overwrote this property via portal-ext.properties, the default values got deleted
thumbnail
Olaf Kock,修改在9 年前。

RE: look and feel for portlets not working

Liferay Legend 帖子: 6403 加入日期: 08-9-23 最近的帖子
Thanks for reporting this fix back - hope it helps the next one searching for this or a similar issue. Happy to see that you solved the problem already.