Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Theme Contributors Security
Hello all
I have created a theme contributor for my site, and the theming works. I'm using it mainly to theme individual portlets.
The thing is that only Admin users, or roles that have 'Permissions' access to the portlet are actually able to see the theme changes. Thing is i don't really want users to be able to access that section.
I've poured through the documentation on Theme Contributors and had a look for anything that allows a change in security but have come up short.
Any advise would be appreciated.
Thanks
I have created a theme contributor for my site, and the theming works. I'm using it mainly to theme individual portlets.
The thing is that only Admin users, or roles that have 'Permissions' access to the portlet are actually able to see the theme changes. Thing is i don't really want users to be able to access that section.
I've poured through the documentation on Theme Contributors and had a look for anything that allows a change in security but have come up short.
Any advise would be appreciated.
Thanks
Themes have zero to do with security.
Use your theme to style stuff.
Use the portal's UI to alter permissions.
Use your theme to style stuff.
Use the portal's UI to alter permissions.
I'm using it mainly to theme individual portlets.This sounds weird to me.
You should use the theme to do general styling. All styles that should be the same for all portlets should go to the theme (or maybe theme contributors). But styles that belong to a portlet should go into the portlet css. When you do that, users only get the css when they get the portlet.
Also: CSS has nothing to do with security. You can't rely on or use css to add security to your system. If you hide something with css, users can just use the developer console to unhide it.
I never touch theme contributors. More trouble than it's worth.
You need to have the use case to make them worth it.
For example, if you have say 5 different themes you need to manage and make changes to, a single theme contributor that can be applied to all 5 starts to have a great deal of appeal to you.
For example, if you have say 5 different themes you need to manage and make changes to, a single theme contributor that can be applied to all 5 starts to have a great deal of appeal to you.
Yup and since having five themes would be a nightmare I always tried to use color schemes because the biggest reason for us to have different themes would be to provide different colors.
SASS makes theme contributor's redundant.
SASS makes theme contributor's redundant.
Again, that is dependent upon your use case. 5 different themes because you are cohosting completely different organizations can make a different color scheme plan fall apart.
I'm not saying every solution deserves theme contributors, most can be handled with color schemes, theme parameterization, etc. But for those cases that can take advantage of them, they can be a good fit.
I'm not saying every solution deserves theme contributors, most can be handled with color schemes, theme parameterization, etc. But for those cases that can take advantage of them, they can be a good fit.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™