Yes it is annoying

When the message JERROR_ALERTNOAUTHOR is thrown by an exception,

• then enabling debug will tell you where it is occuring, so it is easier in the above case

but when, inside a plugin, the code is like this

$app->enqueueMessage(JText::_('JERROR_ALERTNOAUTHOR'), 'error');
$app->redirect(...);

or getting the error from the model ... inside a controller

$this->setMessage($model->getError(), 'error');
$this->setRedirect(...);
return;

then nothing tells you where exactly it occured, you can only estimate where

What about using sprintf and having a file location and line number output within it when in debug mode?

This PR #16814 could be related.

This PR #16814 could be related.

When we have an exception the by enabling debug we can already see where the exception is occuring

the problem is when some code "enqueues" and a no-access message, (see my examples above) and then it redirects, in such a case there is no easy way to find where the no-access thing has occured, especially when such code is inside a plugin

This sounds a really bad idea to me. Why? Well it might be useful when debugging a problem but it will also reveal what "security" is in place and specifically where. In addition it might be meaningful to a developer but its just useless garbage to a regular user.

@brianteeman - you mean the original idea is bad? I'm not looking to reveal anything to the end user or for anything to change for them. As you say, security messages are best left pretty generic. It is only the developer / site owner that needs this, so any additional info can be hidden behind debug mode, or something like that.

As long as its not revealed to the end user then thats fine

@Spudley is this still happening in the latest J3?

@jwaisner I haven't encountered it recently, but I suspect I'd still have a similar problem given the same set of circumstances; I don't think anything has changed in this area.

Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/18577

Since this cannot be reconfirmed at this time we will close this issue. However if this does appear to be a bug in current versions, please open a new item.