[#47509] - [6.2] Enhance Admin UX with Quick Copy for Article IDs and Links
- Closed
- 31 Mar 2026
- Medium
- Build: 5.4-dev
- # 47509
- Diff
- SRV-KILLER09:feature/copy-to-clipboard-clean
User tests: Successful: Unsuccessful:
Pull Request resolves #
- I have read the Generative AI policy, and this contribution is either created without AI assistance or complies with the policy and GNU/GPL 2 or later.
Summary of Changes
This PR introduces a “Copy to Clipboard” feature for the Articles admin list view.
- Adds a copy button next to each article’s ID to copy the ID
- Adds a copy button next to each article’s title to copy the direct frontend URL
- Clicking the button copies the value to the clipboard and shows a “Copied!” confirmation
- Uses native JavaScript and matches Joomla admin UI styling
The goal is to improve admin productivity and make it easier to share or use article links and IDs. This change only affects the UI and does not modify any existing functionality.
Testing Instructions
- Go to Administrator → Content → Articles
- Find the copy icon/button next to each article’s ID and title
- Click the button to copy the ID or URL
- Confirm a “Copied!” message appears
- Paste the value to verify it was copied
- Test in different browsers to ensure clipboard functionality works
- Make sure all admin features continue to work as expected
Actual result BEFORE applying this Pull Request
- No quick way to copy article IDs or URLs
- Manual copy required by opening each article
Expected result AFTER applying this Pull Request
- Copy buttons are visible next to article IDs and titles
- Clicking the button copies the value to the clipboard with confirmation
- No impact on existing admin functionality
Link to Documentation
Documentation link for guide.joomla.org:
- No documentation changes needed for guide.joomla.org
Pull Request link for manual.joomla.org:
- No documentation changes needed for manual.joomla.org
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | JavaScript Administration com_content |
@SRV-KILLER09 New features should always be in the 6.2 branch at this time. See the information here for selecting the branch in the readme. It will probably save you time if you first determine if the feature would be acceptable by reading and following this first #46934
What is the use case for this. Sorry I don't get it
So basically the main goal is to make it quicker for site administrators to copy article IDs or links...with a single click, you can share a link, reference an ID in a support request, or use it in a custom extension & no need to open the article or manually select text.
I know its a very small change, but it might save some time on everyday admin tasks..
one of the problems is that sharing a link might not work if the person getting the link doesnt have the access to see it.
one of the problems is that sharing a link might not work if the person getting the link doesnt have the access to see it.
To address this, I’d like to propose a “temporary access” feature for our Joomla! Community...Basically this would generate a secure, time limited link to a restricted article, allowing access for a defined duration or number of uses before expiring automatically.
Similar to WordPress’s public preview, this could support urgent support, ticketing, and editorial workflows, while maintaining security through proper controls and audit logs...
I’m happy to help prototype this if there’s interest.
I’m happy to help prototype this if there’s interest.
Thats why you should make it a proposal as part of the new feature approval process I linked to previously. You might also want to spend some time looking at a previous attempt at something similar #12009
Thank you for the guidance! I’ll review the previous attempt (#12009) and will follow the new feature approval process to draft a proper proposal for this idea. Thankyou so much once again!
@SRV-KILLER09 As @brianteeman said, it is not a bug fix but a new feature, so the 5.4-dev branch is definitely the wrong target branch.
Please rebase to 6.2-dev or close.
Thanks in advance.
@SRV-KILLER09 As @brianteeman said, it is not a bug fix but a new feature, so the 5.4-dev branch is definitely the wrong target branch.
Please rebase to 6.2-dev or close.
Thanks in advance.
The base branch has been updated to 6.2-dev as requested.
| Title |
|
||||||
| Category | JavaScript Administration com_content | ⇒ | Repository JavaScript Administration com_content com_media NPM Change Installation Language & Strings Front End Plugins |
![avatar github-actions[bot]](/images/avatars/github-actions[bot].png)
This pull request has conflicts, please resolve those before we can evaluate the pull request.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-31 07:24:29 |
| Closed_By | ⇒ | SRV-KILLER09 | |
| Labels |
Added:
Feature
Language Change
Conflicting Files
NPM Resource Changed
PR-5.4-dev
PR-6.2-dev
|
||
What is the use case for this. Sorry I don't get it