You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example if you're using a content blocks module like silverstripe-elemental, you'd want to look at the indexable search data that comes from $page->getElementsForSearch().
In its current configuration the report will not work with modules that change the default content storage location from the Content field to anything else.
An idea for an enhancement here would be to make the HTML search locations configurable.
The text was updated successfully, but these errors were encountered:
This will need more thought, as the page Content field is written back to with broken link classes attached. This would mean we'd need to be inspecting content block content directly, rather than read only versions of it.
robbieaverill
changed the title
Links are checked on $page->Content, but could be configurable to look at other fields
Links are checked on $page->Content: won't work with modules like content blocks
Nov 29, 2017
For example if you're using a content blocks module like silverstripe-elemental, you'd want to look at the indexable search data that comes from
$page->getElementsForSearch()
.In its current configuration the report will not work with modules that change the default content storage location from the
Content
field to anything else.An idea for an enhancement here would be to make the HTML search locations configurable.
The text was updated successfully, but these errors were encountered: