looks similar to #17999

Reason seems to be that 'onContentPrepare' is trigger twice
once for ->text and once for ->introtext

#17175

see also
#17830

I don't say that triggering plugins twice for same text is bad,
thus is do not say that PR 17175 is bad

• but several plugins are not designed to be triggered twice for same text

e.g. in this issue we don't have bad side effects

and yes issue #17999 looks same as this one but in that case the double loaded module has some bad side-effects

@ggppdk so i close this Issue as duplicated Report?

@franz-wohlkoenig

issue #17999 shows an important side effect of double loading of modules as a result of the double plugin triggering on same text

but then we have another side-effect

• issue #17830

i cannot say to close any of them, since people will resubmit them ?

Also the title of this issue is wrong / misleading , and should be fixed !

This issue is about article view that was opened via a link from Article Category List
So this issue is about article view !

@ggppdk please have a Look at updated Title.

Indeed, I have tested using the js code from issue #17999, the title should be about article view.
The debugger shows sometimes other results !?

For me is it an issue, because functions will be double loaded, which leads to a fatal error: Cannot redeclare myfunction() / previously declared in...

With the following restriction, it concerns own code!
I solve this problem with the following code: if (!function_exists('myfunction')) { etc.

Plugins are called twice where the complete text is displayed and no intro text is defined by markers etc.

This is certainly an plugin API change, and in my case breaks a site, and is adding extra processing server side for all pages.

#17175 is problematical and changes the plugin API.

This has broken my site and caused me three days of problems trying to workout why some custom code loaded in articles via jumi and {loadposition xxx} didn't work and other bits did.

Data saved in the session was being processed twice.

I have resolved the issue by moving my custom code out of the article an into another position on the page.

This is a serious issue.
Content plugins are now pretty much all triggered twice.
This causes a whole range of issues. The least bad being that pages load slower, as plugins are doing the same thing twice.
The worst case scenario is that fatal errors happen because of things being triggered/executed twice that shouldn't be.

When I remove the code added through #17175 the issue is gone.
That change should be reverted asap, as it is a B/C change!

If #17175 get reverted then we need to find a solution how to prepare the intro text. @regularlabs what do you suggest?

I guess this is needed for the custom fields?
Solve it in the custom fields plugin.

The code in #17175 assumes plugins are not already doing stuff to the intro text.
But the entire $item is passed. So plugins already have the power and ability to do stuff separately on the $item->introtext, $item->fulltext and $item->text.
And many plugins are already doing that.

The onContentPrepare event doesn't expect a single string and do stuff on there. It handles a complete article object.
#17175 messes with the values of the article object and just runs onContentPrepare again.

Example of what plugins do inside the onContentPrepare:

public function onContentPrepare($context, &$article, &$params)
{
	if (isset($article->title))
	{
		doStuffWithContent($article->title);
	}

	if (isset($article->description))
	{
		doStuffWithContent($article->description);
	}

	if (isset($article->text))
	{
		doStuffWithContent($article->text);

		// don't also do stuff on introtext/fulltext if text is set
		return;
	}

	if (isset($article->introtext))
	{
		doStuffWithContent($article->introtext);
	}

	if (isset($article->fulltext))
	{
		doStuffWithContent($article->fulltext);
	}
}

Ok, got it, will prepare a pr over the weekend.

Ok, great :)

Please test #18066, it should fix the issue.

closed as having Pull Request #18066

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

Thanks all.