[Bug report] Internal posts listing link generates Previewindex.html without a slash

[miditaur]

Operating system

Windows 11

Publii version

Версія: 0.47.8 (build 17475)

This phenomenon was observed in the previous version, and possibly even earlier ones.

Issue type

Application

Bug description

Hello Publii developers,

I have found what appears to be a reproducible bug in Publii’s standard internal-link functionality.

Environment

• Website: newly created clean test website
• Theme: standard Simple theme
• Custom link plugins: disabled / not involved
• Link interface: Publii’s native inline editor toolbar

Steps to reproduce

1. Create a new clean Publii website.
2. Use the standard Simple theme.
3. Create several posts.
4. Open a post in the standard Publii post editor.
5. Select a text fragment so that the inline editor toolbar appears.
6. Click the link button.
7. Select the link to the posts listing from the available Publii link types.
8. Save the post.
9. Open the website in local Preview mode.
10. Click the inserted link.

Actual result

The generated local Preview URL is incorrect.
Publii generates a path similar to:

file:///D:/.../Publii/Previewindex.html

The slash between the Preview directory and index.html is missing.

Expected result

The URL should be:

file:///D:/.../Publii/Preview/index.html

Important confirmation

The posts listing page itself is generated correctly.
When I manually add the missing slash and change:

Previewindex.html

to:

Preview/index.html

the posts listing opens and works correctly.
This confirms that the problem is limited to URL or path concatenation. It is not caused by:

• a missing generated page;
• the standard Simple theme;
• a custom theme;
• a third-party TinyMCE plugin;
• my own link-related plugin.
  The same issue is reproducible on a newly created clean website using only Publii’s native functionality.

Could you please verify the code responsible for resolving internal links in local Preview mode, especially on Windows?

Thank you!

[dziudek]

@miditaur - thanks for finding it - it will be fixed in the upcoming v.0.47.9 release :)

[dziudek]

@miditaur v.0.47.9 has been released :)