@apostrophecms/file - file upload error : File type was not accepted. Allowed extensions: *

[ezzle]

Hi.

I get the following error when trying to upload a .xml, .png, .odt, .pdf file :
File type was not accepted. Allowed extensions: *

How to enable .xml extension for upload?

Best regards

Tshitshi

[BoDonkey]

Hi @ezzle,
That is a little odd unless you have changed the default attachments fileGroups option. Both .png and .pdf files are allowed by default. This section of the documentation outlines how to change what files are accepted for upload. Note that just adding an image type doesn't mean that it will be processed, just that it will be written to the uploads folder and written to the database. Let me know if you need more assistance.
Cheers,
Bob

[ezzle]

One more question. Are you running your codespaces from VSCode locally, or the browser-based version? They seem to act differently.

Browser based version.

[BoDonkey]

I'm having a hard time getting the browser version working nicely. In VSCode it starts up, I can upload files, and they persist between codespaces start-ups. I think we need to look at a repo of your project. Something odd is going on, potentially with other code in the project, that is preventing upload.

[ezzle]

Update:
Very odd:

• Via Images collection on the home page, I can upload and save an image.
• Via Files collection on the home page, I cannot upload the same image and get the error: File type was not accepted. Allowed extensions: *

It seems the problem is not about codespaces

[ezzle]

### The Problem is limited to the Files collection.
Defining project-specific piece-type for testing, I am able to upload files with any allowed extension.
The defined module has 3 attachment fields : module.exports = { "extend": "@apostrophecms/piece-type", "instantiate": true, "options": { "label": "Essential ReportXml", "pluralLabel": "Essential ReportXml", "alias": "essential-reportxml" }, fields: { add: { image: { type: 'attachment', label: 'esse-image', fileGroup: 'images', required: true }, xml: { type: 'attachment', label: 'esse-xml-file', fileGroup: 'xml', required: true }, file: { type: 'attachment', label: 'esse-allowed-file', required: true }, } } }

[ezzle]

Additional testing : update file module to extend '@apostrophecms/image'

module.exports = { extend: '@apostrophecms/image', options: { name: '@apostrophecms/file', label: 'apostrophe:file', ...

I am able to upload files. But the save action produces an error

[boutell]

XML is not on our approved list of extensions for attachments. There are configuration options that can change that. See: https://v3.docs.apostrophecms.org/reference/modules/attachment.html#options This is the immediate problem you're having. It's also true as Bob says that your attachments need to land in a persistent volume of some sort or they won't "stick." Not sure if Codespaces provides a persistent disk or not.

…

On Fri, Feb 10, 2023 at 2:14 PM Robert Means ***@***.***> wrote: At first blush, I would say that codespaces shouldn't make a difference. That message is thrown when the @apostrophecms/attachment module doesn't find a file extension in the array of allowed types. Are you able to upload any files? I haven't played with codespaces that much, but I'm wondering if you need another volume for the uploads? Based on the error it doesn't make sense. You can check the fileGroups by creating a project level ***@***.***/attachment/index.js file. Then console.log(self.fileGroups) from the module init(self). That will let you know what extensions are allowed. If your disallowed file extensions are there, the problem is elsewhere. Cheers, Bob — Reply to this email directly, view it on GitHub <#4041 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAH27MCB3RQX3RAQX4PAATWW2HTDANCNFSM6AAAAAAUXVSLDY> . You are receiving this because you are subscribed to this thread.Message ID: <apostrophecms/apostrophe/repo-discussions/4041/comments/4938720@ github.com>

-- THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER APOSTROPHECMS | apostrophecms.com | he/him/his

[boutell]

I think Bob is probably right, but just for clarification, have you tried a simple .jpg file? Just making sure things Apostrophe definitely accepts are not working.

…

On Sat, Feb 11, 2023 at 6:20 AM Robert Means ***@***.***> wrote: I think I need to play around with codespace a bit to fully understand those errors. Can you provide the schema field/code that you are using for the upload? — Reply to this email directly, view it on GitHub <#4041 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAH27N6DNWAHQAK6NX2CZLWW5YZHANCNFSM6AAAAAAUXVSLDY> . You are receiving this because you commented.Message ID: ***@***.*** com>

-- THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER APOSTROPHECMS | apostrophecms.com | he/him/his

[ezzle]

From the file/index.js
// A subclass of @apostrophecms/piece-type, @apostrophecms/file establishes a library // of uploaded files, which may be of any type acceptable to the // [@apostrophecms/attachment](../@apostrophecms/attachment/index.html) module. // Together with [@apostrophecms/file-widget](../@apostrophecms/file-widget/index.html), // this module provides a simple way to add downloadable PDFs and the like to // a website, and to manage a library of them for reuse.

But I don't see @apostrophecms/file-widget among the modules

[ezzle]

### The Problem is limited to the Files collection.
Defining project-specific piece-type for testing, I am able to upload files with any allowed extension.
The defined module has 3 attachment fields : module.exports = { "extend": "@apostrophecms/piece-type", "instantiate": true, "options": { "label": "Essential ReportXml", "pluralLabel": "Essential ReportXml", "alias": "essential-reportxml" }, fields: { add: { image: { type: 'attachment', label: 'esse-image', fileGroup: 'images', required: true }, xml: { type: 'attachment', label: 'esse-xml-file', fileGroup: 'xml', required: true }, file: { type: 'attachment', label: 'esse-allowed-file', required: true }, } } }

[ezzle]

Additional testing : update file module to extend '@apostrophecms/image'

module.exports = { extend: '@apostrophecms/image', options: { name: '@apostrophecms/file', label: 'apostrophe:file', ...

I am able to upload files. But the save action produces an error

[BoDonkey]

Edited: This was a comment directed at your earlier code comment.
As it turns out, that comment is a hold-over from a2 if I'm not mistaken. There is no file widget. Instead, files are uploaded through the attachment field type. Do you mean the Files and Images menu items in the admin-bar? If you could put up a repo that would cut down on the guessing a bit.

[ezzle]

Edited: This was a comment directed at your earlier code comment. As it turns out, that comment is a hold-over from a2 if I'm not mistaken. There is no file widget. Instead, files are uploaded through the attachment field type. Do you mean the Files and Images menu items in the admin-bar? If you could put up a repo that would cut down on the guessing a bit.

Yes. Files and images menu items in the admin-bar.