Uploads Defaulting to One File Area #615

zachjesus · 2025-10-28T20:28:48Z

zachjesus
Oct 28, 2025

Currently, my uploads even when selected otherwise in UI, default to my audio area, even if I select the library or images file area.

I made sure the syntax of config was correct, and the I can see the file areas with the oputils properly configured, but it just seems to default to audio no matter what I select.

Any one know what might be up?

zachjesus · 2025-10-30T18:29:21Z

zachjesus
Oct 30, 2025
Author

[2025-10-30T17:50:41.666Z] TRACE: ENiGMA½/6148 on enigma: Looking for MCI configuration key (mciKey=MTTLTLTLTLTL)
[2025-10-30T17:50:41.666Z] TRACE: ENiGMA½/6148 on enigma: Using generic configuration
[2025-10-30T17:50:41.667Z] DEBUG: ENiGMA½/6148 on enigma: (nodeId=1192, sessionId=zKdCOEMgnk07, username=zachrosario)
    Set default areaInfo for bypassed form {
      areaTag: 'audio_area',
      storageTags: [ 'audio' ],
      hasStorageTags: true,
      firstStorageTag: 'audio'
    }
[2025-10-30T17:50:41.667Z] DEBUG: ENiGMA½/6148 on enigma: (nodeId=1192, sessionId=zKdCOEMgnk07, username=zachrosario)
    Scanning upload(s) {
      paths: [
        '/tmp/enigul-6148404b0796a86jJtoNmq9rWDOzLy/Nakamura_Ramadan_Is_Almost_Here_2008.pdf'
      ]
    }

It does pass to the server that I selected another area, but then when it actually goes to upload it decides to bypass the form and go to the default option no matter what I select.

0 replies

Juergen-Coding · 2026-01-17T00:04:52Z

Juergen-Coding
Jan 17, 2026

### Upload UI selection ignored → uploads always go to `audio_area` (fallback / bypassed form?)

Hi all,

I’m running into a Filebase upload issue:

- In the upload UI I select another file area (e.g. **library** or **images**).
- The selection **is sent to the server** (I can see the chosen area getting passed).
- But when the upload actually happens, ENiGMA½ **bypasses the form** and always falls back to my default area: `audio_area`.

Here’s the relevant log output:

```text
[2025-10-30T17:50:41.666Z] TRACE: ENiGMA½/6148 on enigma: Looking for MCI configuration
8000
 key (mciKey=MTTLTLTLTLTL)
[2025-10-30T17:50:41.666Z] TRACE: ENiGMA½/6148 on enigma: Using generic configuration
[2025-10-30T17:50:41.667Z] DEBUG: ENiGMA½/6148 on enigma: (nodeId=1192, sessionId=zKdCOEMgnk07, username=zachrosario)
    Set default areaInfo for bypassed form {
      areaTag: 'audio_area',
      storageTags: [ 'audio' ],
      hasStorageTags: true,
      firstStorageTag: 'audio'
    }
[2025-10-30T17:50:41.667Z] DEBUG: ENiGMA½/6148 on enigma: (nodeId=1192, sessionId=zKdCOEMgnk07, username=zachrosario)
    Scanning upload(s) {
      paths: [
        '/tmp/enigul-6148404b0796a86jJtoNmq9rWDOzLy/Nakamura_Ramadan_Is_Almost_Here_2008.pdf'
      ]
    }

The key part seems to be:

Set default areaInfo for bypassed form { areaTag: 'audio_area', ... }

So it looks like the handler rejects the selected area at upload time and replaces it with the default areaInfo.

Questions

Is this fallback expected when the user does not have acs.write permission for the selected file area?
If yes: is there a way to make ENiGMA½ not silently fall back, but instead show an error like “no upload permission for selected area”?
What’s the recommended acs.write for “regular users can upload” (e.g. GM[users] or something else)?

What I’ve checked

config.hjson syntax is valid
oputil shows the areas are configured and visible
UI selection changes correctly, but upload still falls back to audio_area

Suspected fix

Add acs.write for the other areas (library/images). Example:

fileBase: {
  areas: {
    audio_area: {
      name: Audio
      storageTags: [ "audio" ]
      acs: { write: GM[users] }
    }

    library: {
      name: Library
      storageTags: [ "library" ]
      acs: { write: GM[users] }
    }

    images: {
      name: Images
      storageTags: [ "images" ]
      acs: { write: GM[users] }
    }
  }
}

Any confirmation/pointers would be appreciated — especially if there’s a specific log message or config option that indicates “selected area rejected → fallback to default”.

Thanks!

0 replies

Navigation Menu

Uploads Defaulting to One File Area #615

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uploads Defaulting to One File Area #615

Uh oh!

zachjesus Oct 28, 2025

Replies: 2 comments

Uh oh!

zachjesus Oct 30, 2025 Author

Uh oh!

Juergen-Coding Jan 17, 2026

Questions

What I’ve checked

Suspected fix

zachjesus
Oct 28, 2025

zachjesus
Oct 30, 2025
Author

Juergen-Coding
Jan 17, 2026