Your comments

We have the same problem after migrating to another server. Please help, this is urgent!

We are using version 2019.12.25

I just noticed the same error on Chrome 79.0.3945.130 64bit. It only occured on enterprise version, not on free test environment. 

Please see this related topic:

This is newer version, supporting logs and multiple import files. You can run the script from cron.

Best regards, Patrick

This would be awesome, that would be the most comfortable solution when managing nested shares gets tricky (as in my case)

Steps to get your custom logo back:

  • under Configuration > Interface >Branding, switch to custom theme
  • create customizables/theme.css (Help window says "customizables/custom_theme.css", but css/ext.php refers to customizables/theme.css
  • copy content of css/theme_blue.css to theme.css
  • add block $replaceColors to css/ext.php to get back the colored hover effects
  • instead, you could also include additional css code by following
  • add your logo to the images folder
  • in your theme.css, add
    .headerTbar .x-toolbar-left-row::before {
        content: url("../images/logo.png");
        margin: 0 20px;
  • to place your logo on the right side, use .headerTbar .x-toolbar-extras-row::after instead

Best regards, Patrick


here's an export plugin, just unzip and copy to customizables/plugins folder and enter or copy database settings from autoconfig.php. Clear cache, reload and use 'Open with' action on a folder to export all meta data of all files in this folder. Works recursively.

Best regards, Patrick


here's the first version of my import script:

Just unzip it to the filerun root folder. It includes database access from autoconfig.php and reads/writes directly to database tables. Please bee aware it is setup to write only to the meta field 'tags', but you can adjust it to your needs. Just get the corresponding field id from df_modules_metadata_fields.

You could also wrap the final foreach loop with another foreach iterating through an array of meta fields.

If you can follow my approach, it shouldn't be too difficult to setup an export script (which outputs a csv file) in the very same way.

Best regards, Patrick

Having the option to share the "public" link (non-hashed, with direct access to the file) would be great! -> HTTP_HOST/path/to/file.txt