Bug Report: Saving a project with the same name as an existing folder

Bug Description:
When saving a project into a folder, if there is a sub-folder with the same name as the project being saved, the sub-folder is opened instead of saving the project

Steps to Reproduce:

  1. Create a folder called “MyProject” in any folder on the system (e.g. Projects)
  2. In a new project, click Save (or open an existing project and Save As)
  3. Navigate to the Projects folder and enter “MyProject” as the name of the project being saved
  4. Click Save

Expected Result:
The project is saved as MyProject.lbrn2 in the Projects folder

Actual Result:
The Save dialog opens the MyProject folder and displays “no items matched your search”

Workaround:
None - other than to call the project something else or save it somewhere else

System Info:
• LightBurn version: 1.7.08
• OS: Windows 11

Tried saving to a folder other than in a OneDrive location (in case that was causing the problem) and the result is the same for both.

One workaround is to explicitly add the lbrn2 extension to the file name. I’ve just tested it on my system and it seems to work.

Hope this helps.

I’m running LightBurn 1.7.04 and it seems to work correctly on my Ubuntu machine.

I’ve never had that dialog that I recall, except when I’m loading something, not saving anything.

Mine opens in the created myproject folder, but gives no type of error indication.

:smiley_cat:

Thanks Marcus and Jack,

Yes, adding the extension does seem to resolve it.
The message I was talking about is just the windows message:

1 Like

Appears to be a Windows issue. It works as expected in MacOs.

1 Like

There is no file name in your posted photo? I believe without a file name it won’t be able to find anything.

I have limited knowledge of Microsoft OS (thank heavens), so I could be all wet.

:smiley_cat:

My image is what you get after entering My Project as the filename in the folder above. It automatically removes the filename from the box and opens the folder with the same name. It is a bit of a niche situation so not a huge problem, it was just a bit unexpected when it happened and I couldn’t immediately see why. Now I know to add the extension if it happens again. Thanks