102 EDGE Version new whm theme
Hi
When I installed the 102 edge version for testing, I saw that the whm theme changed and I didn't like it at all.
Will we be able to use the old whm theme in version 102?
-
4- WHY cpanel has difficulty solving silly things as I mentioned in my previous topic It's hard to replace this: {.container-lg{max-width:1320px}} That is why ? {.container-lg{max-width:100%}}
The change you propose would have adverse affects on the readability of interfaces and ultimately cause design regression throughout features whose individual interfaces do not anticipate full screen widths. Should we see prevalent use of widescreen monitors in our analytics, we may reconsider this in the future. I'd encourage those who care deeply about widescreen support to let us know over on features.cpanel.net or to participate in Interface Analytics.
I would hate to bring to the table professional and decades long experience with website development but perhaps the cPanel team who are working on this update can use a modern concept such as Flexibox CSS design or even stacked inline boxes, whereby there's no need to set a specified maximum width size. Further, CPanel can still apply this maximum width clarification to only certain entities; and/or set a maximum width in situations where there's a widescreen display: width: 100%; max-width: 2100px /* or other dimension that exceeds single screen width */ You know you can even use @media queries to only set a wider view on screens that are not widescreens; seriously, the possibilities are limitless if you choose to actually build on them....0 -
For those interested in the reintroduction of a filter to the left nav, here's what that looks like. So far as I know, this is not currently in any public build but it should arrive soon (last few rounds of QA and then merge procedures left to do). alt="Screen Shot 2022-04-18 at 09.55.59.png">77365 Couple of things of note:
- It uses the same search algorithm as found in cPanel & WHM 98 and older for now. In a future version we are going to update that algorithm to make it more tolerant of typos and we'll sneak some more metadata about each link into the search index than before.
- It does not replace the search in the top navigation. That search will remain there and we'll continue to work on making that area more and more useful. (Not sure if anyone noticed yet, but it now returns Accounts in addition to features)
- Keyboard navigation should be roughly the same as in cPanel & WHM v98. Note the new keyboard shortcut to jump into this search, though.
0 -
I am grateful for the clarifications, these doubts are present since all this started I understand the situation regarding UX problems But I'm really frustrated, since I set up my company's identity on top of PAPER, it changes to JUPITER okay, but my displeasure is in the part that at this moment we can't customize the THEME, what's available is not possible to set up a visual identity I think they could at least release for the more experienced a way to customize their terms as they want until cpanel concludes what it's doing Unfortunately cpanel doesn't give deadlines for this freedom in customization, we don't know if it will be 1 month or 1 year from now It is difficult to destroy all the identity and practicality created on a layout. If you have a deadline I would be very grateful. Regarding the adjustment for wide screen monitors, I don't see it as a negative impact, I didn't even notice differences in the various monitors I have with such a modification.
Glad to be of help. I sympathize about the timing of Jupiter and setting up your company's visual identity. We knew we were going to have customers in that spot. If you'd like to stay on Paper Lantern, we're maintaining LTS support for it in v102 through the 2023-Q2 timeframe. I hope that gives you a wide window of time to make a plan. Customization support for Jupiter in :2083 (end-user interface) is an area I'd like to return to and improve. In v102 and later, we have the WHM " Home " cPanel " Customizations feature which supports both Jupiter and Paper Lantern...but the items you can customize in Jupiter needs expansion to truly enable everyone to set up a great experience for their users. (There's been plenty of demand for customizing the icons. With support for that in place you'd be able to return to Paper Lantern's icons if you prefer that.) The future is a bit hazy at the moment (lots of cool things in the pipeline) so I'm not really able to predict when we can return to this. As far as deadlines go, here's how the certain parts of the future plays out:
This is all fluid, though, so please look for updated expectations from us as these timeframes approach.Timing Expectation Now v102 continues into the STABLE and LTS tiers. v104 continues to rollout through the non-LTS tiers. The ). Completed translations begin to arrive to all supported versions (including v102). ~2023-Q1 v110, our next LTS candidate begins arriving on EDGE. ~2023-Q2 v110 enters our LTS tier, displacing v102 and ending all support for Paper Lantern for :2083. 0 -
Glad to be of help. I sympathize about the timing of Jupiter and setting up your company's visual identity. We knew we were going to have customers in that spot. If you'd like to stay on Paper Lantern, we're maintaining LTS support for it in v102 through the 2023-Q2 timeframe. I hope that gives you a wide window of time to make a plan. Customization support for Jupiter in :2083 (end-user interface) is an area I'd like to return to and improve. In v102 and later, we have the WHM " Home " cPanel " Customizations feature which supports both Jupiter and Paper Lantern...but the items you can customize in Jupiter needs expansion to truly enable everyone to set up a great experience for their users. (There's been plenty of demand for customizing the icons. With support for that in place you'd be able to return to Paper Lantern's icons if you prefer that.) The future is a bit hazy at the moment (lots of cool things in the pipeline) so I'm not really able to predict when we can return to this. As far as deadlines go, here's how the certain parts of the future plays out:
This is all fluid, though, so please look for updated expectations from us as these timeframes approach.Timing Expectation Now v102 continues into the STABLE and LTS tiers. v104 continues to rollout through the non-LTS tiers. The ). Completed translations begin to arrive to all supported versions (including v102). ~2023-Q1 v110, our next LTS candidate begins arriving on EDGE. ~2023-Q2 v110 enters our LTS tier, displacing v102 and ending all support for Paper Lantern for :2083.
Come on, Don't remove the paper lantern again, let customers choose their own choice importantly, or they will never pay cPanel and lost their own license in a few months, just like Netflix when you pay a subscription if you share your friends and you have to pay for $$ extra charging from Netflix, now they lost over 2 million for increasing the cost. You increased your own price for the cPanel license and limits the domain 5x total back in july 2019. Now you removed the style for customers who have a choice and lost their own style template and stuff from paper lantern and retro in 2022? I'm very surprised what cPanel would remove or Lack of interest/features in another 3 years.0 -
Glad to be of help. I sympathize about the timing of Jupiter and setting up your company's visual identity. We knew we were going to have customers in that spot. If you'd like to stay on Paper Lantern, we're maintaining LTS support for it in v102 through the 2023-Q2 timeframe. I hope that gives you a wide window of time to make a plan. Customization support for Jupiter in :2083 (end-user interface) is an area I'd like to return to and improve. In v102 and later, we have the WHM " Home " cPanel " Customizations feature which supports both Jupiter and Paper Lantern...but the items you can customize in Jupiter needs expansion to truly enable everyone to set up a great experience for their users. (There's been plenty of demand for customizing the icons. With support for that in place you'd be able to return to Paper Lantern's icons if you prefer that.) The future is a bit hazy at the moment (lots of cool things in the pipeline) so I'm not really able to predict when we can return to this. As far as deadlines go, here's how the certain parts of the future plays out:
This is all fluid, though, so please look for updated expectations from us as these timeframes approach.Timing Expectation Now v102 continues into the STABLE and LTS tiers. v104 continues to rollout through the non-LTS tiers. The ). Completed translations begin to arrive to all supported versions (including v102). ~2023-Q1 v110, our next LTS candidate begins arriving on EDGE. ~2023-Q2 v110 enters our LTS tier, displacing v102 and ending all support for Paper Lantern for :2083.
I see this deadline of up to 2023 as an okay time. However, I don't see a deadline for cpanel to make Jupiter really customizable with a functional documentation. This point is really worrying, even because of the rumors of the merging of plesk with cpanel. They could really give a possible prediction of the future of cpanel and when jupiter can really be modified at the development level and not only by WHM0 -
This point is really worrying, even because of the rumors of the merging of plesk with cpanel.
I can promise this is absolutely not a thing that is going to happen.0 -
I can promise this is absolutely not a thing that is going to happen.
They why do you seem to be actively trying to destroy WHM/Cpanel? The new ui is atrocious - and given the timescales mentioned earlier, its simply going to speed up our migration away from Cpanel in general. Congrats on doing a great job of destroying what was the go-to control panel for hosting. I wont waste my breath with suggestions, they never get listened to anyway in my experience - I'll just vote with my wallet instead!0 -
Again not sure what you're trying to say here. Not only do we actively engage here in the forums (primarily through @cPRex though often as individuals as well), we also actively engage on the features.cpanel.net site, send out surveys both in the interface and directly, and monitor feedback through tickets and other avenues. We are working to be more responsive to the feedback we gather, and you can read more about those efforts
0 -
@anton_latvia, @tandyuk, you are [COLOR=rgb(97, 189, 109)]correct 1000% I'll vote for my wallet more than cPanel's new UI, this is farewell... Canceling cPanel license. 0 -
I think the issue is a classic "shoot yourself in the foot" problem.... 1) Lack of clear communication: 4 months ago, cPanel should have been notifying inside the whm - perhaps at the top (INSTEAD of commercials?) "head's up - WHM theme is changing - see the blog for all the details" - with a link to a detailed article explaining why..... and perhaps even asking for feedback or "what do you love/hate" BEFORE forcing it on users.... I know there was a notification for the cPanel theme, but I was not aware of one for WHM. 2) Annoying your customers by focussing on something like this WHM change (and cPanel change) when so many people want cPanel Dev team to instead concentrate on delivering much needed features requests such as for example: there is an update on LB which is rather vague - though interesting to see a delivery date of Q4 2022 mentioned... we shall see how realistic that is after waiting ten yrs) While it appears the cPanel team are a bit gungho - I would like to thank you for listening and taking on board the requests to add back in the useful features to v102. 0 -
redacted 0 -
@anton_latvia, @tandyuk, you are [COLOR=rgb(97, 189, 109)]correct 1000% I'll vote for my wallet more than cPanel's new UI, this is farewell... Canceling cPanel license.
yeah.. i don't think many can do what you are saying... i mean, i can't force thousands of clients and tens of thousands of websites to move from cpanel to other panel because of this. lol. if you have a server for 1 site for yourself, then sure, if you don't like cpanel UI changes, vote with your money and change the software used. i wouldn't use Cpanel for 1 site only, too much money for 1 site. But i have thousands of clients who also vote with their money to prefer Cpanel.0 -
yeah.. i don't think many can do what you are saying... i mean, i can't force thousands of clients and tens of thousands of websites to move from cpanel to other panel because of this. lol. if you have a server for 1 site for yourself, then sure, if you don't like cpanel UI changes, vote with your money and change the software used. i wouldn't use Cpanel for 1 site only, too much money for 1 site. But i have thousands of clients who also vote with their money to prefer Cpanel.
We look after thousands of websites, largely via resellers, and have already had numerous complaints from our resellers over this new theme, which no notice was given for, nor choice about whether we wanted. We have been actively working on migration away from cpanel for some time anyway, due to the new licensing model, so this isnt a big shock for our clients, and one they are largely happy with - this change has just kicked that migration up another gear.0 -
Hey folks, any ETA on UI includes feature? Has it landed already? Noticed in 102 changelog: Fixed case PH-17699: Add a Content Include system to Jupiter. but the stuff in /var/cpanel/customizations/includes
still don't load.0 -
@sangeeths - the documentation for that specific feature can be found here: Guide to cPanel Interface Customization - Content Includes " cPanel & WHM Developer Portal 0 -
Thanks a ton @cPRex. Also, is something similar to home_page_header.html.tt
is in the works or should we now detect that with JS? We were using this previously along withglobal_header.html.tt
but I think only the latter was included ascpanel_jupiter_header.html.tt
in Jupiter. Is there anything exposed on the frontend that could help us differentiate?0 -
The details on that documentation page are all I have at the moment. If there's stuff you *aren't* seeing that you want, make a feature request and I'll get it over to the UI team. 0 -
@cPRex @cPanelAdamF are we going to have in jupiter The option to add links on the left navigation menu or is that somehow an option now that I"m not seeing ?? In WHM we have all that why not in cPanel Do I have to enable that somewhere ? thanks SPIRO 0 -
I don't have anything official on those left menu options just yet, but it's something our team is working on. 0 -
I don't have anything official on those left menu options just yet, but it's something our team is working on.
Will there be links there as a default. Like in WHM ? Not admin adding links. Just links in the left nav menu would be nice to mimic WHM's left nav menu with the search box top left under the to logo so there is uniformity.. - Also is there a way to get a link menu example cPanel home/domains/Redirects cPanel home/security/SSL-TLS Status On all the top pages of cPanel like in WHM we have this and it makes it much easier and faster to get to what we want. So we don"t have to keep going back to home and scrolling down again. so if I was at home/security/ ssh access I could click on home/security and see a separate page with all those options like this this is a buzz killer to have to click on cPanel again to scroll back down. :( here is cPanel no Links home /whatever /whatever -04-27 145205.jpg">77561 here is WHM with Links which is nice -04-27 145100.jpg">775650 -
We're still working out better ways to utilize the sidebar space in cPanel. There's lots of fun options being discussed. 0 -
@Spirogg As @cPRex said, we are indeed thinking about that sidebar in :2083 and the potential for that open space. To set some expectations, we have a few projects on tap to end out the year that will have to come first, so there's lots of time for open discussion about what would be best for that area with everyone. 0 -
we have a few projects on tap to end out the year that will have to come first, so there's lots of time for open discussion about what would be best for that area with everyone.
That's great, but if you're already wanting to remove Paper Lantern as of now, that feels like there will be a big gap time-wise between what is currently in place on Paper Lantern and a finalised completed design for Jupitar. Of course, CPanel could retain Paper Lantern until these discussions are completed and Jupitar is actually ready?0 -
Maintaining two themes simultaneously AND asking you all to plan mass-migrations is very costly in terms of time and effort for all involved. I've managed two of these situations now (when X3 was retired, and now with Paper Lantern's retirement) and I certainly don't have the stomach for this approach any more. Earlier in the thread, someone demanded an apology from me; if I was to offer one, it would be that I personally should have pushed harder to make changes directly to Paper Lantern rather than the path we took. This would have been a different kind of disruptive but perhaps one a bit easier to tolerate as we modernize the UX and invite new users of all skill levels into the fold. I say all that to say this... Starting with Jupiter, we are moving from a "every few years, replace the previous theme outright." stance to a "improve the user interface continuously" stance. There will be no pronouncement of Jupiter having been "completed". Please do not wait for that. 0 -
I am glad to say that the frustration in our team while using 102 has decreased significantly compared to Jupiter release from last couple of months. The biggest contributor to this decrease is the reintroduction of the left filterfield in WHM There are a few points that I am receiving complaints about which I have to agree are still annoying. Top right buttons Server menu, Notifications menu should be toggled and not disappear by clicking in the screen. Notification center should either open in a new tab or take the user back to the previous screen after the viewing is done. Load averages should be visible all the time. (confirmed to be in development thank you for that) Blue overlay during search field usage should be either dropped or possible to disable it for WHM, cPanel logged in users. Filter function in cPanel Tools should be preferably be restored like the filter function is in WHM. Those are the main remaining issues I hear about. Don't get me wrong I hear a lot of other complaints of our users but none of those impact productivity or resolve any confusion compared to v100 which is primary our focus. With regards to any formal or non formal apology, while the launch was a absolute disaster for all parties involved I am glad we have the opportunity to input feedback and actively seeing some of it being either implemented or taken under consideration. I personally have far worse experiences with certain vendors on this regard. That does not mean there is no room for improvement but personally I do feel our voice as company is heard to some degree. I am also glad to hear that we are closing a chapter with regards to theme deprecation. While I am sure a lot of people rather had Paper Lantern being the turning point instead of Jupiter (us being one of them) this will save a lot of time in the future for all involved parties. I rather have this to look forward to than any public apology. I would how ever suggest the team to open a sticky thread per big release tier change in the future. The reason for it being to gather feedback and open the discussion about any upcoming changes. While from a analytic point of view I understand the need to have a guided surveys they rarely unearth actual user frustration. Not only that it might help a bit with keeping the forums clean it also shows that feedback is not only actively welcomed but also that some feedback is taken into consideration. We all know that any release with or without a controversial change will cause such a thread to show up anyway, so it might as well be done by the vendor in a controlled and easy identifiable manner. 0 -
Earlier in the thread, someone demanded an apology from me; if I was to offer one, it would be that I personally should have pushed harder to make changes directly to Paper Lantern rather than the path we took. This would have been a different kind of disruptive but perhaps one a bit easier to tolerate as we modernize the UX and invite new users of all skill levels into the fold. I say all that to say this... Starting with Jupiter, we are moving from a "every few years, replace the previous theme outright." stance to a "improve the user interface continuously" stance. There will be no pronouncement of Jupiter having been "completed". Please do not wait for that.
Thank you @cPanelAdamF this is actually really positive to read.0 -
Hi, not sure if this is in the works already or not, but would like to recommend adding an "x" to the left side search bar to clear the search box. Thanks! 0 -
I'll pass that along! 0 -
Hi, not sure if this is in the works already or not, but would like to recommend adding an "x" to the left side search bar to clear the search box. Thanks!
We have a fix for this arriving in PH-18039, which should hit v106 first and then be backported from there to 104 and 102.0 -
I'll pass that along!
I already get an X when I mouse over or when I start to type in chrome browser and I believe with my Macbook pro safari ? 102.0.14 -05-06 165815.jpg">777490
Please sign in to leave a comment.
Comments
399 comments