nextcloud / nextcloud/welcome

Links in source text file are unclickable on dashboard

Open
#169 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug priority normal
Dominant language
JavaScript
Stars
20
Forks
13
PR merge metrics
No merged PRs in 30d

Description

To make it easy for users to find files in the NextCloud folder tree, I created a Readme.md file in the root folder and it shows in the "Welcome and Useful" widget on everyone's dashboard.

I created it with the NextCloud text editor and created the link by adding it with the link button.

However the URLs displayed are not clickable.

This is my second attempt to facilitate file finding for all users. My first attempt with the Readme.md files sometimes shows its content - intended as the folder description - in the folder display above the list of files, but not when using the folder tree to navigate around the cloud instance. #7958

To Reproduce

Create a readme.md in the cloud root with a list of files with a file name and a link to the open it like this:

My File 1: https://my-next-cloud.tld/f/52741
Another file: https://my-next-cloud.tld/f/521112

and so on.

Exit the readme.md, set up the admin setting for the app to use this file.

Go to the Dashboard, select the "Welcome and Useful" widget.

Notice that the links in the readme.md appearing in the widget are not clickable.

The file is also too long and there should be a scroll bar on the welcome app, but the code escape the container and flow off below the screen.

Expected behavior
The widget should display the content of the md file as intended, not as raw text.

Screenshots

Server details:

Nextcloud version: 32.0.8
PHP Version: 8.1.34
Database: Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper

Client details:

OS: Linux
Browser: Chrome, FF
Browser version: all
Device: all

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.

Research direction

Start by reproducing the issue in the dashboard's "Welcome and Useful" widget with a root Readme.md containing file links and enough content to overflow. Trace the welcome widget's rendering entry point and verify the displayed Markdown is rendered as intended. Done means links are clickable and long content stays within the widget with scrolling.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.