FileManager broken on v1.675 and v1.676

FBP

Verified User
Joined
May 5, 2014
Messages
31
I migrated from an almalinux9 server with DA v1.673

The FileManager on the new server w/almalinux9 DA v1.675 is unusable, I also tried v1.676 and it is also broken.

It appears to be a CSS issue but who knows, what I do know is you guys keep making editing files on DA a bigger PITA every update.

The editor is junk to put it kindly, it's slow and clunky, the right click options are trash, and editor pages now refresh, so good luck trying to copy from one sites code to another site anymore.

Now the latest and greatest from DA, a broken file manager in the "stable" release.

I have to switch to the old skin to manage files on all levels it looks like this attachment.
 

Attachments

  • Screenshot 2025-04-29 at 09-55-49 View Files.png
    Screenshot 2025-04-29 at 09-55-49 View Files.png
    98.3 KB · Views: 25
Please try removing all the Evolution customizations. The screenshot really does not look like a standard DirectAdmin installation.
 
Hello, I have set no customizations, the screenshot is a fresh install of DA 1.675 file manager, I also went back to old server, updated it from .673 version of DA to latest and it broke the file manager on the old server as well. I've cleared file cache, tried different browsers, it's definitely not me, I have two other 1.673 servers and their file managers work.

How do you downgrade to .673 or .674 ??
 
Last edited:
I've written plugins and skins for DA, and I've never signed up to be a beta tester. Over a decade and now you can't even put out a stable release branch that is actually "stable". The evolution theme is junk, I am seriously considering going back to cpanel.

Can't easily edit any files now for going on nearly 48 hours on a brand new server. Your initial reply was that somehow by installing your control panel, I did something wrong? All signs it may be time to jump ship.

24hrs later and no answer on if/and or how to go back to .673 or .674

How hard is it to set .674 as the stable release? Seriously
 
Why not update to 1.676? I'm running 1.676 and no issues at all with the file manager.

Looks like this as admin.
afbeelding.png


This is just from a default installation and I have no issues at all editting files. Just select file and click edit.

Looks a bit different than from your screenshot, I don't have those selection squares like you have either in there. Unless that can be activated somewhere in the config.

Also this is main admin, maybe your fbpadmin account is missing something, I don't know, but it certainly looks something is different on your system.
File manager works as designed in Evo. Maybe something else is conflicting with your file manager.
 
Hey Richard thanks for the reply, unfortunately I tried both 75 and 76, all levels produce a broken file manager page like in my screenshot.

Just to be clear, the file manager page I show in screenshot is 100% unusable, you can't right click, nothing works as expected.

It also doesn't matter what user I try, the file manager is broken for everyone on all levels.
 
@FBP, I would suggest opening a support ticket to check if this is something specific to your server. The File Manager is working fine on other servers.
 
Hey Eric I usually use chrome or firefox and have tested it in different browsers and on different computers, they all display the same. My .674 servers file manager works, the fresh install .675 / .676 servers filemanager does not work.

Hey fin, if you read my last reply to you, take note that I went back to the old server I was migrating from, which was .673, I upgraded that server to .675 and the upgrade broke the file manager on the old server, it also looked identical to my screenshot.

As I said I won't be beta testing for something I pay for, I still have tried to restore a backup from the old server on a different server and it restored and the file manager functions as expected.

Is John still running the show here or has he sold out?

I would suggest you roll back the stable version to .674 until you figure it out.
 
I would suggest you roll back the stable version to .674 until you figure it out.
It's not fin but fln with an L in the middle. I tested with Chrome and Firefox both no issues.
Best send in a ticket as suggested, no need to betatest things, they might be able to discover themselves what exactly is breaking things.
They won't revert back things if you're the only one with the issue. Which is logical.
 
Thanks Richard, and my apologies fln, to clarify what I am saying, in theory every DA .673 server and every backup made by a DA .673 server will have a broken file manager when either restored to .675 or if the .673 server is upgraded to .675.

To attempt to replicate this, find a .673 server and upgrade it to stable, or make a backup of a site from the .673 server and restore it to a .675 or greater server, I don't have time for tickets, sorry.
 
@FBP, I seriously doubt this has anything to do with backups and older DA versions.

All of the DA servers out there (servers that are at least 3 months old) have successfully migrated from 673 (released on 2025-01-25) to 675 (released on 2025-03-27).

Unfortunately, if you can not open a support ticket, we will not be able to help you. Somehow I think opening a support ticket should not be that much harder or time-consuming than starting a discussion on a forum 🤷‍♂️.

Without access to the server I can only guess. But if I had to guess, I would say such situation can be caused if you are missing some of the Evolution skin files (CSS and JS code). Did your server run out of free disk space during upgrade?
 
Hey fln, I tar'd the evo skin from one of my .674 servers and copied it over to the problemed .675 server and it fixed the file manager.

Then I upgraded one of my other .674 servers, confirmed the file manager was again broken, replaced skin with .674 version and file manager is working again, so it is definitely an issue you will see eventually, as I said before people aren't exactly lining up to use it.
 
At the moment, more than 86% of all DA servers are running version 1.675 or newer. So far you are the only one seeing this kind of problem with File Manager.

If you tried it on multiple servers, it is likely that the problem is not on the server side but in your browser. One way to test it is to try opening our demo DA instance https://demo.directadmin.com/. It always runs the latest DA version. If you have problems there as well, it would hint that the problem is on the client side (your browser or computer) and not server side.
 
Back
Top