Ah ha! I did some digging and have a new theory…
Are you using Field Kit to upload these files?
I found that the restws_file module (which farmOS uses to process files uploaded via the API) has some fallback code in it that will result in a file named [log-type]_file_[timestamp].dat. This is the only code in farmOS that can result in that filename pattern (that I can find).
@graffte does that sound right? Were you uploading files through Field Kit or through the normal farmOS web UI?
I attached a number of files for OMRI certificates, invoices, material tags, and other info related to the input applied
Were these photos of documents? Or were they other file types like PDFs? Field Kit only supports photo uploads right now. And these photos get attached to the log’s “Photos” field, not its “Files” field. The “Photos” field only supports files ending in one of the following: png gif jpg jpeg
how big are the files you are trying to upload? There is a limit to how many megabytes can be transferred in a single request (currently 50 mb on Farmier-hosted instances). But that shouldn’t be an issue if you are uploading them one at a time through the web UI (because each file upload is processed in a separate request), assuming each individual file is under the limit.
This makes me realize… if you are using Field Kit, then this could also be an issue. I’m just remembering that we ran into this exact limitation in the past: Log not Synching to Database - #12 by mstenta
Field Kit needs some work on the file handling side of things, and that’s on our radar. Field Kit development has turned focus to farmOS 2.x, though, so that is likely where it will be fixed/improved.
If this does seem to be the cause of this issue for you, then at this point my best advice is to not use Field Kit for uploading files.
Instead, if you need to upload files from your phone, then I would recommend using farmOS directly in your phone’s web browser. It works the same way as it does on desktop, and will adapt to the screen size relatively well. farmOS itself will handle issue with the file uploads and provide feedback/warnings if anything goes wrong (this type of feedback still needs work in Field Kit).
The only real limitation to using farmOS directly on your phone is that it requires an internet connection. (This is one of the main limitations that we hope Field Kit aims to solve - but “offline-first” is not easy.)
Hope that all makes sense - and gets to the root of this issue for you! And hopefully it won’t be too hard to re-upload the files in question. Let me know if I can help or provide any more guidance!