darktable-org / darktable-org/darktable

metadata editor preset: shortcut and lua command do not work

Open
#18,911 8 comments 0 reactions 1 assignee View on GitHub

@wpferguson is already working on this.

Since Jun 2, 2025.

lua no-issue-activity
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

I am trying to set a creative common license via meta data editor. Neither lua command nor keyboard shortcut work.

I tried this lua command, as copied from shortcut editor:
dt.gui.action("lib/metadata/preset/CC BY-NC-SA", 1,000)

After that, my logfile contains this error message:
[dt_action_process] action 'lib/metadata/preset/CC BY-NC-SA' not valid for current view

I tried to create a keyboard shortcut, but I get a popup message "... not assigned".

@wpferguson , @dterrahe : Could this have something to do with the new hierarchical presets? See #18829

Steps to reproduce

dt.gui.action("lib/metadata/preset/CC BY-NC-SA", 1,000)

After that, my logfile contains this error message:
[dt_action_process] action 'lib/metadata/preset/CC BY-NC-SA' not valid for current view

Expected behavior

No response

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

dt5.1.0+930~ga836f2f1f1

What OS are you using?

Linux

What is the version of your OS?

Arch-based EndeavorOs, rolling release

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.