nextcloud / nextcloud/collectives
Cannot create link to a collectives page from within a page template
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 195
- Forks
- 51
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 48
Description
Describe the bug
When editing a page template, it is not possible to create a normal inline text link to an already existing page within the same collective.
Selecting text and opening the link menu only offers:
- "Link to file or folder" (opens the generic Nextcloud Files picker)
- "Link to website"
- "Open Smart Picker"
None of these provide a way to search for and link to a page within the current collective the way "Link to page" does when editing a regular (non-template) page.
To Reproduce
- Open a collective that has at least one page.
- Go to "Manage templates" and create/open a template.
- In the template, select a word.
- Click the link icon in the toolbar.
- Try to find an option to link to a page within the collective — no such option is available.
Expected behavior
It should be possible to select text in a template and create a plain inline link ([word](url)) pointing to an existing page in the same collective.
Screenshots
Server details:
- Collectives app version: 4.4.2
- Nextcloud version: 34.0.2
- PHP Version: 8.4
- Database: MariaDB 10.11.18
Client details:
- OS: Windows
- Browser: Chrome
- Browser version: 150.0.7871.187
- Device: Desktop
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the template editor's link toolbar and compare its available actions with the regular page editor's "Link to page" flow. Reproduce the issue using a collective with an existing page; done means selecting text in a template exposes a way to choose that page and creates a plain inline link to it.
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
- 68/100