Hi there,

Currently, that how it works actually. But it would be best if you can submit a feature request regarding this issues by creating a new ticket on the forums and set it to "Feature Request", so everyone else could vote for it, the more people request on this, and we will priority consider it.

Thanks for your understanding

Understood. IS there a way to have a login module associated with this 400 error, so I can attempt to do it myself now?

Hello Abaraham,

We actually had this redirected in prior versions but customers are complaining that Google is penalizing them because their site doesn't render a 404 page. This is why EasyBlog is throwing a 404 error when you try to view an article that you do not have access to view or if it is no longer available.

I believe they are customizing their error pages on their Joomla template. If you need this to behave differently, here's what you can do. Edit the file /components/com_easyblog/views/entry/view.html.php and at line 56 locate the codes below:

[gist]
if ($exception instanceof EasyBlogException) {
return JError::raiseError(400, $exception->getMessage());
}
[/gist]

Replace it with,

[gist]
if ($exception instanceof EasyBlogException) {
return $this->app->redirect(EB::getLoginLink(JRequest::getURI()));
}
[/gist]