Joomla-cms: RSS show {loadmoduleid nnn}

[harrypotter06]

Steps to reproduce the issue

if you showw RSS (https://www.yourdomain.com/?format=feed&view=featured&type=rss&option=com_content) on RSS Output you see {loadmoduleid nnn} or {_module call_}. So customer see on RSS output that customer not need on RSS

Expected result

Rss output do not show {xxx}

Actual result

rss output show {loadmoduleid nnn}

System information (as much as possible)

Joomla 3.9.8

Additional comments

[ReLater]

Confirmed with 3.9.14.
I think this issue is closely related to issue https://github.com/joomla/joomla-cms/issues/22520

[harrypotter06]

Confirmed with 3.9.14.
I think this issue is closely related to issue #22520

No, Version 3.9.14 has the same issue !!!
See that in RSS Output: {loadmoduleid 165} or other things that in {}

issue #22520 did not solve this issue

[richard67]

@harrypotter06 Is seems you misunderstood @ReLater . He wrote that he confirms that the problem exists in 3.9.14, too, and linked to a related issue. He did not link to a pull request which would solve anything, and he did not write it is solved in 3.9.14.

[harrypotter06]

He did not link to a pull request which would solve anything, and he did not write it is solved in 3.9.14.

@richard67 , i know. I confirmed only that the issue exist and the "solution" on #22520 only a workaround is ....

[mbabker]

This is sadly the system design and probably won’t change. All the relevant plugin events are only triggered on HTML views.

[Sukinoz]

Just for trying to "prioritize" this problem related to the RSS (and #22520 , which is still without a solution), comment/remember that RSS is required when you want to share the content automatically with social networks, to generate automatic emails for mailing lists, to insert content on other websites, etc.

[mbabker]

It's not going to be prioritized. I've been beating this drum for years:

• https://github.com/joomla/joomla-cms/issues/13647
• https://github.com/joomla/joomla-cms/issues/14176

It's all talk and no action. In part because taking action at this point would be even more painful to the ecosystem than replacing BS2 from Joomla 3 with BS4 in Joomla 4.