whoami

Lucas Jenß

cat /etc/motd

The Coding Journal ツ — Notes taken on an epic coding journey. Technical solutions, debugging notes, and practical guides from the trenches of software development.

Close-up of white dominoes with black dots standing on green felt surface, shallow depth of field, focused mood

ls -la ~/languages/

total 8
drwxr-xr-x
▶ PHP
▶ Ruby
▶ Scala
▶ C#
▶ JavaScript
▶ Objective-C
▶ Shell Scripting

ls -la ~/toolchain/

total 7
drwxr-xr-x
▶ Typo3
▶ Akka
▶ Capistrano
▶ Git
▶ MAMP
▶ Adobe Illustrator
▶ NSTrackingArea (Cocoa)

uname -a

platforms
drwxr-xr-x
▶ Mac OS X
▶ Unix

Restoring Missing Content Types In TYPO3 Indexed Search

A TYPO3 search result can look healthy while quietly ignoring particular content elements. Pages may be indexed, titles may appear, and common text blocks may return results, yet a custom element, accordion, media block, or third-party record remains invisible. This usually points to the indexing pipeline rather than a fault in the search form.

The important distinction is that indexed_search generally works with rendered frontend output. It does not automatically understand every backend CType or every custom database field. If an element produces no searchable text, sits outside the searchable page markers, or is excluded by access and language rules, the indexer has nothing usable to store.

This issue is especially noticeable on Australian sites with location pages, service listings, event content, and mobile-first landing pages. A council-style information page might contain accessible text in standard text elements but place critical details inside a custom Fluid component. Visitors using a local NBN connection or a mobile device then receive incomplete search results even though the content is visible when browsing normally.

The fix is a controlled investigation: identify the missing record, inspect its frontend HTML, verify the TYPO3 search configuration, and rebuild the affected index. Changing database rows directly can hide the symptom for a short time while leaving the rendering problem untouched.

Confirm What The Indexer Can See

Begin with a reproducible example. Record the page UID, content element UID, CType, language, workspace state, and a distinctive phrase that should be searchable. Search for that phrase in the frontend, then open the page anonymously in a private browser window. This separates indexing problems from permissions, caching, or a search query that is too restrictive.

Inspect the rendered HTML rather than relying on the backend preview. The phrase must appear as real text in the response sent to the browser. Text placed in a background image, an SVG path, a JavaScript-generated component, or a collapsed data attribute may be visible to a person but unavailable to the standard indexed_search parser.

Check whether the relevant output is enclosed by <!--TYPO3SEARCH_begin--> and <!--TYPO3SEARCH_end-->. Content rendered outside that region is deliberately excluded. Include markers can be useful for selected fragments, but they should be applied carefully so that navigation, cookie notices, and repeated footer content do not pollute the index.

Check Content Element Rendering

A custom CType needs a functioning frontend rendering definition. Depending on the TYPO3 generation, that may be registered through TypoScript, a sitepackage configuration, or a custom content object. Confirm that the element is actually mapped to a Fluid template and that the template prints the fields containing meaningful words.

A frequent mistake is to display a field through a data processor but never output it in the template. Another is to render a label with CSS or JavaScript while omitting a plain text equivalent. Search-friendly markup does not need to be visually prominent, but it should be present in the server-rendered HTML and remain accessible when scripts are disabled.

For records representing products, venues, or articles, decide whether the searchable page should contain the complete text or a useful summary. If the content exists only in a related table, indexed_search will not necessarily follow that relationship. Render the required title, description, address, and relevant metadata into the page, or create a deliberate indexing strategy for the related records.

This is also a good point to check HTML validity. Unclosed tags, malformed comments, and accidental TYPO3SEARCH_end markers can make the parser treat a large section as excluded. A custom element that works in one template may fail in another when wrappers or layout containers change.

Review Visibility And Page Conditions

An element marked hidden, outside its start and stop dates, or restricted by frontend user groups should not be expected to appear in the public index. The same applies to a page excluded from search through page properties or a configuration setting. Check the record and every parent page before changing TypoScript.

Language handling causes another class of false positives. A German or Mandarin version may be indexed separately from the Australian English page, while a search performed with the wrong language context returns no result. Verify language overlays, fallback behaviour, site configuration, and whether the translated content element actually exists rather than merely inheriting an unavailable default.

Workspaces and permissions matter during testing. A logged-in editor can see a draft or restricted record that an anonymous indexing request cannot access. Test with the same host, scheme, language, and authentication state used by the indexer. Canonical redirects, domain records, and HTTPS enforcement should lead to the same accessible page that TYPO3 is attempting to crawl.

Sites serving Australian users should also account for practical privacy and compliance requirements. Avoid indexing private customer details, medical information, or payment references simply because they are rendered in an authenticated template. Under the Privacy Act 1988 and the Australian Privacy Principles, discoverability can become a data exposure issue rather than a search-quality issue.

Verify Search Configuration And Indexing Jobs

Review the indexed_search TypoScript and extension configuration for global and page-specific exclusions. Confirm that indexing is enabled, that the relevant page tree is included, and that search markers have not been overridden by a site template. A later TypoScript include can silently replace an earlier setting, so inspect the resolved configuration in the backend or with the tooling available for your TYPO3 version.

