Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.8.0-b1
    • Fix Version/s: 5.8.0-b1
    • Component/s: Client Interface
    • Labels:
      None

      Description

      Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

      This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

      Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

      In terms of naming, open for discussion, but something like this might work:

      ?bltemplate=templatename
      ?bltheme=themename-or-ID

      ?bltemplate=templatename&bltheme=themename-or-ID

      Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

      If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

      See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename

        ?bltemplate=templatename&bltheme=themename

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename

        ?bltemplate=templatename&bltheme=themename

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        admin Paul Phillips made changes -
        Description Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename

        ?bltemplate=templatename&bltheme=themename

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename-or-ID

        ?bltemplate=templatename&bltheme=themename

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        admin Paul Phillips made changes -
        Description Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename-or-ID

        ?bltemplate=templatename&bltheme=themename

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        Theme developers like to preview their themes on a working Blesta installation. Companies like to preview a theme they are working on before making it live for everyone. Many applications allow this by passing the name of the template/theme in the URL. For example ?variable=THEMENAME

        This would control which template set is loaded, for example ?variable=bootstrap would load the default theme (which would happen without doing this if it's the one selected under Settings > Company > Look & Feel > Template), but ?variable=mytheme would load the /app/views/client/mytheme theme instead.

        Additionally, we should look at including a parameter for the color theme in Blesta also. You may want to change both the template, and the color theme, or just one or the other.

        In terms of naming, open for discussion, but something like this might work:

        ?bltemplate=templatename
        ?bltheme=themename-or-ID

        ?bltemplate=templatename&bltheme=themename-or-ID

        Since the terms template and theme are very generic, prepending those with "bl" for blesta may avoid any future conflict in naming.

        If it's not easy to keep the variable in the URL persistently, we could write a cookie with the details.

        See original feature request here https://requests.blesta.com/topic/specific-theme-preview-without-activation
        admin Paul Phillips made changes -
        Rank Ranked higher
        admin Paul Phillips made changes -
        Rank Ranked lower
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        abdy Abdy Franco made changes -
        Assignee Abdy Franco [ abdy ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 7 hours, 29 minutes [ 26940 ]
        Worklog Id 16449 [ 16449 ]
        abdy Abdy Franco made changes -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Story Points 3
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.8.0 Sprint 3 [ 179 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Status In Review [ 5 ] Closed [ 6 ]
        admin Paul Phillips made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        admin Paul Phillips made changes -
        Affects Version/s 5.8.0-b1 [ 11742 ]
        Affects Version/s 4.12.0 [ 11500 ]
        admin Paul Phillips made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        admin Paul Phillips made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Assignee Abdy Franco [ abdy ] Paul Phillips [ admin ]
        admin Paul Phillips made changes -
        Fix Version/s 5.8.0-b1 [ 11742 ]
        Fix Version/s Short Term [ 10800 ]
        admin Paul Phillips made changes -
        Status Reopened [ 4 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.8.0 Sprint 3 [ 179 ] 5.8.0 Sprint 3, 5.8.0 Sprint 5 [ 179, 184 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            admin Paul Phillips
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              4/Aug/23

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 7 hours, 29 minutes
              7h 29m

                Agile