Skip to content

Conversation

@alikon
Copy link
Contributor

@alikon alikon commented Nov 30, 2025

Pull Request for Issue #46458 .

Summary of Changes

Change URL to site for non-admin users.

Testing Instructions

Open the Content: New Article Submitted email template and add the URL tag somewhere (it's not used by default).

Create a new user with a working email and assign them the Author/Publisher group, etc. (so they can create an article in the frontend but won't have access to the admin panel).

log in frontend like a superuser
and submit an article

Actual result BEFORE applying this Pull Request

wrong url https://SITE/administrator/index.php?option=com_content&view=articles&filter[search]=id:17 for non superuser

Expected result AFTER applying this Pull Request

correct url for non superuser
https://SITE/index.php?option=com_content&view=articles&id=nnn

Link to documentations

Please select:

  • Documentation link for docs.joomla.org:

  • No documentation changes for docs.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

@Kostelano
Copy link
Contributor

I have tested this item ✅ successfully on a57b517

It works, thanks. If the user isn't an admin, they get a working link to the article in the frontend.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46519.

@richard67 richard67 added the bug label Dec 1, 2025
@brianteeman
Copy link
Contributor

even though the url is a site url (not admin) doesnt mean that the recipient of the email will be able to access the article. You are only checking to see if the recipient can access the admin. You are not checking if they can access the article

@alikon
Copy link
Contributor Author

alikon commented Dec 2, 2025

Check added

@softforge
Copy link
Contributor

@Kostelano would you be able to retest now @alikon has added a new check please.

@Kostelano
Copy link
Contributor

I have tested this item ✅ successfully on e4170af

Everything works as before


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46519.

@softforge
Copy link
Contributor

I have tested this item ✅ successfully on e4170afEverything works as before

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46519.

Thank you, appreciate your time to retest

@exlemor
Copy link

exlemor commented Dec 7, 2025

Sorry @alikon, I seem to not be receiving the wanted results ;(

After PR is applied, I still get this URL /_j6b2n/administrator/index.php?option=com_content&view=articles&filter[search]=id:23. ;(

Shows the front end user is logged in:
ScreenFloat Shot of Safari on 2025-12-07 at 03-42-13

Shows the test user is of type Publisher (same results with Author, or Author + Publisher )
ScreenFloat Shot of Safari on 2025-12-07 at 03-42-34

Shows the email result after creating email as Test User of type Publisher with Patch applied ;(
After-PR-applied-2025-12-07 at 03-44-07

@alikon
Copy link
Contributor Author

alikon commented Dec 7, 2025

@exlemor if i understand correctly the user that submit the article is (Author, or Author + Publisher)

but the user for who you show the email (Emmanuel) have core.login privileges if that is correct, cause user (Emmanuel can see the submitted article from backend) then the link is correct that shows you the admin link

@exlemor
Copy link

exlemor commented Dec 7, 2025

@exlemor if i understand correctly the user that submit the article is (Author, or Author + Publisher)

but the user for who you show the email (Emmanuel) have core.login privileges if that is correct, cause user (Emmanuel can see the submitted article from backend) then the link is correct that shows you the admin link

Hi @alikon, I should have added the other graphic sorry, for the Author (or Publisher) user, there is NO email that arrives to the user@domain.com email account (I even checked server email logs) :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants