Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"FIlename too long" error -- where does the 190 character limit come from? #11

Open
timstallmann opened this issue Mar 17, 2023 · 0 comments

Comments

@timstallmann
Copy link

timstallmann commented Mar 17, 2023

Hi! I'm encountering "Filename too long" errors from this plugin on an Omeka site I maintain; there seems to be a 190 character hard limit on foldername + filename, but from my understanding most Linux filesystems have an unlimited path length and a 255 character limit on filenames -- is there any reason I couldn't patch this file to change the storageName length on my local install?

Here is the relevant bit of code, in ArchiveRepertoryPlugin.php:

if (strlen($storageName) > 190) {
    $msg = __(
        'Cannot move file "%s" inside archive directory: filename too long.',
        pathinfo($file->original_filename, PATHINFO_BASENAME)
    );
    throw new Omeka_Storage_Exception('[ArchiveRepertory] ' . $msg);
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant