• Resolved Ravi B

    (@ravibee)


    Hi Ernest, I use the Block Visibility plugin to hide content in a post. It would be nice if ASL didn’t scan hidden content in its search. Currently, ASL ignores the “hidden” attribute and finds matches in hidden text thereby allowing the user to navigate to a page that could potentially only display an “Under Construction” message, because the found content is actually hidden and yet not ready for public consumption.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Ernest Marcinko

    (@ernestmarcinko)

    Hi,

    Thank you very much for your suggestion, but I’m not sure if this is technically possible. While the part of content is hidden when it’s rendered, it is still there in the database and at that point it’s not possible to differenciate (as it is only raw text content).
    I will surely take a look, but there is a very good chance this is not possibe to achieve.

    All the best,
    Ernest

    Thread Starter Ravi B

    (@ravibee)

    Hi Ernest, I totally understand. I suggested it as a feature request because of the popularity of Block Visibility. I realize it could increase ASL’s indexing time when a post is created or modified.

    Perhaps a configuration flag for “Don’t search hidden content” may help? That would allow a graceful fallback to existing behavior if there are any issues with the implementation. The default value of this flag could even be “False”.

    Thanks.

    Plugin Support Ernest Marcinko

    (@ernestmarcinko)

    I will definitely take a look, but it’s unfortunately much more complicated than that. I’m not sure if it’s technically possible to exclude that content, as what the search plugin “sees” in the database vs what the user gets are very different.

    All the best,
    Ernest

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Feature request: support Block Visibility plugin’ is closed to new replies.