+7

Fantastic new FileRun version available! Update now!

Vlad R 1 month ago updated by EmilyLove 3 weeks ago 46
  • Much much better mobile experience. Automatic dark mode, installable PWA, embedded PDF viewer.
  • Upload by copy+paste! From Windows Explorer or MacOS Finder into your browser! 🤯
  • Mount as Windows drive without third-party apps.
  • Edit files with your desktop Microsoft Office without downloading. Changes get saved back to FileRun!
  • Very fast loading of the UI, lower memory requirements, smoother browsing of massive folders.
  • The "Photos" view mode shows a much nicer photo grid, and it is now available while browsing any folder.
  • Collections can now hold files and folders that are shared by other FileRun user accounts. Users without home folders can now also create and manage their own collections.
  • Lots and lots of improvements and fixes, including security fixes.

Complete change log here:  https://filerun.com/changelog

Guide on updating: https://docs.filerun.com/updating

    Answer

    +2
    PINNED

    Here is a patch that fixes the following reported issues:

    • compatibility with ONLYOFFICE 7.1.
    • fixes the CSV editor.
    • fixes MySQL error related to the user activity log.
    • fixes broken UI when user has no permissions of making any changes to files.

    Installation guide:

    1. Make sure you are running the latest FileRun version (20220519). This is a patch to the right version, not a complete update (applying to an old FileRun version will probably break things).
    2. Download this file: https://f.afian.se/wl/?id=K5IZnMgXEQ6k6pBYeTlKfkSKas0SOB5Z&fmode=download
    3. From the control panel of your FileRun installation, signed in as FileRun superuser, under the "Update" section, use the little button located on the top-right of the page to upload this file to FileRun.
    4. Wait for the file to upload, then click "Install update".
    5. Clear your browser's cache if you wish to experience the changes. New visitors will not need to do this.

    Thank you very much for your patience and for reporting the problems.

    I got this...
    
    Updating database structure...Failed to execute: UPDATE `df_oauth_clients` SET `logo_url` = 'https://filerun.com/images/dav.png' WHERE `cid` = 'Generic0000000000000000000WebDAV': '.SQLSTATE[42S02]: Base table or view not found: 1932 Table 'cloud.df_oauth_clients' doesn't exist in engine.'
    
    Failed to install update. Please check above for error messages.
    Your FileRun installation might now be broken. If it is, please follow this guide to restore it: https://docs.filerun.com/updating#recovering_a_broken_installation.
    
    -------------------------------------
    Log saved at "E:/xampp/htdocs/system/data/temp/update_20220519_20-05-22.log.txt"

    The error is not from FileRun. Your MySQL database is probably broken.

    Perhaps this would help: https://stackoverflow.com/questions/38759870/xampp-mysql-table-doesnt-exist-in-engine-1932

    +1

    I just updated filerun and noticed a problem with OnlyOffice. Not sure if it is related, it might just be coincidental. 

    When trying to open an office file with OnlyOffice, OnlyOffice reports: “ the document security token is not correctly formed" – which usually means filerun is using the wrong JWT token, so I double-checked, and it was the same inside docker-compose.yml as I had copied into the plugin's configuration in filerun. 

    So thinking it might be OnlyOffice's issue, I downgraded from OnlyOffice 7.1.0 to 7.0.1 which is like 3 months older and everything worked again.

    So to cut a long story short, would somebody mind checking whether this new filerun version properly handles the JWT secret? 

    +2

    This happened to me as well, and it was happening before the update.

    Thanks for chiming in, it is always good to get confirmation from other users and at least now we know its definitely an issue with onlyoffice. 

    Btw. seeing that the filerun hotfix “fixes” the problem it does seem related :-)

    When updating all of the backups complete then:

    [...]
    Backing up "images/icons/" ......Ok.
    Backing up "images/illustrations/" ......Ok.
    Backing up "images/favicons/" ......Ok.
    Backing up "system/data/temp/smarty/" ......Ok.
    Updating "index.php" ......

    rerunning the process doesn't help.Reboot server (Ubuntu 20.04) didn't help

    The permissions of the FileRun installation folder does not allow PHP to write/change. Best to change ownership of the folder (chown www-data:www-data -R /var/www/html) and try again, then restore the folder ownership, making sure "sytem/data" is still writable. You can look at "system/data" folder to check it's ownership or permissions as example of a folder which is writable by PHP/FileRun.

    All fixed now, many thanks.

    loader-wizard.php appears was the problem

    I can't see pictures and files when i update from control panel. I try tried to 'systemctl restart nginx' but the result is the same. When i delete all files about filerun and reinstall the latest filerun and use the exist database ,the result is the same. Fortunately, I made a backup of the previous version of filerun , and when i rolled back to the version of filerun ,everything is fine. Do i need to delete the database and reconfigure all in control panel ?(┬┬﹏┬┬) 

    also I can't see my newly uploaded files.

    I have installed the latest ghostscript but the pdfs still have no thumbnail.And the first is I install through apt-get (I've actually installed it before),the second through github source code compiling :"make && make install".

    Please open a new topic if it is not related to the update.

    In case it helps anyone and to make Vlad aware of potential issue (in case is not unique to my env) 
    After upgrading to this version my Activity Logs stopped working.  
    Upon further inspection I found an error reported by Mysql:
    "1364 Field 'path' doesn't have a default value" when Filerun was trying to write an Activity log entry to "df_logs" table.

    ALTER TABLE `filerun`.`df_logs`
    CHANGE COLUMN `path` `path` VARCHAR(255) NOT NULL DEFAULT '0'

    After this change the Activity logs started logging again.
    Hope it helps someone.

    You shouldn't have a column name 'path' in that table. This updates specifically removes it. If it is still there, the update did not install properly on your system, and you should try again.

    +1

    Nevermind, I think there is a bug in the update. I will fix it.

    I'm getting an error registering the ServiceWorker, only in Chrome desktop:

    "Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://docs.########.com/') with script ('https://docs.########.com/sw.js?v=20220519'): An unknown error occurred when fetching the script."

    I've tested in Edge, Safari, and Chrome Android and all 3 of those register fine. The error appears to only happen to me on Chrome desktop, both locally and remotely. 

    Any thoughts?

    Close your browser completely (all tabs) and try again.

    Tried this but registration still fails. Chrome is updated to Version 102.0.5005.61.

    This issue occurs on both Mac and Windows.

    Nope, same error. I tried on both Windows and Mac, on 3 different networks, 2 separate installations (plus the demo).

    I can provide the stacktrace Chrome spits out but i assume it's not that helpful since the code in minimized?

    My guess is a browser extension intefering with this. Are you able to install any PWA at all? (Here's a demo third-party installable page that you can try: https://mdn.github.io/pwa-examples/a2hs/)

    The github example installed fine.

    Here's the stacktrace I'm getting. It seems to point to the filerun.js section of the filemanager? Not sure if it's helpful or not though.

    Regarding the security warning using older versions of ghostscript:

    despite RHEL7/CentOS7 and RHEL8/CentOS8/RockyLinux8/... have older versions (9.25-5.el7 and 9.27-1.el8) the fixes seem to have been backported to these versions. Found in the Changelogs:

    https://centos.pkgs.org/7/centos-x86_64/ghostscript-9.25-5.el7.x86_64.rpm.html
    https://rockylinux.pkgs.org/8/rockylinux-appstream-aarch64/ghostscript-9.27-1.el8.aarch64.rpm.html

    +2
    PINNED

    Here is a patch that fixes the following reported issues:

    • compatibility with ONLYOFFICE 7.1.
    • fixes the CSV editor.
    • fixes MySQL error related to the user activity log.
    • fixes broken UI when user has no permissions of making any changes to files.

    Installation guide:

    1. Make sure you are running the latest FileRun version (20220519). This is a patch to the right version, not a complete update (applying to an old FileRun version will probably break things).
    2. Download this file: https://f.afian.se/wl/?id=K5IZnMgXEQ6k6pBYeTlKfkSKas0SOB5Z&fmode=download
    3. From the control panel of your FileRun installation, signed in as FileRun superuser, under the "Update" section, use the little button located on the top-right of the page to upload this file to FileRun.
    4. Wait for the file to upload, then click "Install update".
    5. Clear your browser's cache if you wish to experience the changes. New visitors will not need to do this.

    Thank you very much for your patience and for reporting the problems.

    just reporting the Patch/Update installed without problem/errors for me. Thanks Vlad!

    Yeah! This solved the onlyOffice problem. Can you tell me how you fixed it?

    I've clicked on the "Check for Updates" button but in the panel below it says:

    Error: cURL error 60: SSL certificate problem: certificate has expired (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

    My current version is 2021.12.07.

    Thanks

    Turns out I was using the Docker afian/filerun image, not filerun/filerun. After updating docker-compose, all is well. New version look great, thank you.

    I feel compelled to comment on this upgrade; I have had numerous issues on previous upgrades when they didn't go smoothly, so it seems only fair that I highlight that *this* upgrade went smoothly with no errors.  That being said, I did take the time to ensure that the entire Filerun directory tree on my Linux-based webserver were fully writeable by the apache user and group before starting, and as a consequence, the upgrade completed correctly on the first try.  :)

    Thank you Richard! I hope you enjoy the new version!

    Greetings! Thanks again for all your work that's helped me with family photo archiving. I previously had success in preventing inadvertent photo deletion by other users by disabling their permission "User can make changes to files and folders." Now with current version (19052022 + patch), this setting seems to prevent the ability to display the entire folder tree and photos within each folder. (The actual folders and pics are chmod 777 for testing). This was not a problem with previous versions. Running within Docker. Any hints? 

    "prevent the ability to display the entire folder tree" - you mean you can't browse folders from the tree panel?

    I can browse the folders, but no pics are displayed. Also no username button with logout option. Reenabling permission "User can make changes to file and folders" in a given role restores normal browsing, but of course allows file deletion. 

    I have solved the problem by deleting and recreating the roles, then re-assigning the users. I assume it was some permission issue... Thanks again for your remarkable work!

    Same issue here.  

    If "User can make changes to files and folders" is not set, the display is missing buttons and data regardless of browser being used.

    As soon as this option is set, everything is fine.

    The patch above should fix this.

    It does not.  Everything looks like the photo posted above when "User can make changes to files and folders" is not set.

    Perhaps try the solution that worked for me above and definitely clear browser cache...

    +1

    I didn't delete or recreate anything but on the 3rd time clearing absolutely everything in the browser cache (and 24 hours later) everything started displaying properly.  So far everything is now working/displaying properly.

    Getting a new error trying to update to Update to 20220519

    Updating database structure...Failed to execute: INSERT INTO `df_settings` (`var`, `val`) VALUES('ui_theme_dark_mode', 'never'): '.SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'ui_theme_dark_mode' for key 'var'.'
    

    Sorry, I'm a complete noob :/

    Inside "system/data/temp" you will find all the logs created by your attempt to update. In order to help you fix this problem I would need to error from the first attempt, not the last.

    I can't update at all.

    Error.log:

    [Thu Jun 09 18:53:30.096888 2022] [proxy_fcgi:error] [pid 29056] [client 192.168.86.1:1426] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Class 'ZipArchive' not found in /var/www/filerun/system/classes/arch/arch.zip.lib.php:10
    Stack trace:
    #0 /var/www/filerun/system/classes/arch/arch.lib.php(17): ArchZip->__construct()
    #1 /var/www/filerun/system/modules/software_update/sections/cpanel/php/install.php(45): ArchUtil::init()
    #2 /var/www/filerun/index.php(181): unknown()
    #3 {main}
      thrown in /var/www/filerun/system/classes/arch/arch.zip.lib.php on line 10', referer: <a href="https://emilylove.app/?module=cpanel" class="redactor-autoparser-object">https://emilylove.app/?module=cpanel</a>

    You just need to install PHP zip extension and then try again. Something like this should help:

    apt-get install php7.4-zip

    Thanks, that fixed my issue!