If the site uses the crawler extension or a scheduler task, inspect its queue and execution history. A crawler that receives a redirect loop, a 403 response, a slow response, or a PHP error may leave some pages unindexed while reporting only a general failure. Web server logs, TYPO3 logs, and scheduler output usually reveal this faster than repeated searches.

Clear relevant frontend and system caches after correcting rendering or configuration. Then trigger a deliberate reindex of the affected pages using the indexing task available in your TYPO3 release. Command names and backend screens differ between major versions, so use the version-specific documentation rather than copying a command from an old project.

Do not confuse an empty result with a stale result. If an old phrase still appears after its content has been removed, the index requires cleanup or a full rebuild. If a new phrase is absent but the page was never processed again, the scheduler or crawler is the likely problem.

Rebuild And Test The Search Index

For a small site, reindexing the affected branch is usually safer and quicker than rebuilding everything. For a large publishing platform, schedule a full rebuild outside busy hours and monitor database load, PHP workers, and search response times. Australian businesses often run deployments around quieter evening periods, but remember that Sydney, Melbourne, Brisbane, and Perth do not share the same daylight-saving rules.

After reindexing, test exact phrases, partial phrases, accented characters, plural forms, and terms from each affected content type. Test both desktop and mobile layouts, since responsive templates sometimes replace server-rendered text with a client-side component at smaller widths. A page that works on a wide monitor can still produce a poor search document on a phone.

Keep a small regression set in the project repository: one phrase from a standard text element, one from the custom element, one translated phrase, and one phrase that must never be indexed. Run it after TYPO3 upgrades, sitepackage changes, and search configuration edits. This is particularly useful for teams supporting clients across Australian time zones and release schedules.

When documenting the incident, include the original CType, the template responsible for rendering it, the searchable markers, the indexing task used, and the final verification query. A clear note saves future developers from deleting records or repeatedly clearing caches when the real issue is a missing frontend rendering definition.

Compare Symptoms With Likely Causes

The quickest diagnosis comes from comparing what the visitor sees with what the indexer receives. If the content is absent from the HTML source, focus on rendering. If it is present but excluded from the search region, focus on markers. If it is present and correctly marked but still missing after a rebuild, investigate language, permissions, crawler failures, or index configuration.

A useful workaround is to provide a plain-text summary for visually complex elements. An accordion can retain its interactive presentation while including headings and answers in accessible markup. A map can include a textual address list. A casino or payment-related mobile feature can expose meaningful explanatory copy instead of relying on a client-side widget; a separate mobile payment example can help illustrate why visible interface behaviour and indexable document content are different concerns.

Symptom Probable cause Useful check Practical fix
Standard text is found, custom element is absent Missing or incomplete frontend rendering Inspect the page source for the expected phrase Output the field through the custom template
The content appears visually but not in source HTML JavaScript, image, SVG path, or CSS-generated text Disable JavaScript and inspect response HTML Add server-rendered, accessible text
Several elements disappear after a layout change Search markers moved or closed too early Search for TYPO3SEARCH_begin and TYPO3SEARCH_end Correct the marker placement
Only translated content is missing Language overlay or fallback mismatch Test each site language and record overlay Fix language records and site configuration
Old results remain after deletion Stale index entries Search for a removed phrase Clear or rebuild the relevant index
Pages are inconsistently indexed Crawler, scheduler, redirect, or permission failure Review task history and HTTP logs Fix the request failure and rerun indexing

A reliable TYPO3 search setup treats every content type as a rendering responsibility first and an indexing concern second. Make the required words available in the server response, keep them inside the intended search region, confirm that the public request can access them, and rebuild the index only after those conditions are correct.

For an additional perspective on how technical systems depend on consistent input and processing paths, the road-focused reference offers an unexpected but useful analogy: a destination cannot be reached when a route quietly omits a required section. The same principle applies to indexed_search—trace the content from database record to rendered page to index entry, and the missing step becomes much easier to repair.

Apply the checks to one affected content element first, record the result, and then extend the fix across the sitepackage. That approach restores search coverage without weakening access controls or filling the index with presentation noise.


cat ~/interests.json

KeyValue
editorTerminal-first workflow
osMac OS X / Unix
vcsGit, distributed version control
deployCapistrano, cron automation
graphicsSVG, Adobe Illustrator troubleshooting
networkingIP validation, SSH, VPN

git log --oneline --reverse

2013-10-30

Solving SVG import issues in Adobe Illustrator CS6 and CC

When importing an SVG into Illustrator, the operation fails with an unknown error [CANT]. A workaround for this Adobe-side bug.

2013

Solving NDK build issues on OS X

Troubleshooting native development kit compilation problems on Mac OS X.

2013

Programmatically adding PHP generated TypoScript to the backend configuration

Integrating dynamically generated TypoScript into Typo3 backend setups using PHP.

2013

ArgumentError: Could not parse PKey: no start line

Debugging an SSH key parsing error encountered during deployment.

2011-08-04

Validating IP-Addresses in PHP

Using PHP filter functions with flags like FILTER_FLAG_IPV4 and FILTER_FLAG_IPV6, and understanding how filter_var handles reserved IP addresses.

2011-07-09

Cocoa: Using NSTrackingArea

A short tutorial on using Cocoa's NSTrackingArea to capture mouseEntered and mouseExited events.


cat ~/contact.txt

github: github.com/x3ro
stackoverflow: x3ro
coderwall: coderwall.com/x3ro
twitter: @x3rames