Hello, After applying my previous patch, 0001-fix-nested-virtual-database-result-identity.patch, the original problem with retrieving articles from nested virtual databases was fixed.
However, testing revealed a new issue. New problem =========== When performing a search with the MIME option enabled through a three-level virtual dictionary, the MIME headers are missing from the returned results. The previous patch fixed the database identity selection for nested virtual databases, but the existing dico_result_db() callback does not provide a way to pass the result visibility flag to the next level of nesting. As a consequence, the result_db_visible flag is not propagated through the entire hierarchy of nested virtual databases. This prevents the correct database from being identified when retrieving MIME headers. Proposed fix ======== I have prepared a second patch that extends the database module API to address this issue: • Increases DICO_MODULE_VERSION from 3 to 4. • Adds a new dico_result_db_ex() callback with an additional flag argument. • Preserves the existing dico_result_db() callback for backward compatibility with older modules. • Implements virtual_result_db_ex() to propagate the visibility flag recursively through nested virtual databases. • Updates dicod/result.c to use the new callback for ABI version 4 modules, while retaining the old callback for earlier versions. Testing ===== I rebuilt the Docker image michahel72/trixie-dico:latest with the new patch and tested it using my Docker-based environment. After starting the containers with docker compose up -d, I verified the web interface at http://localhost/. The MIME header problem with searches through the three-level virtual dictionary was resolved. The patch is attached: 0002-propagate-result-visibility-through-nested-virtual.patch Best regards, Michael Vlasenko
0002-propagate-result-visibility-through-nested-virtual.patch
Description: 0002-propagate-result-visibility-through-nested-virtual.patch

