DirectAdmin 1.681

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
1,190
We are happy to announce the release of DirectAdmin 1.681.

A full release change log is here:

DirectAdmin 1.681

The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!
 
A new build is released. It fixes an issue in the Evolution menu customization page when trying to set a custom menu icon for a category.
 
It looks like the change of "menu entries for phpMyAdmin and webmail" breaks plugin. If I have all commands allow in feature_sets, all plugins show. But if I chose Core functions, Email only, then none of the plugins shows in Evolution skin. DA 1.680 had no problem. I tried to add CMD_PLUGIN and plugin to a customized commands.allow, but it didn't help.

Which command do I need to allow to get plugins showing in the Evolution skin now?
 
  • Like
Reactions: fln
Thanks @gate2vn, showing the plugin menu entries now use /api/plugins/list endpoint. Adding the command plugins will make them work.

However I consider this to be a bug from our side for not automatically adjusting the feature sets. We will soon release an update that will make sure existing feature sets are updated to automatically get plugins command if CMD_PLUGIN was there.
 
Related to plugins, from CMD_PLUGIN_MANAGER page, I cannot deactivate, update or even delete a plugin. DA asks for the admin password, then nothing happens. Can you check this too, please? Thank you.
 
An update is released to make sure plugins listing is available in the feature sets.

@gate2vn The plugin manager works fine on our test server. Also there were no changed related to plugin manager for quite some time. If you would open a ticket we could check out if this is something specific to your server.
 
web-based installer looks nice :)
I trialled it out on a vm the other day for sh*ts and giggles, and I have to say it works really well. Gives you the feeling you have a bit more control over the installation, and I think it will be great for novice users who may struggle to set env variables properly, or miss them.

All in all, a really welcome useful feature.
 
One more update is pushed out. It fixes a UI bug in File Manager on mobile devices. Prior to the bug-fix the directory tree would be always visible instead of being visible only when the button at the bottom right corner is clicked.
 
Changes have been made how plugins behave in DirectAdmin: https://docs.directadmin.com/changelog/version-1.681.html#new-plugins-page-in-evolution-skin

This causes the menu bar not to show anymore in none of the cases. This is very confusing for customers as they don't know plugins.
We added many internal and third party features to DirectAdmin such as backups, Installatron and a PHP version switcher. They are just part of the menu and behave like any other feature in DirectAdmin as they are part of DirectAdmin.

When you click one of these features in the menu as a customer suddenly the menu bar disappears which is very confusing as a customer won't understand the pattern nor that this is 'normal'. They just want to click between the features/options in the menu as any other system or control panel would do.

Is there any way to just show the Evolution menu bar again for customers?
 
Is there any way to just show the Evolution menu bar again for customers?
Short answer - no, not really.


The long answer is:

Menu (navigation between pages) looks different for each of the Evolution layouts. One of the goals of this change was to make sure plugin pages look the same in all layouts.

The new layout is specifically designed to be very similar to the File Manager. Users should be able to quickly pick up the similarities and use back button to get back to Evolution. It is also possible to navigate away from the plugin page using the page search action.

Keeping plugins inside Evolution (looking like other Evolution pages) is not really possible without injecting code and extra logic inside the plugin page. This led to a situation when there were a lot of exceptions from both sides. I mean from Evolution and from plugin developers. And the problems kept popping up to the point when some plugin developers (for example Softaculous) started completely bypassing the Evolution frame and opening plugin in a new browser tab.

The current plugin layout (Evo header + plugins contents) is designed to eliminate the need of all workarounds and give full flexibility to the plugin developers. And full control for the plugin developer as well, Evolution no longer injects logic into plugin pages).


We understand this disrupts the workflow users were accustomed to. However, form the functional perspective, it is still possible to navigate back to the main Evolution view with a single click. If we were to add the menu to the new plugin layout, we would be forced to make the menu look different than it looks on the layout users navigated from. This means the workflow disruption would be just the same. Or even worse because users would need to adjust to two different styles of menu (one in main evolution pages and one in the plugins page).


Hope this gives a better understanding of at least some of the underlying reasons for this change.
 
Thanks for your explanation @fln

There are 2 types of plugins:
The ones like Softaculous and Installatron, which are essentially a whole application on their own. There are also plugins, that are just a small addition to DirectAdmin, a small bridge between the control panel and the platform underneath. From a end-customer perspective the latter is just like other DirectAdmin functionality and that's the way it was presented up till now. With the recent change, even those small plugins are suddenly alien to the rest of DirectAdmin, which is confusing for users

I hope this change can be reconsidered or an optional 'menu' flag in plugins.
 
@Joriz, would be great if you could list the plugins you use. We would like to test them out on our test servers.
 
@fln We use many CloudLinux plugins such as Node.js Selector, PHP Selector Python Selector and Resource Usage. Also we use in-house plugins which offer minor additions as they where part of DirectAdmin for the end-customer.
 
Back
Top