Any way to make this work with the "+ New" button on Bases?

[millerdev]

Reproduction steps:

• Create a new folder with a Default Template
• Create a Base filtered to the folder with the Default Template created above.
• Click the Base's "+ New" button to add a new note.

Observed:
New note does not use the Default Template assigned to the folder where the note is created.

Expected:
New note should use the Default Template.

[raeperd]

Thanks for the report!

I tested this on macOS with a Base filtered to a folder that has a folder-specific Default Template. The Base + New button applied the expected template in my test.

This plugin listens to Obsidian’s standard vault create event. It also skips files that already have content.

I checked the latest Obsidian API. I don’t see a separate public hook for files created by Bases. The API exposes BasesView.createFileForView(...) for custom Bases views, but the standard vault create event is still the relevant hook here.

One related issue is #12. In that case, Bases + New worked; only the iOS Share Sheet path did not trigger the plugin.

Could you share these details?

• Obsidian version
• Default Template plugin version
• OS
• .base filter config
• Whether the new file starts empty or already has frontmatter/properties

[millerdev]

Obsidian version: 1.12.7
Default Template plugin version: 1.2.6
OS: Fedora 44 (Linux)
.base filter config

properties:
  file.name:
    displayName: Title
views:
  - type: table
    name: Table
    filters:
      and:
        - file.folder == "bases/books"
    order:
      - file.name
      - Author
      - Recommended
      - Note
      - Created
      - Started
      - Completed
      - Read
    sort:
      - property: Read
        direction: ASC
      - property: Created
        direction: DESC
    columnSize:
      file.name: 193
      note.Author: 125
      note.Recommended: 215
      note.Note: 133
      note.Created: 116
      note.Started: 112
      note.Completed: 96
      note.Read: 18

Whether the new file starts empty or already has frontmatter/properties:

+ New creates a file with frontmatter/properties, but is otherwise empty. Example:

---
Author:
Recommended:
Note:
Created:
Started:
Completed:
Read:
---

The template I want to use has two default values (bases/templates/Book.md):

---
Author:
Recommended:
Note:
Created: {{date}}
Started:
Completed:
Read: false
---

.obsidian/plugins/default-template/data.json

{
  "defaultTemplate": "",
  "folderTemplates": {
    "bases/books": "bases/templates/Book.md"
  },
  "ignorePaths": []
}

Thank you for looking into this issue!

[millerdev]

Are you able to reproduce the issue with the added information?

[raeperd]

Thanks for the additional details, and sorry for the delayed response. I still haven’t been able to reproduce this on macOS, and I don’t currently have access to a Fedora machine for testing.

Your example suggests an event-ordering issue. Default Template deliberately skips newly created files that already contain content. On Fedora, Bases may add the frontmatter before this plugin handles the file creation event, while the plugin ran first in my macOS test. Another plugin, such as Templater, could also populate the file or affect the timing.

Could you check:

• Does this reproduce in a fresh vault with only Default Template enabled?
• If not, which other community plugins are enabled, especially templating or property-automation plugins?
• If you have access to macOS or Windows, does the same setup reproduce there?

If it still happens on Fedora with only Default Template enabled, that would point to platform-specific timing between Bases and the vault create event.

[millerdev]

Delayed response on my part as well 🙂

I created a new vault with no plugins other than Default Template. Then added Books.base with other files, directories, and config as outlined above.

• Clicking + New in Books.base creates a new note with all empty properties (template not used, unexpected).
• Adding a new note using the normal New Note context menu entry on the bases/books directory uses the template with default Created and Read properties (expected).

I also get the same results on Android.

I agree, it must be an event ordering issue. I love the simplicity of this plugin, and wish there was a way to fix this.