File manager (Filemin) editor issues

Hello, I have the same issue described here https://github.com/qooob/authentic-theme/issues/731 and I did upgrade to Authentic Theme 18.47. But for some reason still can't use the editor, all the opened files are blank with exactly 1 line, but at least now you get an window. Cleared cache, restarted the browser, cleared caches, restarted Webmin, restarted the whole server - no effect whatsoever. I am scared to even think what happens if I type something and save... Or I don't type anything and just hit save.

Can you guys check with Ilia, it seems he can't reproduce the problem?

Status: 
Active

Comments

fakemoth's picture
Submitted by fakemoth on Sat, 04/29/2017 - 12:04

Title: File manager issues » File manager (Filemin) editor issues
fakemoth's picture
Submitted by fakemoth on Sat, 04/29/2017 - 12:08

PS: this happens in Chromium Version 58.0.3029.81 (64-bit) on openSUSE Leap 42.2. But started a Firefox - the same thing. Confirmed by a client running Ubuntu.

Both browsers had major updates these days, in Linux mainly focused KDEs Plasma 5.

Two questions :

1 - Are you accessing Webmin/Virtualmin using an SSL (https) URL ?

2 - Are these files you're having problems with plain text files?

Assigned: Unassigned »
fakemoth's picture
Submitted by fakemoth on Sun, 04/30/2017 - 00:33

It happens also on multiple servers, now I have 3 with this issue. To the point:

1) of course only via https;

2) yes they are, for example .css .php .html files and also .htaccess and the like

It's not just me, look at the bug report, but surely is since the last 2 updates, as everything was fine before. The first update 18.46 wouldn't open any file, the second one 47 opens the editor, but it's empty. Except that the files aren't.

Ilia's picture
Submitted by Ilia on Sun, 04/30/2017 - 00:54

Last night, after 18.47, I could reproduce the problem and fixed it in the same package.

It happened when type column is displayed.

You could update manually now using shell script. After that, as the version is the same you would need hard reset browser's cache. Usually Shift+Ctrl+R does it.

Please be kind doing it as I'm going to do another bug fix release very soon.

fakemoth's picture
Submitted by fakemoth on Thu, 05/04/2017 - 04:23

Thanks Ilia, any news on a official release/update version with this fixed?