Jupiter Theme Missing Plugins

[Josh Abbott]

I'm testing the new Jupiter theme included with v98 and I noticed that the links for several cPanel plugins, including one that I developed myself, are missing after switching from Paper Lantern to Jupiter.

Based on the documentation for creating cPanel plugins, I used this command in my plugin's installation script:
/usr/local/cpanel/scripts/install_plugin myplugin_cp_reg.tar.gz --theme paper_lantern

This appears to only install it for Paper Lantern, which hasn't been an issue since Paper Lantern was the only theme included with cPanel. But now that Jupiter is being included as an additional theme, I believe hosting providers are going to experience issues with their plugins not displaying in the new theme.

The current documentation for the install_plugin script seems to imply that omitting the --theme option will still default to paper_lantern. Is there a way to ensure the plugin is installed to all cPanel themes, including ones that may be added in the future?

Perhaps cPanel could automatically migrate plugins from Paper Lantern to Jupiter, and any future themes that are added?

 

[cPanelAdamF]

Thanks for reporting this, @Josh Abbott, and thank you for playing with Jupiter. You are ahead of the game!

Yes, we currently do not automatically install plugins in Jupiter (other than our own) in this beta period. For now, you will have to intentionally run install_plugin --theme=jupiter to test out your plugins on Jupiter.

Jupiter is still under active development and we do expect plugin developers to need to do some updates to add support for it. Our own plugins (wordpress toolkit specifically) had visual regressions when we installed it into Jupiter for the first time. As a result, we couldn't assume all plugins would just work out of the box without updates from the plugin developer. As we move away from Paper Lantern in future releases, we will retarget install_plugin as appropriate. We may also add a install_plugin --all-themes to help in the future transition away from Paper Lantern as well.

 

[tomidjx]

That's not really ok. We should know in advance that Jupiter theme is still in beta and that plugins would disappear. This is because now I 've got to revert back to glass, or paper lantern, and thats is a bit of a waste of time.

 

[electric]

When cpanel upgraded to v98, it installed the Jupiter theme. Now some users are switching to it, and they complain that it is missing all our plugins. (softaculous, Jetbackup, etc..)

This is not good. There should be a large BETA notice on the Jupiter theme, along with a note explaining that some features might be missing and the user should switch back to Paper_Lantern theme to use any missing feature.

Or.. cpanel developers should include a way to automatically import plugins that are installed for Paper Lantern theme into the new Jupiter theme.

Thanks.

 

[cPRex]

I agree, and I've passed along similar feedback to the UI team.

 

[Spirogg]

yes I myself just noticed this. and WordPress manager is not showing... oops

it should be standard especially WordPress, CSF as well as plugins we have installed.

since people have been using these plugins like CSF for ages with cPanel.

- Thanks @cPRex for passing along the feedback to the UI team but they need a HUGE Knock on the Door to fix this, so we can report bugs if we find them with Jupitar for plugins wordpress CSF etc.

 

[RyanR]

Any news on this as it's still affecting myself...

 

[cPanelAnthony]

I don't have any news yet, but I will make sure to provide an update when available.

 

[sunmacet]

Now every account has deprecated message and we are flooded with customer tickets about it and still the Jupiter is more or less BETA?

 

[cPRex]

@sunmacet - we have posted this warning inside the cPanel interface to let users know Paper Lantern will be removed soon.

 

[sunmacet]

Why? Why to panic users with warnings? Why can not we choose what warnings to show to our customers? We could do it more gently. Now there is warning that the users do not understand and they try to fix it and failing to do so they are creating tickets. Even when they have chosen to be in the "early adopters" server they are really confused by this warning.

 

[cPRex]

It's a Catch-22 situation for us for sure - there's a balance of warning users about upcoming changes vs springing it on them. No matter what happens, some users on either end of that spectrum aren't going to be satisfied.

 

[sunmacet]

They are our customers not yours. We should have the option to select what kind of warnings we show to our customers. No we just put another message over your message to explain that your message is nothing to worry about...