I haven't had time to read and understand current MVC implementation but I think MVCFactory should not contains magic code like that. Maybe a better solution for this problem would be override createView and createModel method directly in DisplayController of com_content frontend, something like below code:

	protected function createModel($name, $prefix = '', $config = array())
	{
		if (!$prefix && $this->input->get('view') === 'articles' && $this->input->get('layout') === 'modal')
		{
			$prefix = 'Administrator';
		}

		return parent::createModel($name, $prefix, $config);
	}

	
	protected function createView($name, $prefix = '', $type = '', $config = array())
	{
		if (!$prefix && $this->input->get('view') === 'articles' && $this->input->get('layout') === 'modal')
		{
			$prefix = 'Administrator';
		}

		return parent::createView($name, $prefix, $type, $config);
	}

The same logic would be applied for view = article and layout = pagebreak

@joomdonation Thank you for your comment.

I looked at it again. I am far away from properly understanding the MVCFactory class. But I think that the functionality belongs here. The function is not only needed in com_content. Each component may use a backend view in the frontend. That is why I think it is general and it belongs to the parent class

But: This special case must be specified in the child class. If we agree that in this case the variable $config['base_path'] is set, it would run properly. That's how it was in Joomla 3. But changes in Joomla 4 have caused that the variable $prefix is set and that is why the line I changed in this PR did not work any more.

I think this is what @mbabker means here: #23530 (comment) with

which is a regression from 3.x where the components were smart enough to proxy frontend requests to the backend code

I see no reason why $prefix needs to be checked in the if statement I changed.

There must be a reason for that check. I am unsure but from my quick look, with your change might break the case when we try to create a frontend model (in this case, we would pass 'Site' as the value for $prefix parameter)

Also, as I mentioned, we are having too much magic code to determine the $prefix base on base_path config value. That's why I think override createModel and createView method when it's needed would be better.

For this, we need someone with better experience to make decision.

@laoneo can you take a look at this?

It seems that the prefix must always be set in Joomla\CMS\MVC\Controller\BaseController::getView(). Otherwise Joomla\CMS\MVC\Controller\BaseController::$views ends up with prefix-less views, which causes conflicts.

Close because of other PR #25367

Thanks for this PR @astridx