? No Code Attached Yet
avatar lucado
lucado
21 Oct 2019

Steps to reproduce the issue

  • insert code like {loadposition myposition} in an article
  • perform a search of words just before the code

Expected result

  • visualize the module as in an article
    or
  • code removed
    or
  • any better solution

Actual result

  • some text and code {loadposition myposition}

System information (as much as possible)

  • joomla 3.9.12 and 4 alpha 12

Additional comments

  • the module could not be visualized anyway when the text is trumcated for limited number of characters
    screen shot 2019-10-21 at 09 22 44screen shot 2019-10-21 at 09 23 15
avatar lucado lucado - open - 21 Oct 2019
avatar joomla-cms-bot joomla-cms-bot - change - 21 Oct 2019
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 21 Oct 2019
avatar alikon
alikon - comment - 1 Nov 2019

This does'nt happen with com_search the {loadmoduleid 28} is correctly stripped out from search result, unfortunately com_search will not be shipped with j4

avatar mbabker
mbabker - comment - 1 Nov 2019

Because of how Smart Search works, content plugins by design don’t fire off on the frontend search view. Plugins are supposed to hook the indexing process to do any manipulation to the data that is getting saved, and the load module plugin should be hooking this process to remove the placeholder.

avatar Quy
Quy - comment - 26 Jan 2022
avatar Hackwar
Hackwar - comment - 26 Jan 2022

This is not an issue of smart search, but as Michael wrote, of the content plugins excluding themselfs from fireing during indexing. We should review the core plugins, but Smart Search is working as expected. I've not been responding to this issue so far, because I first wanted to review our plugins.

avatar Hackwar Hackwar - change - 19 Feb 2023
Labels Added: ? No Code Attached Yet
Removed: ?
avatar Hackwar Hackwar - labeled - 19 Feb 2023

Add a Comment

Login with GitHub to post a comment