[
https://issues.apache.org/jira/browse/ROL-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-1785.
---------------------------
Resolution: Later
Item from 2009. Greg, until we get much larger I think what we presently have
is sufficient. If the blog admin shuts off customization of themes, he
generally doesn't want the themes not to change, period -- which would include
both switching the themes and altering them, so disabling the Design tab
entirely would appear appropriate. There's just not enough demand yet for "I
don't want the themes to be customized, but it's OK for the user to change the
theme entirely." Also, if we partially altered the Design tab to just allow
theme-switching we'd also have to hide all the text implying that the theme can
also be customized, cumbersome work to do.
> Design menu not showing when themes.customtheme.allowed=false
> -------------------------------------------------------------
>
> Key: ROL-1785
> URL: https://issues.apache.org/jira/browse/ROL-1785
> Project: Apache Roller
> Issue Type: Bug
> Components: Themes and Macros
> Affects Versions: 5.0
> Reporter: Greg Huber
> Assignee: Roller Unassigned
> Priority: Minor
>
> In editor-menu.xml there is an option set to not show the design menu if
> themes.customtheme.allowed is set to false.
> ie:
> enabledProperty="themes.customtheme.allowed">
> This will completely disable the theme switching also. There is a action:
> <action name="themeEdit!*" method="{1}"
>
> class="org.apache.roller.weblogger.ui.struts2.editor.ThemeEdit">
> <result name="input" type="tiles">.ThemeEdit</result>
> <result name="input-sharedonly"
> type="tiles">.ThemeEditSharedThemesOnly</result>
> </action>
> that takes care of this and only allows theme switching. I am not sure if
> this is now what it is supposed to do ie completelt disable themes, we loose
> functionality if it is.
> Also .ThemeEditSharedThemesOnly is missing from tiles.xml.
> Cheers Greg
--
This message was sent by Atlassian JIRA
(v6.2#6252)
