cPanel & WHM Version 98 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Add More Control to Paper Lantern and Custom Styles

PCZero shared this idea 6 years ago
Open Discussion

Paper Lantern is well on its was to being a good UI, however it still has a lot of weaknesses and features form the existing X3 that have been omitted so far. This makes PL a big downgrade form X3. Please add back the following item.

ACTIVATE/DEACTIVATE STYLES - I see no way to limit the styles available to my customers. As I could in X3, I want them ONLY to be able to choose from my custom PL styles and not have the 'basic' or 'retro' canned styles available. Please provide a way to do this. There is really no point to even having custom styles if users can still select the canned ones.

Replies (5)

photo
1

This was requested earlier. The request was marked complete BUT the instructions provided ONLY included disabling the entire PL theme. I asked then (and again now) how to ONLY disable certain styles of the PL theme, specifically the canned "default" and "retro" ones so that users will only be allowed to use the custom styles that we create. In X3 this was accomplished by enabling/disabling the styles in the live editor. Until this is done there really is no use at all in making custom styles for PL since you cannot make sure your customers use them.

photo
2

The basic theme cannot be disabled as it represents the fundamental styles we have to ship in order to implement the layout and widgets from our style guide. Selecting it is effectively the same as saying 'I don't want any styles'.


After x3 has been fully deprecated, we will be deprecating the 'Retro' style as it impedes the continued evolution of Paper Lantern. Many of the things we have planned for Paper Lantern will be unavailable in the Retro Style and, over time, the value of continuing to maintain the retro look will diminish.

photo
1

This is 100% totally not only an unacceptable response but it is absurd and makes no sense what so ever. You can SHIP a style but that does not mean that I have to allow my customers have it as a style to select from along with my custom styles. It should simply be a matter of adding a feature in the WHM interface that flags any given style to be displayed as available to my customers in the cPanel interface. Adding a 'display this style' field/flag would easily accomplish this. Perhaps with the limitations of the current code of PL you cannot disable the standard style, but that is the exact programming issue that needs to be fixed if that is the case. I understand the desire for the team to have a new look and feel to the cPanel interface (whether it is better to any degree is a matter of taste), however as is the point in all of my requests this is simply asking that the new theme does not be brought to life until it has the same underlying functionality as what it is replacing. Not having the ability to disable the canned stock style is absurd and completely defeats the purpose of having multiple custom styles for my custom to select from. The teams recognition of this basic fact is proven by the ability to do just hat I am asking within the X3 theme. That point is 100% not debatable by anyone.

photo
1

Awaiting response as to why adding a simple flag to toggle display of individual styes within PL would not be done in order to add the functionality of the enable check box in the X3 live editor.

photo
1

I would really like to be able to disable the "Retro" theme option in my user's cPanels. (In fact, would like to be able to set the cPanel theme choices to only custom ones that I customize). And as you can see above, 3 years ago cPanelAdamF said:

"...we will be deprecating the 'Retro' style as it impedes the continued evolution of Paper Lantern. Many of the things we have planned for Paper Lantern will be unavailable in the Retro Style..."

As far as I can tell, there's still no way for us to remove / disable the "Retro" theme. :(

photo
1

Thanks for your feedback! That's definitely a use case that is worth considering. We don't have any updates on this at the moment, but please make sure to vote for the features you'd like to see implemented. When we have an update, we'll make sure to post here.

Replies have been locked on this page!